Open role

Member of Technical Staff, Control Plane (Founding)

Own the gating path that decides whether an autonomous action commits, rolls back, or escalates.

Team Control plane engineering

Location New York, NY

Type Full-time

Level Founding MTS / Staff-to-Principal equivalent

Compensation $260,000 – $340,000 base + 0.5%–1.25% equity + benefits

What we are building

Dipp AI Technologies is on a mission to close the gap between AI’s advanced reasoning capabilities and an enterprise’s ability to trust it with real work: verifiable, cost-disciplined, and in control of its own data.

We build Orcher, the agentic control plane that enforces Human-in-the-Role across seven components, and Dipp Intelligence, our Enterprise Superintelligence solution that compounds on verified execution.

Work directly with the founding team, building for customers from startups to Fortune 100 companies across industries. Help enterprises adopt frontier models, open weights and new compute providers without surrendering authority, economics or data control.

About the role

Orcher sits between enterprise AI agents and the systems of record they act on. Every directive passes through verification, policy evaluation, and an authority check before a single write commits. You will own that path end to end: the evaluation engine, the commit protocol, and the failure semantics when a check cannot be satisfied.

This is a founding technical role. You will make architectural decisions that persist for years — how directives are represented, how policy is compiled and evaluated under latency budgets, how partial failures are reconciled against downstream systems that do not support two-phase commit.

You will work directly with the founder and with design partners in banking, healthcare, insurance, and the public sector. Their auditors will read the behaviour of the code you write. We hire people who have shipped systems where being wrong had institutional consequences.

What you will do

  • Design and build the directive evaluation pipeline: verification, policy check, authority binding, commit, and evidence emission.
  • Define commit and compensation semantics against systems of record that offer no transactional guarantees.
  • Hold the latency budget for the gating path and keep p99 within the envelope enterprise workloads require.
  • Build the failure taxonomy — deny, escalate, hold, retry — and make each outcome legible in the audit ledger.
  • Write the reference implementation and internal specification other engineers build against.
  • Partner with design-partner engineering teams during deployment and turn field failures into permanent invariants.

What we look for

  • Deep experience building distributed systems where correctness mattered more than throughput.
  • Fluency in a systems language — Rust, Go, or modern C++ — plus comfort in TypeScript for control-plane tooling.
  • Practical knowledge of consensus, idempotency, exactly-once semantics, and reconciliation under partial failure.
  • Experience with policy engines, authorization systems, or rules evaluation at production scale.
  • The judgement to say no to a design that cannot be audited, and the writing ability to explain why.
  • Comfort working with regulated-industry customers and their security and compliance reviewers.

Experience

  • 8+ years building production backend or infrastructure systems, including 3+ years at staff level or equivalent founding scope.
  • Track record owning a system of consequence end to end — payments, trading, clinical, identity, or infrastructure control planes.
  • Prior experience at an early-stage company or as an early engineer on a zero-to-one platform is strongly preferred.

Education

  • BS, MS, or PhD in Computer Science, Electrical Engineering, or a related technical field.
  • Equivalent practical experience is fully accepted in place of a degree; we evaluate the systems you have built.

Compensation and benefits

  • Meaningful founding equity with a standard four-year vest and a one-year cliff.
  • Full medical, dental, and vision coverage for you and your dependents.
  • 401(k) with company contribution, and a home-office and hardware budget.
  • Annual budget for conferences, research, and publication of your own work.

How we hire

  1. 01Intro conversation with the founder (30 minutes).
  2. 02Systems design discussion on the gating path (75 minutes).
  3. 03Practical exercise reviewed together — no timed algorithm puzzles.
  4. 04Architecture and judgement panel with two engineers.
  5. 05References and offer, typically within two weeks end to end.