Skip to content

Careers

Build AI where the work happens.

Join engineers who work directly with operators and own systems from the first workflow audit through production. Small team, senior people, real operations.

See open rolesRemote-first across Europe and Asia

How we work

What the job asks of you

Own the problem
Work from business reality, not tickets stripped of context.
Work close to operations
Understand how the process actually runs before deciding what to build.
Ship production
Success is a system working reliably in the business, not a demo.
Use judgement
AI where it belongs. Deterministic systems where they are better.

Open roles

Five seats, two teams

Every role works with clients directly. None of them is a back-office seat.

Hiring process

Five steps, no recruiter

  1. 01

    Application

    Tell us what you have built and where you want to go next. We read every application ourselves. Expect a reply either way within a week.

  2. 02

    Intro call

    30 minutes with our engineers, not a recruiter. We talk through your work and you get honest answers about how we operate.

  3. 03

    Technical conversation

    60 to 90 minutes on scenario-based problems to understand your judgement, system design, and how you reason through trade-offs.

  4. 04

    Working session

    A paid half-day on a scoped piece of work with the people you would actually be working with. It goes both ways: you get to see how we run before you commit.

  5. 05

    Offer

    Compensation is benchmarked to your market and reviewed annually. We make the offer and the reasoning behind it clear in one conversation.

What you get

The practical side

  • Remote-first, with genuinely flexible hours across European and Asian time zones
  • Direct client exposure from your first engagement, not after two years of internal work
  • Budget for conferences, courses, and the model providers you need to stay current
  • A senior engineer paired with you for your first two engagements
  • Paid time to write. Several of the pieces on our blog started as internal engagement notes
  • Outcome-driven culture. We measure what shipped, not hours logged