Tyler Wall @ ZocDoc

AI Sprint Intelligence: Built pre-grooming system using historical transcripts as KB. Double-blind validated at ±1 story point accuracy. 2.5x team velocity, 13% sprint efficiency gain, prevented production outage.

Migration Agent at Scale: Prototyped migration patterns for 300 endpoints in hours, automating 80% of boilerplate. Engineers freed for testing and edge cases. Platform leverage at scale.

QA from Zero: Built 0 → 1,500 automated test cases driven by business requirements from tickets and QA features, not AI-generated boilerplate. Deployment safety through coverage.

AI Governance: After AI agent modified routing tables breaking production, established read-only AI accounts and DevOps approval workflows. AI drafts full tickets with rationale for human review.

Paved Roads That Work: Built real-time debugging platform (Redis/Xdebug/BPF) that engineers adopted by choice. 95% MTTR reduction because it solved actual problems, not theoretical ones.

Platform ROI: Delivered $336K+ annual savings while improving reliability. The kind of platform investment that makes finance and engineering both happy.

Developer Metrics at Scale: Built 50 per-developer daily/weekly reports tracking adoption and bottlenecks per-ticket/per-feature/per-developer. Turned support overhead from 25% to <5% through data-driven tooling, not directives.

Deployment Safety: Led first load test in company history—5 sessions, zero failures. Created a culture where teams want to load test.

Strategic Influence: Single-handedly led Instacart integration and drove Shopify migration end-to-end. Advised executive leadership on platform roadmaps and build-vs-buy decisions.

AI Pioneer: Drove GPT-3 adoption (2022, pre-ChatGPT) demonstrating ROI that justified AI tooling budget organization-wide.

Cross-Functional Alignment: Worked with Operations, Customer Service, and Engineering to connect platform investments to business priorities. Platform decisions made with stakeholders, not for them.

Platform Benchmark: Built Operations team from 0 (solo) to 9 engineers across 3 squads, creating the platform other teams measured against for Testing, Stability, and Documentation.

Proactive Developer Empathy: Self-initiated DR-tolerant SDK now deployed company-wide. Solved pain points before they became blockers.

Fast Feedback Loops: In first 90 days, boosted performance 87% and established feedback loops that prevented regression.

Team Unblocking: Rescued failing project 6 months behind schedule by restructuring architecture and enabling 6-8 remote developers to deliver successfully.

Platform for Compliance: Delivered real-time quoting engine handling complex state-specific regulations—a platform engineers could build on without regulatory expertise.

Cross-Border Platform Engineering: Designed distributed architecture spanning AWS (US) and Aliyun (China). Solved latency challenges so engineers didn't have to think about them.

Self-Service Integrations: Built unified logistics engine integrating 8+ providers. Abstracted complexity so teams could ship without provider-specific knowledge.

Developer-Facing Payment APIs: Connected 19+ payment gateways into a unified interface. Engineers integrated once, supported everywhere.

Performance Engineering: Directed NewBalance.com performance initiatives improving speed and conversion. Measurable developer experience outcomes.

Fractional CTO: Operated as engineering leader for multiple clients. Established standards and practices that outlasted engagements.

Platform Automation: Led multi-channel sales automation achieving +1,700% YOY sales. A platform that multiplied team output.

DevEx Tooling Pioneer: Developed core development tools and coding standards that every project at the company ran on. Engineers inherited a working baseline instead of starting from scratch.

Early DevEx Champion: Implemented quality gates (linting, test requirements, coverage blockers)—one of the earliest developer experience initiatives at the company.

Shipping While Improving: In 90 days, delivered the only two new features. The quality gates I put in place stayed — other developers kept using them because they caught real issues.