Why work here

You will work on systems that people depend on to do their jobs — crews in the field, assessors handling claims, operators watching a network. That constraint makes the engineering more interesting, not less: you cannot hand-wave reliability when someone is standing on a site waiting.

We are deliberately small enough that you will see an engagement end to end, and structured enough that you will not be the only person who understands what you built.

  • People who ask what problem the work is solving before starting it
  • Comfort with operational reality — legacy systems, constraints, imperfect data
  • Willingness to write things down so the next person is not stuck
  • Directness delivered with care, including upward
Colleagues working at long tables in a bright open-plan office
Our process

How we hire

Four steps, usually inside three weeks. We tell you where you stand at each one.

1

Introductory conversation

Thirty minutes, both ways. What you are looking for, what we actually do, and whether there is a fit worth pursuing.

2

Practical discussion

A conversation about real work — a system you have built, a decision you regret, a trade-off you would make differently. No whiteboard algorithms.

3

Meet the team

Time with the people you would work alongside, including space to ask them things you would not ask a hiring manager.

4

Offer

A written offer with the salary band, the role, and who you report to. We do not negotiate against other candidates.

Open roles

Current openings

No roles listed right now

We are not advertising specific vacancies at the moment, but we do keep good applications on file and hire when the right person appears. Send us a note about what you do and what you are looking for.

Speculative applications

Email [email protected] with the subject line “Careers”, a short note, and whatever best shows your work — a CV, a repository, a write-up of something you built.

Locations

Auckland, New Zealand

Manila, Philippines