Dear Hiring Team,
Enterprise engineering orgs live or die on two things — the platforms their teams build on, and the operational discipline to keep them running. That is the work I have done at Cox Automotive for the past six years, and it is the lens through which I am evaluating a Staff-level seat on a team where that combination matters.
Over ten years I have shipped production software at every layer of the stack. A six-agent AWS Bedrock orchestration (Strands SDK + A2A protocol) that replaces hours of manual SRE dashboard triage with a single natural-language query across 40+ services. An IDE-native Model Context Protocol (MCP) server attributing P95 latency to the exact files and lines engineers rewrite, with a DNA-tagging correlation pattern linking 50+ event types through a single component identifier. Context Hub — an open-standard plugin marketplace unifying Claude Code and VS Code GitHub Copilot Chat for 100+ engineers across 25+ teams, shipping 197 skills, 3 agents, and 22 slash commands via one install. Copilot Proxy — a production Go gateway translating the full Anthropic Messages API to OpenAI Chat Completions, unlocking Claude Code CLI for a Microsoft-first org with no new Anthropic spend. A 400-component datacenter-to-AWS migration with $180K annual savings and zero production rollbacks. And an AWS FIS-driven chaos-engineering and GameDay program (MTTR 26–45 min) serving 30+ engineering teams, feeding the Production Readiness Review framework and SLO recalibration across the same 40+ microservices.
The through-line is Infrastructure-as-Code, Observability-as-Code, and Constitution-driven SDLC — platforms others build on, documented well enough that the team does not need me to operate them. Evidence-based engineering, human-in-the-loop consensus, and phase-gated governance are not slogans; they are how my changes ship. The same discipline that keeps on-call calm is what keeps AI acceleration from turning into AI chaos.
What makes the profile unusual for a Staff-level seat is how we grow the team around the platforms. On a 4-engineer team we host 2–3 interns every semester — engineering leadership's designated training ground — and over the past two years 8–12 interns have rotated forward into full-time software engineering roles across the broader organization. We run 1–2 enterprise-wide brownbags per quarter on AI coding agents, Observability-as-Code, chaos engineering, and MCP; principal engineers across the org consult the team for deep-dive engineering questions; and the team operates on the no-boundary principle: you build it, you own it, you run it — from design through incident response. Reliability rigor and cross-domain depth, taught hands-on from day one.
I would value thirty minutes to understand what your team needs from this role, and to walk through the multi-agent orchestration, the migration sequencing, the GameDay fault catalog, or the Observability-as-Code module library in whatever depth is useful. My calendar is open.