Order testing
Before
A command-line tool on one laptop. No record of what anyone ran.
After
An API, a portal and MCP tools for the whole order lifecycle. Other teams run it themselves, every action is audited, and it is smoke-tested nightly.
2026 Milestones
January to August 2026 • Self-service testing, four ways • A new service from design doc to production in one quarter
Impact Overview
4
Interfaces to one test flow
25+
MCP Tools Shipped
1 quarter
Design doc to production service
0
Downtime across two migrations
The Flagship: One Test Flow, Four Ways
One test flow (create an order, pick it, deliver it, cancel or refund it, plus the staff shifts around it), reachable four ways so that nobody has to wait for someone who knows the CLI.
before
Command-line tool
One laptop, engineers only
backbone
Go API
Full order lifecycle + delivery simulation
self-service
Portal page
Guided flows, no CLI
for AI agents
MCP · 25+ tools
Straight from Claude Code
Now used in production, with guardrails that keep test orders in a dedicated test location
Before and After
What changed for the engineers who use these tools.
Delivery testing
Before
Someone at a warehouse with a courier phone, coordinated across two teams.
After
One person and a browser, from courier sign-in to drop-off with live location.
Test accounts
Before
Made by hand and reused forever. Counted as real customers and sent real marketing email.
After
Minted on demand by a dedicated service, invisible to reporting and marketing, retired automatically.
API documentation
Before
Written by hand and drifting from what the services actually did.
After
An OpenAPI spec for every service, enforced in CI: if a service drifts, the build fails.
Engineering Accomplishments
Documentation & Knowledge Sharing
Technology Stack
Platform & DevOps
KubernetesGCPDockerArgoCDGitHub ActionsDataDog
AI & Tooling
MCPClaude CodeGemini CLIOpenAPI
Languages & Protocols
GoTypeScriptPythongRPCRESTSOAP
Curious about the details? Let's talk
Happy to walk through any of this in more detail.