How we work

Consultants here are employed, not gig-staffed, and most engagements run remotely from wherever you are. You work alongside a principal rather than underneath a delivery layer, and you keep the same engagement from scoping through handoff — which is the part most consultancies get wrong.

Support is real: a certified project manager handles scheduling and status, and systems administration keeps our own environment out of your way. You are hired to do the technical work, not to chase timesheets.

Getting in touch

Send us what you’ve built and how you like to work. A repository, a design doc, or a description of a problem you fixed is far more useful to us than a résumé. Use the contact page to reach us, and say whether you’re writing about a role or a partnership.

What we look for

Engineers who write things down

Most of the value we deliver is a decision someone can still understand six months later. If you find the writing part tedious, this is not a good fit.

Depth over breadth

We would rather work with someone who knows AWS networking or identity properly than someone who has touched every service once.

Comfort in regulated environments

HIPAA, SOC 2, PCI DSS, and FedRAMP work comes with evidence requirements and access controls that slow everything down. Knowing that going in matters more than holding a specific certification.

People who can face a client

Our consultants sit in the room with the people paying for the work. That means explaining a tradeoff to a CFO as readily as to a staff engineer, and saying "I don't know yet" when that is the honest answer.

Partner firms with a different specialty

We turn down work that sits outside what we do well. Having someone good to hand it to is worth a lot to us, and we expect it to run both ways.

Introduce yourself.

We keep a short list of people and firms we'd call first. If that sounds like you, tell us what you do and how you'd want to work together.