Full-Stack Engineer
You would own features end to end inside businesses that are already running on them — the data model, the API, the interface, and the gate that decides whether your change is allowed to merge. Small team, so the surface you own is wide and the feedback is immediate.
A week looks like this: read the part of the system you are about to change, decide what the record should actually be, then build the whole slice — schema, endpoint, screen, test. Nothing here is thrown over a wall to another team, and nothing merges because someone was in a hurry.
- Build features end to end in TypeScript and React, on a Node or Python backend with Postgres underneath.
- Model the data properly — one authoritative record per business concept, constraints enforced by the database rather than remembered by the application.
- Write the tests that make the security-critical path a gate rather than a suggestion.
- Work inside a client’s standups and deadlines, and hand the thing over so their own team can carry it.
- Leave the runbook and the decision note behind you. If it only lives in your head, it is not finished.
- Strong TypeScript and React, and a backend you are genuinely fluent in — Node or Python.
- Real SQL. Not an ORM you have never looked underneath.
- You have shipped something people depend on, and stayed to fix what broke.
- Plain writing. Explaining a trade-off to a non-technical owner is part of the work, not a soft skill.
- Comfort with a gate blocking your own merge when it should.
Not required: a degree in the field, framework maximalism, or a portfolio of side projects. What you shipped and what it cost to run matters more.
Send. Use the form below to send us one thing you have built and are proud of. We reply either way, within a week, with what we thought of it.
Review. Two paid days on a real repository through one lens, written up the way we write them.
Decide. A conversation with the two people you would sit beside, then a straight yes or no with the reason attached.