Skip to content

Careers · Punjab, Pakistan · Remote

Engineering where being wrong has consequences

We build systems that post to general ledgers and agents that touch them. That constrains how we work, and it is the most interesting thing about the job.

Open roles

Nothing open right now

We are not running an always-on pipeline of listings for roles that do not exist. If you are strong in one of the disciplines below, write to us anyway — we have hired that way before.

Disciplines

Three kinds of work

ERP engineering

AL and X++ extensions, Odoo Python and OWL, posting logic, migration tooling. You will read more accounting than you expect.

Agent infrastructure

Dart and Rust. Tool contracts, policy evaluation, durable execution — the parts that have to hold when a model is wrong.

Product engineering

Flutter and TypeScript. Client work where the interface is the product and the deadline is somebody else's launch.

Before you apply

What this job actually involves

Four things people are surprised by. Better to be surprised now.

01

You will talk to clients

There is no account layer here. The engineer who builds it runs the review, which means explaining trade-offs to a CFO in language they can act on.

02

You will write things down

The 33 published blueprints are written by the people who did the work. Writing is part of the engineering, not an afterthought someone else handles.

03

The ledger does not forgive

A rounding error in a marketing site is a bug. A rounding error in a general ledger is an audit finding. Most of what we do is careful for a reason.

04

Small team, real ownership

You will own surfaces end to end, not tickets. That is the upside and the cost of a team this size.

Apply

Send something you built and what was hard about it.

Not a cover letter. A repository, a write-up, a migration you survived — and the part you would do differently.