Work that actually matters.

Mainframes that clear payments. AI that solves real business problems. Workflows nobody has automated before. Hard problems, real systems, and a team that enjoys the work.

Senior by defaultYou are on the program, not behind it.
Real systemsProduction, change control, consequences.
Two hour capNo take home longer than that, and we pay for it.
Remote friendlyWith travel where the work requires it.

Five things we look for.

You have shipped inside a large organization You know what a change advisory board is, and you have survived one. That experience is hard to hire and impossible to fake.
You explain things plainly Half of this work is making a room of non-engineers comfortable with a decision. If you cannot do that, the engineering does not land.
You are comfortable saying no To us and to clients. If we are about to recommend the wrong thing, we want the person who can see it to say so in the meeting, politely.
You want to hand it over The goal is the client's team running it without us. If you would rather be indispensable, this is the wrong firm.
You want to automate the repetitive tasks Our model only works if the people doing the work would rather build the thing that removes it than keep doing it by hand.
Recognize yourself? Tell us what you have built. We read every note and we reply, including when the answer is no. Send us a note

Four steps. You will never be left wondering.

/01

A conversation

Forty five minutes with someone who does the work. Not a screening call with a recruiter.

/02

A real problem

Something close to what we actually do. Capped at two hours, and we pay for your time.

/03

Meet the team

You talk to the people you would work with, and you ask us the hard questions.

/04

Decision

Within a week of the last conversation, either way, with a reason.

We hire ahead of the requisition.

A posted role is not the only way in. When we meet someone we want to work with, we find a way to work with them. If what is above sounds like you, send a note and tell us what you have built.

We read every one and we reply, including when the answer is no.

Where are the roles based?

Remote first, with travel to client sites where the work requires being in the room. Mainframe programs require it more often than AI ones.

What does the work actually look like?

Some weeks it is deep in a z/OS codebase. Some weeks it is building an accelerator pack that fifty clients will use. Some weeks it is explaining to a risk committee why a design is safe.

Tell us what
you have built.

A short note is enough. Include one thing you shipped that you are still proud of, and one thing that went badly.