How we work, and what we look for.

How we work

  • We write things down

    Decisions, trade-offs and the reasons behind them live in writing, not in a meeting someone missed. It is slower on the day and dramatically faster over a project.

  • You own the outcome, not the ticket

    Engineers here talk to clients, understand the business problem, and are expected to push back when the requested solution is the wrong one.

  • Craft is not decoration

    Accessibility, performance and readable code are part of the definition of done. We do not ship a thing and schedule the quality for later.

  • No heroics

    Sustained overtime is a planning failure, not a virtue. Estimates are honest and scope is negotiated rather than absorbed by people's evenings.

Open roles

No open roles right now.

We would rather show an empty page than list a role we are not actually hiring for. If the way we work sounds like how you want to work, send us something — what you have built, what you are good at, and what you want to do next. We read every message and reply to the ones we can act on.

Send an open application

Start with a conversation, not a quote.

Bring us the workflow, the constraint or the deadline. We will map it with you before anyone talks about scope.