Skip to content

Working here

A small team, and nothing to hide behind.

There is no bench here, and no layer between you and the software. That is the whole pitch: you will build things people use, you will maintain them afterwards, and you will find out quickly whether your decisions were any good.

Engineering culture

Four things that are actually true of the work.

Small team, real ownership

There is no layer between you and the thing being built. You will see your work in front of a user, and you will be the one who fixes it when it misbehaves.

AI as a tool, not a shortcut

We use AI tooling across engineering, and we expect you to. We also expect you to be able to explain what the code does — reviewing AI output critically is a skill we take seriously here.

Software you have to live with

We maintain what we ship, often for years. That changes how you write code: the person inconvenienced by a clever shortcut is usually you, six months later.

Direct feedback, early

Work gets reviewed on what it does, not on how long it took. You will be told plainly when something is wrong, and told why, which is the only version of feedback that is worth anything.

What you would learn

The parts a course leaves out.

Most people arrive able to write code and unable to change code — which is almost the whole job. The gap between those two is what you would spend your time here closing.

  • Working in a real production codebase from the first week, not on a detached practice project

  • Code review on everything you write, with the reasoning spelled out rather than just a verdict

  • Exposure to the whole path — problem, data model, interface, deployment, and what breaks afterwards

  • Using AI tooling the way a working engineer does, including where it is the wrong answer

  • Seeing how a requirement from a business becomes a decision in a schema

Before you ask

What we have not decided yet.

Duration, working pattern, any stipend and any certification are agreed with each applicant and confirmed in writing before anything begins. We have not fixed those terms in advance, so we are not going to advertise them here — ask us, and you will get a straight answer rather than a number we might have to walk back.

Apply

Pick a track and
tell us what you have built.

We read applications ourselves. Something small that actually works tells us more than a list of technologies.