Skip to content
07Careers

Build systems that have to work.

We are a small engineering team. That means the person who designs a system is usually the person who ships it, operates it, and answers for it.

01How we work

What the work is actually like.

  1. 01

    Decisions are written down.

    Choosing a modular monolith over microservices, or putting search behind a message queue, is a decision with consequences. We record why, so the next person inherits the reasoning and not just the result.

  2. 02

    You own it past the demo.

    Work is not finished when it renders. It is finished when it is documented, tested, packaged and operable by someone who was not in the room when it was built.

  3. 03

    Constraints come first.

    An offline school, a shop with a bad connection, a provider that goes down mid-request. We design for the conditions the system will actually meet, not the ones that make it easy to build.

  4. 04

    Small team, wide surface.

    The same engineer may touch a Spring service, a React client and a Kubernetes manifest in one week. Breadth is expected; so is the discipline to keep each part honest.

02No open roles right now

We are not hiring for a specific position today.

If you build the kind of systems described on this site and want to be considered when that changes, send your work — a repository, a system you designed, or a problem you solved and why you solved it that way. We would rather read that than a CV.

Start a conversation