5.4
PRs per engineer per week
Public resume · printable operating brief
Technical Product Manager | Engineering-Rooted PM
Platform reliability, developer productivity, and AI workflow acceleration.
Senior technical PM leading developer velocity strategy for 4,000+ engineers at Block, with a background spanning full-stack engineering, release excellence, and internal platform leadership.
Optimized for browser Save as PDF and tuned for a 2-page US Letter export.
01
Technical PM with 15+ years of experience building platforms that improve engineering velocity and developer experience at scale, backed by a BS in EECS from UC Berkeley and hands-on experience as a full-stack software engineer. Currently leading Developer Velocity strategy at Block across Square, Cash App, and Tidal, driving a 170% improvement in PR throughput, 99.90% deployment reliability, and 1,000+ weekly engineering hours saved through AI-assisted CI tooling. Proven at turning developer research and systems data into executive-level platform strategy, including material used for Board reviews and Investor Day.
02
5.4
PRs per engineer per week
170%
Improvement in PR throughput
99.90%
Deployment reliability
1,000+
Engineering hours saved weekly
3,200+
Developer survey responses per quarter
68%
Canary deployment adoption
03
Developer Velocity, CI/CD, Build Systems, Cloud Infrastructure (GCP), Canary Deployments, Deployment Reliability
DORA Metrics, SPACE Framework, Agile/Scrum, OKRs, Release Engineering, Incident Management
Full-Stack Engineering (C#, .NET, PHP, JavaScript, SQL), Elasticsearch, Machine Learning Classifiers, ATS/Data Systems
Roadmap Strategy, Executive Communications, Vendor Management, Stakeholder Alignment, Data-Driven Decision Making, Analysis
Anthropic Claude Code, OpenAI Codex, Snowflake, Looker, Tableau, Datadog, Splunk, Qualtrics
04
Platform Product Manager | Developer Velocity Program Lead, Platform and Foundational Engineering
Platform Product Manager | Release Engineering, Automated Testing, Centralized Authentication
Product Manager / Team Lead | US Refugee Admissions Program
Internal Product Manager / Technology Partner | Internal Tools, Engineering & Recruiting Platforms
Software Engineer → Technical Lead
05
University of California, Berkeley · Bachelor of Science, Electrical Engineering and Computer Science (EECS) · 2008
06
The resume above remains the canonical 2-page artifact. The modules below provide context, supporting metrics, and operating principles for evaluators who want proof behind the outcomes.
Context: Block needed a coherent definition of engineering velocity across Square, Cash App, and Tidal.
Challenge: Teams lacked a shared language for speed, responsiveness, and developer experience.
Intervention: Jason formalized DORA + SPACE metrics, created the master velocity dashboard, and made it central to weekly executive reporting.
Outcome: PR throughput rose from 2.0 to 5.4 PRs per engineer per week while DXI improved from 50 to 62 across all 16 measured drivers.
Context: Developer feedback existed, but it was fragmented and too small to drive confident investment decisions.
Challenge: Platform teams needed high-integrity qualitative data that reflected different engineering disciplines.
Intervention: Jason normalized survey operations, grew participation beyond 3,200 responses per quarter, and improved triage and follow-through.
Outcome: The survey became the primary data source guiding Platform Engineering investment and contributed to the largest single-driver satisfaction gain in program history.
Context: Build failures and fragmented CI systems created persistent developer toil.
Challenge: Teams were spending meaningful time diagnosing failures instead of shipping product work.
Intervention: Jason partnered with internal AI teams and platform engineers to roll out Actionable CI and bridge multiple CI platforms toward longer-term consolidation.
Outcome: AI-driven build resolution saved developers roughly 17% of the time spent fixing failed builds, returning an estimated 1,000+ hours weekly.
Context: Faster shipping only mattered if platform reliability stayed high.
Challenge: Canary adoption and auto-rollback usage were stalled because teams lacked enough validation confidence.
Intervention: Jason focused the roadmap on validation gaps, reliability checks, and process changes that increased release confidence.
Outcome: Canary adoption climbed from 27% to 68%, auto-rollback usage rose from 2% to 15%, and Block sustained 99.90% reliability during major vendor outages.
Context: Platform engineering needed a repeatable operating rhythm that protected teams from noise.
Challenge: Quarterly planning and request intake were not yet mature enough to align platform work with the highest-leverage developer needs.
Intervention: Jason authored the Release Excellence strategy, created the planning process, and implemented structured intake patterns that reduced low-priority interruption cost.
Outcome: CI build times fell by 16% to 40% across major repositories and teams hit SLA targets for the first time in more than a year.
Context: Meta needed internal tooling to support rapid growth and hiring at scale.
Challenge: Recruiting operations needed better prioritization, candidate context, and bottleneck visibility.
Intervention: Jason built a resume ranking classifier, a candidate profile aggregator, and KPI dashboards used across recruiting workflows.
Outcome: The systems recovered 2,000+ false negatives, reduced candidate research time from 15 minutes to 1 minute, and saved about 600 hours per month.
07
The blog ships inside the same Eleventy site so the resume can stay the canonical artifact while longer-form writing accumulates beneath it.
Why the site now includes a compact Eleventy-powered writing archive alongside the printable resume.