Careers

Build with us.

We do not publish open roles yet. If you build software, products or infrastructure and want to work with us, write to us with what you have built.

Rows of desks and mesh chairs in a bright open-plan office

Disciplines

The work, by discipline.

Five disciplines, one team responsible from the first workshop to on-call. Each one links to what it covers and the tools it uses.

  • Software

    Web applications, platforms and the business software companies run on.

    • React
    • Next.js
    • TypeScript
    • Node.js
  • Mobile

    Apps for iOS and Android, from the first prototype to store release — and every OS update after.

    • React Native
    • TypeScript
    • Node.js
    • APIs
  • SaaS

    Multi-tenant products billed by subscription, built to be operated for years.

    • Next.js
    • TypeScript
    • Node.js
    • PostgreSQL
  • AI & Automation

    AI that does real work inside a product, and automations that remove manual steps.

    • AI
    • Automation
    • Data systems
    • Node.js
  • Cloud & Infrastructure

    Servers, deployment pipelines, monitoring and security — operated, not just configured.

    • Docker
    • Linux
    • Cloud
    • CI/CD

Principles

How we work.

Four principles decide how we design, build and run what we ship. They are the ones we would ask you to hold too.

  1. Engineering first

    Every technical decision has to serve the product. Architecture is chosen for what it must carry, and the reasons are written down.

  2. Product thinking

    Experience, architecture and business model are decided together, by people who understand all three.

  3. Built to operate

    A product is not finished when it ships. Monitoring, patches, backups and on-call are part of the contract, not an add-on.

  4. Simple by design

    Complexity belongs inside the system. It never belongs in the experience of the people using it.

Writing to us

What to put in your message.

  1. What you have built

    Links to code, products or write-ups you can share, and what your part in them was.

  2. What you want to work on

    The kind of problems you want to solve next — and the ones you would rather not.

  3. How you like to work

    Where you are based, the hours that suit you, and when you could start.