Senior Full-Stack Engineer

What you'll own

• —A named surface on one or two client products at a time — you are the person who knows how it works
• —The data model for what you build, including the migration path when it changes
• —Reviewing other people's code properly, which means being willing to block a merge
• —Being in the sprint demo and explaining your own work to the client

What we need

• —Strong TypeScript, and React or a comparable component framework in production
• —A backend you've actually operated — Node, Python or PHP — including the database behind it
• —Relational data modelling you can defend: indexes, constraints, and why you normalised or didn't
• —Experience shipping to real users and dealing with what came back

Helpful, not required

• —Next.js App Router, Drizzle or Prisma, Tailwind
• —Having run something on-call, even briefly
• —Client-facing experience — you'll get it here either way

What this role isn't

So the wrong candidates can rule themselves out in thirty seconds rather than three interviews.

• ×It isn't a pure front-end role. You'll write SQL most weeks.
• ×It isn't an architecture-only role. You write code.
• ×It isn't a place to specialise narrowly — breadth is the job.

How we interview

1. 01Screening call — 30 minWhat you've built and what you'd want to own. No puzzles.
2. 02Technical conversation — 90 minWe read real code together, yours or ours, and talk about the trade-offs in it. No whiteboard algorithms.
3. 03Conversation with your lead — 45 minHow you'd work together, and your questions about us.

Decision within two weeks of the first call. If it's a no, you get a reason, not silence.