We're hiring - 2 open roles on the Forward-Deployed track

Build the loop. Then run it everywhere.

We run an AI-native software team: contract-first, Claude at every step, features live behind a flag in days - no sprints, no staging, no hand-offs. We're hiring two full-stack engineers (Python + JS/TS) who'll master that pipeline on our product, then deploy forward to execute external projects on it.

Open roles

Two seats. One track.

Both roles are full-stack by default - backend, web, and app in the same week - and both grow into forward-deployed engineers who run entire external projects on the loop.

Junior

Junior Full Stack Engineer

0–2 years. Solid Python + JS/TS fundamentals and genuine AI-native fluency. Ship well-scoped features from your first weeks, grow into the Engineer DRI seat, then deploy forward. Slope over pedigree - new grads welcome.

Full-time · 1 opening · Python + JS/TS · Forward-Deployed track
View role →
Senior

Senior Full Stack Engineer

5+ years. Deep Python + JS/TS. Own the biggest features end-to-end from day one, hold the technical bar at the review gates, mentor the junior engineer, and lead forward-deployed engagements.

Full-time · 1 opening · Python + JS/TS · Forward-Deployed track
View role →
How we build

No sprints. No staging. No hand-offs.

Every feature runs a 10-stage pipeline where Claude does the heavy lifting and a human DRI - one directly responsible engineer - drives every step.

01

Contract-first

A frozen backend↔frontend contract + simulator before any code - so both sides build in parallel against the same reality.

02

AI-native execution

Claude Code writes most of the code. Engineers direct it, review it, and verify it by running the app - not by trusting the diff.

03

One Design System

Every screen is composed from a living component library; anything new is contributed back. Build it in the system, not the feature.

04

Flags, not staging

Verify locally, merge dark behind a feature flag in production, dogfood there, flip it on. Rollback is one click.

05

Artifacts, not meetings

Each step outputs a structured doc the next step's Claude reads directly. Three synchronous touchpoints per feature - that's it.

06

Done = demonstrated

Screenshots, green gates, a flag, and a one-click rollback - never just "code written."

The track

Builder → DRI → Forward-Deployed.

A forward-deployed engineer ships working software while embedded with an external team - owning the project from the scoping conversation to the live feature, on their stack, at our speed.

1

Build

Master the pipeline
  • Ship full-stack across a Python/Django backend, a TypeScript web client, and a React Native app
  • Claude Code as your pair on everything
  • Verify by running: flows driven, screenshots taken, gates green
2

Own

The Engineer DRI seat
  • Design frozen contracts + simulators from the PRD
  • Build backend ∥ frontend in parallel, integrate, launch behind a flag
  • Success metric wired to a live dashboard before the flip
3

Deploy forward

External projects
  • Install the portable pipeline on a client's repos
  • Scope → contract → build → demo → live, embedded with their team
  • Feed what you learn back into the loop
Hiring

A process built like the job.

The centrepiece is a paid, timeboxed build exercise where using AI isn't just allowed - it's required. We assess how you direct and verify AI, not typing speed.

01
Intro call
30 min · bring something you shipped
02
Build exercise
Paid · timeboxed · AI required
03
Deep-dive
Defend decisions · pair live
04
Offer
Fast

AI is already your daily pair? Show us.

Apply with links to things you've shipped - working software beats résumé lines. Location and compensation are discussed during the process.