Software Engineer - Marketplace Management

About Nasam

What Makes This Role Different

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

What We Expect

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.