Home/Company/Careers
Company

Sixty people. Still one named team on every account.

Big enough to staff several engagements properly, structured so the engineer who designs a system is still the one who runs it. Growing without losing that is the thing we are actually managing.

Send us something you builtHow we work

Headquartered in the United States · working worldwide

How hiring actually goes
four steps, no take-home you will resent
LIVE
StepWhat happensLength
A conversationabout what you have built, not your CV45 min
Read our codea real repository, and tell us what is wrong with ityour own time
Pair on somethingreal, paid, with the person you would work withhalf a day
Meet the teamall of them, and ask anything1 hour
4 steps, 1 paid, 0 unpaid take-homesan answer within a week, either way
4
Four steps, one of them paid
and no take-home you will resent
Step two, early

Here is some of our code. What is wrong with it?

This is a simplified version of the routing function from a lending platform we run. It compiles, it passes its tests, and it is wrong in a way that costs money. Click the line you think is the problem.

routing/assign.tsclick a line
1// assign.ts — picks the owner for an inbound lead
2export function pickOwner(lead: Lead, reps: Rep[]) {
3 const eligible = reps.filter(r => r.licensedIn(lead.state));
4
5 const ranked = eligible.sort((a, b) =>
6 a.openFiles - b.openFiles
7 );
8
9 return ranked[0];
10}
Take your time. There is one line that would lose a real business real revenue.
What it is like

Six things that are true here, including the awkward ones.

01

You will read more than you write. The first week of any engagement is reading somebody else's decisions.

02

You will be asked to say when something is a bad idea, including when we have already sold it.

03

You own what you build, afterwards — there is no support tier to hand it to.

04

You will own systems outright. There is a firm behind you, but no ticket queue to hand your work to.

05

Client work, not product work. The variety is real and so is the context switching.

06

We write things down. If you find documentation tedious, this will be a frustrating place.

Open roles

Three open. We hire when the work is real.

Not headcount targets — each of these exists because there is work we cannot do well without another person. No agencies, and no CV screen before a conversation.

Senior engineer — full stack

TypeScript, Postgres, Next.js
New Jersey or remoteopen+

WHAT YOU WOULD DO

Own a client platform end to end — data model, API, interface, and the decisions behind all three.
Sit in discovery. You will be on a client's floor in week one, not handed a spec in week four.
Write the boundary document, then build against it, then run what you built.
Say when something should not be built. That is part of the job, not a favour.

WHO WE ARE LOOKING FOR

Five or more years shipping production software people depend on.
Deep with TypeScript and relational data modelling. Postgres by preference.
Comfortable owning a system outright, with a team around you rather than above you.
Able to explain a technical trade-off to someone who does not write code.

WHO WE ARE NOT

Framework tourists. We care what you shipped, not which stack you prefer this year.
Anyone who wants to be handed tickets. There is no backlog groomed for you.
Within 90 days you will have shipped a slice a real user works in daily.Send us something you built →

Solutions engineer

Discovery, architecture, and the client relationship
New Jerseyopen+

WHAT YOU WOULD DO

Spend the first week of an engagement on the client's floor, watching how work actually happens.
Read their systems — every automation, field and integration — and write down what nobody documented.
Draw the current state and the intended state, and defend the difference to a room.
Stay involved through delivery, because the person who found the problem should see the fix.

WHO WE ARE LOOKING FOR

A background in software, operations or consulting where you had to understand somebody else's business fast.
Enough technical depth to read a data model and know when it is wrong.
Genuinely good at asking the second and third question.
Willing to travel occasionally. The floor is the job.

WHO WE ARE NOT

Pure sales engineers. This role produces findings, not proposals.
Anyone who needs a discovery template. Every engagement is different.
Within 90 days you will have run discovery on your own engagement.Send us something you built →

AI engineer

Agents with guardrails, in production
New Jersey or remoteopen+

WHAT YOU WOULD DO

Build assistants that do the useful part and hand back — the stand-down condition matters more than the model.
Implement guardrails in code rather than in prompts, because a model can be talked out of an instruction.
Instrument cost per conversation, because an agent nobody can price is an agent nobody controls.
Work on real production systems with real consequences, including compliance ones.

WHO WE ARE LOOKING FOR

Shipped something using an LLM API that real users touched, not a demo.
Strong Python or TypeScript, and comfortable with the plumbing — queues, retries, idempotency.
Sceptical about autonomy. The interesting design work is deciding what the agent may not attempt.
Interested in evaluation, not just prompting.

WHO WE ARE NOT

Prompt engineers. This is software engineering that happens to call a model.
Anyone whose portfolio is a chatbot wrapper.
Within 90 days you will own an agent running against a live client system.Send us something you built →
Questions

What people ask before applying.

Are you hiring right now?

Yes — three roles, listed above. Each exists because there is work we cannot do well without another person, so when they close the page will say so. Speculative applications are still read and answered.

Is there an unpaid take-home?

No. There is a paid half-day pairing on something real, with the person you would actually work with.

Remote or in person?

Both work. The diagnose stage means being on a client's floor sometimes, so travel is occasional rather than never.

What is the team size?

Sixty-plus across delivery, data and AI. Engagement teams are four to eight, so the unit you work in stays small even though the firm is not.

What will I actually work on?

Client systems — CRM platforms, integrations, AI agents, reporting. Real production software with real users, not internal tooling.

How long does the process take?

About two weeks, and you get an answer within a week of the last step either way.