We're a small studio, and we hire slowly.

Twenty-two people, by design. We hire only at staff and principal level — engineers and designers who have shipped real products and care about the slow craft of doing it again. Three positions are open right now.

• ● Open · 01 / 03

  Senior Full-Stack Engineer.

  Type
  Full-timeLocation
  Remote · CET ±3hLevel
  Staff / PrincipalTeam
  Web PlatformsCompensation
  €110k – €150k + equity

  You'll ship engagements on the web-platform side of the studio — commerce surfaces, marketing platforms, content infrastructure for clients whose front door is most of their business. You write the architecture document, you ship the hard parts yourself, and you stay on the engagement until it stops being interesting in a good way. There is no tier; you work as a peer to the other seniors on the engagement.

  What you'll do

  • Ship a single client engagement at a time alongside two or three other seniors — typically 12–20 weeks. No one runs the team; the team runs the work.
  • Own the architecture: routing, caching, data layer, deployment topology. We expect a written proposal you'd defend in a board meeting.
  • Write production code. Partners write code. There is no tier between you and the work.
  • Review and edit the work of your peers, and welcome the same in return. Run the design crit alongside the lead designer on the engagement.
  • Hold the on-call line for engagements you've shipped, in rotation with the rest of the studio.

  What we look for

  • A decade or so in the work — staff or principal level on a serious product, ideally one used at scale.
  • Deep TypeScript / Next.js (or Remix), and a working fluency in at least one of: Postgres internals, edge runtimes, or a typed backend (Go / Rust).
  • A point of view on what belongs at the edge, what belongs in the database, and what belongs in the client. You have changed your mind on these at least once.
  • A taste for design. You read the Figma comments and write back in them.
  • An ability to disagree with a client without losing the room.
  Nice to have

  • Open-source contributions in the framework / runtime layer.
  • Time spent in a regulated environment (finance, health, public sector).
  Send a paragraph or two on what you've shipped and a link to the work. No CV needed in the first pass — a partner reads every note within a week.

  Apply for this role
• ● Open · 02 / 03

  Senior Product Designer.

  Type
  Full-timeLocation
  Remote · EuropeLevel
  Senior / StaffTeam
  DesignCompensation
  €90k – €130k + equity

  You'll design product surfaces alongside the engineering team — same files, same standups, same standard. The studio's design discipline is small and unhierarchical; you'll join as a peer to the existing senior designers and partner with engineers to ship work that feels inevitable.

  What you'll do

  • Design one client engagement at a time — discovery, system, prototypes, motion language, the whole arc. You do the design yourself; nobody is reviewing your Figma into a queue.
  • Maintain a tokenised design system that ships as code. We do not separate design and engineering.
  • Run design crit. Open invitations to the client team. Recordings kept, rationale documented next to the file.
  • Pair with engineers on prototype-to-production. The handoff is a conversation, not a wall.
  • Contribute to the studio brand and journal. Write occasionally if the spirit moves.

  What we look for

  • A portfolio of shipped product, not pitch decks. We will read the work that lived under load.
  • Fluent in Figma at the design-system level — variables, modes, libraries that scale.
  • Comfortable reading and editing component code (React + TypeScript). Comfortable building the prototype yourself.
  • A motion practice. You can defend a curve and a duration as readily as a kerning decision.
  • Cultural literacy — you have opinions about magazines, type, and software all at once.
  Nice to have

  • Brand identity work in your past, or willingness to do it occasionally.
  • Public writing about the practice — a blog, a Are.na channel, anything.
  Send a paragraph or two on what you've shipped and a link to the work. No CV needed in the first pass — a partner reads every note within a week.

  Apply for this role
• ● Open · 03 / 03

  AI Systems Engineer.

  Type
  Full-timeLocation
  Remote · CET ±3hLevel
  Staff / PrincipalTeam
  AI SystemsCompensation
  €120k – €170k + equity

  You'll ship AI-systems engagements — retrieval pipelines, agent stacks, evaluation infrastructure for clients who are held to a real standard (clinical, financial, legal). The studio's AI work is eval-first: we build the test harness before we build the answer. You'll carry that posture as a peer to the rest of the engagement team, not above it.

  What you'll do

  • Architect and ship retrieval and agent systems for clients with non-negotiable correctness requirements. You write the eval set yourself, with the client.
  • Build evaluation pipelines — golden sets, rubrics, automated scoring, human review where it matters.
  • Own the observability story: traces, cost tracking, drift detection, regression alerting.
  • Defend model and architecture choices to the client and to your peer reviewers — including the decision not to use an LLM where simpler tools would do.
  • Stay current. The field moves; we expect you to read.

  What we look for

  • Production AI experience that was held to an external standard — not just a demo, not just a prototype.
  • Strong Python and at least one of: LangGraph, DSPy, custom agent frameworks. We are framework-agnostic; pragma matters.
  • Practical experience with retrieval evaluation — recall@k, faithfulness, citation grounding.
  • A history of building eval before features. You have stories about catching regressions before users did.
  • Comfort explaining why a model failed last Tuesday with the trace open in front of you.
  Nice to have

  • Background in a domain where the answer matters (medicine, law, finance, public sector).
  • Open-source contribution to an eval or observability tool in the AI stack.
  Send a paragraph or two on what you've shipped and a link to the work. No CV needed in the first pass — a partner reads every note within a week.

  Apply for this role

The lists above are role-specific. The instincts below apply to every senior we read for — and to everyone we have hired.

• A decade in the work, or its honest equivalent.

  We hire at staff or principal level. Years are a proxy; what we are really reading for is whether you have lived through the part of a product where the easy decisions are gone.

• A point of view, written down.

  We want to know what you have argued for, and what you have changed your mind about. A blog, a long PR description, an internal memo — anything that shows the shape of how you think when nobody is watching.

• A taste for ownership.

  The studio runs without a project manager and without a tier between you and the client. If you have spent the last few years insulated from delivery, this is unlikely to be the right room for you.

1. 01

   Note

   Send a paragraph or two to [email protected]. A partner replies in a week, or sends a short note explaining why we cannot.

2. 02

   Conversation

   A 45-minute call with a partner and a senior in the relevant discipline. We will ask about the work that mattered and the one you wish you could redo.

3. 03

   Studio day

   A paid day inside an active engagement. You write code or design in our files. We pair, we review, and we listen to how you think when you are uncertain.

4. 04

   Offer

   Two partners and the lead of your discipline make the call. Offers are written, with the comp range published above and equity participation explained in plain language.

Don't see the right role? Write anyway.

Even when we are not actively hiring, we keep notes from senior engineers and designers we'd want to work with. The next opening is rarely posted before someone we already know reaches out.