Consulting

Hands-on engineering inside your team: I scope the change, build it with you, ship it behind a rollout you can reverse, and hand it off.

Engagements

Modernization and migration delivery

Moving a system that can't stop off a legacy core, one funnel or market at a time.

What you get

  • A migration path with one stable entry point, a flag per funnel and a kill switch
  • The service code, written with your engineers
  • Verification gates for data that has to arrive intact
  • Runbooks for the cutover and the rollback

Evidence: Cart-checkout platform

Platform and reliability

Making on-call answerable: who owns what, what healthy means, and what to do first when it isn't.

What you get

  • An ownership map for every endpoint and component
  • One consolidated set of monitors with monitor-based SLOs
  • A triage guide for every monitor, required before it ships

Evidence: Checkout reliability

AI-native development and agent tooling

Coding agents working in parallel on one repository, with deterministic rules for who may touch which files, and AI coding models evaluated on real repository tasks.

What you get

  • Claim and conflict rules for agents that share a repository
  • Stale-work and diff-risk checks your hooks and CI can read
  • A written way of working: roles, one worktree per slice, a fresh review for every PR, a human merge
  • Repository-level evaluation: apply generated patches, run the tests, score the result

Evidence: AgentGrid

How an engagement runs

  1. Scope

    Agree what changes, what must not, and how we'll know it worked.

  2. Build with your team

    I write the code alongside your engineers, in your repositories and reviews.

  3. Ship behind a reversible rollout

    Flags, guardrails and a kill switch, so every step can be undone.

  4. Hand off

    Runbooks, triage guides and an owner for every part, so it keeps working after I leave.

Format

Engagement
Contract, full-time or part-time
Location
Remote, or on site in the Boston area

Start an inquiry