All roles

Founding Product Engineer

Own whole features end to end, from the Postgres row-level security policy up to the thing a venue owner taps on a Tuesday lunch service.

Why this role exists

Served does reservations, floor plans, menus, reviews and a visibility audit that reads live public sources. That is a wide surface for the number of people currently holding it, and the work is now limited by hands rather than by ideas.

Team
Engineering
Commitment
Full-time
Location
Remote, within two hours of CET
Pay
Range sent with our first reply

What you would own

  • Features from schema to screen: migration, row-level security policy, server action, UI, test.
  • The correctness of anything touching money or tenancy: a venue must never see another venue’s data, and that is enforced in the database, not in a component.
  • The performance of public pages, which are static or incrementally regenerated and are the first thing a guest ever loads.

What we need

  • You have shipped and then maintained a TypeScript product, and lived with your own decisions for more than one quarter.
  • You are comfortable in SQL, not just in an ORM. You can read a policy and say who it lets in.
  • You can decide what not to build, and say why, in writing.

What helps, but is not required

  • Next.js App Router, Supabase or Postgres, Stripe.
  • You have worked somewhere with real operational load (hospitality, logistics, healthcare) and know what happens to software during a rush.

What this job is not

This is not a specialist seat. There is no separate QA, platform or on-call team to hand a problem to, and there will not be one for a while: the person who ships it is the person who fixes it at 19:00 on a Friday. If you want a narrow, deep lane inside a large system, you will be happier elsewhere and we would rather you knew now.

How hiring runs

  1. You write to us

    No form and no account. An email with something real in it: what you have built, or what you would look at first in this role. A CV is welcome but it is not the part we read closely.

  2. We reply either way, within a week

    Including when the answer is no. If it is a yes, that reply carries the pay range for the role, so you have it before you spend any more time on us.

  3. One conversation, 45 minutes

    What we are building, what the role actually involves day to day, and your questions. One call, not a sequence of screens with different people asking the same things.

  4. A paid piece of real work

    Around half a day on an actual problem from our backlog, at a day rate we agree before you start. You keep the work and the fee whichever way the decision goes. If a take-home does not suit your circumstances, say so and we will find another way to see how you think.

  5. Decision, with reasons

    Yes or no, and why, from a person. Then the offer in writing with the numbers in it.

Apply for this role

An email is the whole application. No account, no form, no portal.

Where a range is not published above, we send it in our first reply, before any call and without you having to ask. We will not ask what you earn today.