Founding Product Engineer - Marketplace Management

About Nasam

Nasam is a multi-channel growth partner for brands in Saudi Arabia. We help brands operate and grow across marketplaces including Amazon, Noon, Trendyol, Salla, and quick commerce, so they can stay focused on product and marketing.

Each brand works with a dedicated Account Manager, supported by internal software that helps them operate with more speed, better judgment, and less manual work. Our platform is already live and used daily across orders, inventory, pricing, catalog, analytics, vendor management, and invoicing. It supports 20+ brands across multiple integrated marketplaces.

We are still early. The market is still open. Marketplace management in Saudi is growing fast, but there is no clear category leader yet. We think the company that understands the domain deeply and executes best can still become it.

What Makes This Role Different

This is not a role where engineering sits downstream from product, design, or operations.

You will be one of Nasam's early engineering hires. You will work across the product end to end: understanding the problem, shaping the approach, designing the experience, building the system, shipping it, and learning from how it is used.

There are no separate frontend, backend, QA, data, or infrastructure teams. That does not mean chaos for the sake of chaos. It means ownership is real. The work is broad, the feedback loop is fast, and your judgment matters.

Your users sit in the same room. You will work closely with Account Managers, understand how they operate, what slows them down, where they are guessing, and what the platform should do to make them more effective.

This role is for someone who wants to build software that changes how a business operates, not someone who only wants to implement scoped tickets.

How We Think About Product

• We care more about user experience than local code convenience. If the better experience is harder to build, we usually choose the harder thing.

• We do not want to build dashboards that simply display data. We want to surface what matters, make the next action obvious, and reduce the amount of thinking the user has to do.

• We do not measure features by whether they automate a task. We measure them by whether they increase brand growth and whether they expand what one Account Manager can effectively handle.

• We try to understand a problem properly before building. If something is non-trivial, it should be scoped with care. We document decisions, architecture, tradeoffs, and domain knowledge because clear thinking matters here.

What You'll Work On

You will build and extend core platform capabilities across marketplace operations, internal workflows, and growth tooling. Examples include:

• Designing workflows that help Account Managers identify which brands need attention, why, and what action to take

• Turning fragmented marketplace data into coherent product decisions. Different channels report different metrics, with different definitions and different levels of reliability. You will help define what matters and how it should be surfaced.

• Building systems that reduce manual operational work without losing important judgment. In some cases that means automation. In others it means building tools that improve decisions, not just speed.

• Integrating new marketplaces and sales channels, each with distinct APIs, business rules, fulfillment models, and edge cases

• Structuring operational processes that are currently handled through checklists, back-and-forth, or tribal knowledge, then deciding what should become software, what should stay manual, and how the experience should work

• Supporting time-sensitive commercial moments such as Ramadan, White Friday, and Founding Day, where pricing, promotions, inventory, and execution all need to work across multiple channels

What This Looks Like in Practice

A brand sells on Amazon, Noon, and Salla. Each platform reports performance differently. You need to work out what listing health should actually mean across those systems, create a coherent model behind it, and surface the signals an Account Manager can act on without overwhelming them.

We add vendor management. You go deep into Amazon documentation, learn how the purchase order lifecycle really works, speak to the people internally who live the workflow every day, prototype the right experience, and refine it until the system fits both the business reality and the user.

An Account Manager handles 12 brands. Each morning starts with the same question: what needs attention today, and why You think about how the platform should answer that clearly and proactively.

A brand is preparing to launch on a new channel. Today that process includes manual steps, scattered knowledge, and inconsistent execution. You help define what brand readiness actually means, what can be automated, what needs visibility, and how to make onboarding more predictable.

What We Expect

We expect strength across four areas.

1. Problem Ownership

You should be able to take a problem from understanding to shipped solution. That means you do not wait passively for a perfect spec. You gather context, identify what matters, challenge weak framing, make tradeoffs, and drive progress.

Before building, you should be able to explain the real problem, who experiences it, why it matters, what success looks like, and what risks come from solving it poorly.

2. Product Thinking and UX Judgment

You should think in workflows and decisions, not screens and tickets. We care about software that helps users act, not software that simply shows information.

That means understanding the context around the feature, the decisions the user is trying to make, what is slowing them down, and how the product should reduce confusion and effort.

A functional interface is not enough. We want experiences where the right action is clear and the product feels aligned with the way the business actually works.

3. Engineering Craft

You should have strong full-stack engineering judgment. That includes system design, schema design, backend services, frontend implementation, maintainability, reliability, failure handling, and code quality.

We are not looking for working output alone. We are looking for good judgment: choosing suitable solutions, understanding tradeoffs, and building systems another engineer can trust and extend.

4. Domain Understanding

In this role, domain knowledge is part of the work. Product and engineering decisions get much better when you understand how marketplaces operate, how brands experience problems, how Account Managers work, and where the operational and commercial constraints actually come from.

You do not need to come in knowing everything. But you do need genuine curiosity about the space and the willingness to build judgment through documentation, products in the market, internal workflows, and real user exposure.

What Success Looks Like

In this role, success looks like being able to independently gather context, shape a problem well, and ship solutions that improve how the business operates.

Over time, we would expect you to:

• Take important problems from understanding through shipping with minimal guidance

• Improve requirements rather than simply execute them

• Make stronger product decisions because you understand the workflow and user deeply

• Ship work that needs little UX correction because the thinking was strong from the start

• Show sound technical judgment across backend, frontend, and data

• Bring domain understanding naturally into product and engineering decisions

Who Tends to Thrive Here

• You think in problems, not just tickets

• You want to understand why something matters for the business before you build it

• You are comfortable moving end to end, from framing to shipping

• You are comfortable with ambiguity, but you do not romanticize it. You reduce it through good thinking, good questions, and good writing.

• You care about product quality, not just code quality

• You are curious about the domain. Marketplace dynamics, fulfillment models, pricing, brand growth, operational workflows, and commercial constraints are interesting to you, not background noise.

• You would rather have real scope and real responsibility in a small team than narrower ownership in a larger one

This Role Is Probably Not for You If

• You mainly want clearly scoped tasks with most of the thinking already done for you

• You are interested in technology but not especially interested in product, users, or business context

• You prefer narrow specialization over broad ownership

• You want a highly structured environment with established process, stable role boundaries, and a well-defined progression ladder

• You are optimizing primarily for resume signaling rather than for learning, judgment, and real responsibility

Requirements

• Strong full-stack engineering ability. You should be able to build backend systems, design relational databases, and ship frontend experiences with sound judgment, communication and thought process.

• Evidence that you have taken something meaningful from idea or problem stage to shipped outcome. That could be within a company, a side project, a product you built, or something you founded.

• Clear written communication. We document decisions, design, architecture, and domain knowledge. Writing clearly is part of the job.

• Comfort learning unfamiliar business domains and translating them into product and system decisions.

Nice to Have

• Experience with marketplace APIs, e-commerce operations, or multi-tenant systems

• Experience in an early-stage startup environment

• Taste and curiosity in product discovery

• Experience with NestJS, PostgreSQL, AWS, and React

What We Offer

• Competitive salary
• Equity
• Hybrid work in Riyadh
• A fast feedback loop
• Scope and ownership that are difficult to find in more mature teams

Hiring Process

• The process is short and practical. We will start with a conversation about how you think, what you have built, and how you approach product and engineering problems. Then we will ask you to do a small piece of real work similar to what the role actually involves.