Careers

Small team. Real problems.

We hire slowly and specifically. If none of the listed roles fit but you build things we would find interesting, apply anyway and say so — that route has worked before.

Open roles

Where we are looking

Every role is remote-first within the US. On-site work happens only where an engagement requires it.

  • Backend Engineer — Agent Infrastructure

    Full-time · Contract consideredRemote (US)

    Open

    Identity, authorization, and audit for autonomous systems. You will work on the policy evaluation path, credential lifecycle, and the tamper-evident trail — the parts where correctness matters more than throughput.

    GoTypeScriptPostgresOIDCOpenTelemetry

  • Automation Engineer — Workflows & Voice

    Full-time · Contract consideredRemote (US)

    Open

    Sourcing and enrichment pipelines, CRM integration, and realtime voice agents. Comfort with messy third-party APIs, and a low tolerance for automations that fail silently.

    TypeScriptPythonn8nTwilioPostgres

  • Full-Stack Engineer — Product

    Full-timeRemote (US)

    Open

    Web applications and internal tools across every division. Strong opinions about accessibility, real-device performance, and shipping something small that works over something large that nearly does.

    TypeScriptNext.jsReactPostgres

  • iOS Developer

    Contract · Project-basedRemote

    Open

    Native iOS in Swift and SwiftUI, shipped through TestFlight to the App Store. Portfolio matters far more than years — send something people actually used.

    SwiftSwiftUIXcode CloudTestFlight

What we look for

Four things, and they are not on your résumé

We do not filter on degrees, years, or company names. These are the actual signals.

You debug from the mechanism

When something breaks you form a hypothesis about why, then test it — rather than changing things until the symptom disappears.

You measure before you claim

"It's faster" is a hypothesis. A number from a wall-clock measurement of the real path is an answer.

You write for the next person

Code, commits, and docs that someone else can pick up in eighteen months without an archaeology session.

You can say you were wrong

Quickly, without drama, and without needing to be talked into it. It is the single strongest predictor of someone worth working with.

Apply

One form, no portal

No account to create, no résumé parser, no eight-stage pipeline. One form, read by a person, answered either way.

One link is enough. We would rather see something you built than a formatted résumé.

Only relevant to defense work. Never required for any other role, and never a factor in how we read the rest of your application.

This is the part we actually read. Specific beats polished — the debugging story is more interesting than the feature list.

Read by a person. You get an answer either way.