Global Story Index
Quick Reference
| # | Company | Story | One-Liner | Dimensions | Link |
|---|---|---|---|---|---|
| 1 | Capital One | Snapshot Generator | Simplified CDC init, saved 8 teams months of work | Execution, Optimization | Highly impactful - Snapshot generator |
| 2 | Capital One | VP Trust – Influence Without Authority | Won over resistant VP overseeing 20 teams | Influence, Leadership | Difficult Person - Durable Executions VP |
| 3 | Capital One | Claims Modernization – Cross-Team Leadership | Stabilized 16 contractor teams, delivered Feb milestone | Execution, Leadership, Alignment | Delay - Claim modernization |
| 4 | Capital One | Claims Modernization – Legacy Decommission | Migrated monolith, eliminated stuck claims ($34M/yr) | Strategy, Risk Mgmt, Reliability | Delay - Claim modernization |
| 5 | Capital One | Claims Modernization – Milestone Delay & Recovery | Flagged Dec delay 6wk early, recovered Feb | Execution, Ownership, Decision | Delay - Claim modernization |
| 6 | Capital One | Claims Modernization – Conflict Resolution | Resolved Lambda granularity debate between tech leads | Collaboration, Influence | Delay - Claim modernization |
| 7 | Capital One | Fraud Defense – Team Transformation | Upskilled team migrating EMR→Glue, incidents -70% | Leadership, Mentorship, Efficiency | Upskilling - Data Engineering |
| 8 | Capital One | Fraud Defense – Glue Pipeline Incident | Contained $3M fraud loss incident in <24h | Reliability, Incident Response | Upskilling - Data Engineering |
| 9 | Capital One | VP Trust – Temporal Adoption | Shifted exec direction to Temporal as enterprise pattern | Strategy, Influence, Exec Alignment | Difficult Person - Durable Executions VP |
| 10 | Temporal Evaluation | Influenced partner team away from SQS/Lambda to Temporal | Strategy, Influence, Decision Making | Pinterest - Infragov modernization - wider | |
| 11 | Budget Planning (Trust During Onboarding) | Shipped prod system in 5mo, earned cross-org trust month 1 | Execution, Trust, Leadership | Pinterest - Infragov modernization - wider | |
| 12 | dbt Company-Wide Introduction | Introduced dbt to Pinterest via platform partnership | Strategy, Evangelism, Influence | Pinterest - dbt Company-Wide Introduction | |
| 13 | Developer Tooling That Scaled | Built Presto adapter + DuckDB env, 100× faster, adopted org-wide | Initiative, Efficiency, Platform Thinking | Pinterest - Developer Tooling That Scaled | |
| 14 | PagerDuty Reliability | Replaced email paging with API integration, 200→5 pages/mo | Reliability, Mentorship | Pinterest - PagerDuty Reliability | |
| 15 | Cross-Org Platform Migration | Migrated 6 platforms in 6mo with 2 engineers, coordinated 10-12 teams each | Execution, Cross-Org, Delivery | Pinterest - Cross-Org Platform Migration | |
| 16 | Cost Hierarchy (Beyond OKR) | Solved re-org breakage across 80 pipelines, not on OKR | Initiative, Influence | Pinterest - Infragov modernization - wider | |
| 17 | DBT Migration (Productivity) | Replaced 50 copy-paste pipelines with dbt macros, velocity ×3 | Execution, Efficiency | Pinterest - Infragov modernization - wider | |
| 18 | Credimi | COVID Decision Under Pressure | Scaled 400→1300 loans/mo in 6 weeks during COVID | Execution, Decision, Urgency | Move fast - Credimi during Covid shutdown |
| 19 | Sapient | Stakeholder Misalignment (Failure) | Lost sight of real users on Gates Foundation project | Learning, Stakeholder Mgmt | Failure Example - Stakeholder misalignment |
Detailed Stories
1. Capital One – Snapshot Generator (Org-Level Impact)
S: May → Jul 2024 | Dist. Eng., Capital One Fraud Modernization. 10 teams (~80 engs) blocked: CDC init took 30 days per topic. T: In 12 weeks, enable instant startup of real-time read side to unblock Dec launch. A1 – Investigate: Found nightly exports not point-in-time; 30d lag unavoidable in current design. A2 – Prototype: Built Spark-based snapshot generator using event history to rebuild state quickly. A3 – Validate: Single-topic POC completed in hours vs 30d; verified by 3 team leads. A4 – Scale & Adopt: Parameterized logic across 33 topics; added monitoring + runbooks; shared docs org-wide. R: Init time 30d → 10 min; 10 teams unblocked; technique reused in 3 modernization programs. TRAITS: Execution • Optimization • Reliability (Q 2 10 15 34)
2. Capital One – VP Trust: Influence Without Authority
S: Jan → Sep 2024 | Dist. Eng., Capital One Core Modernization. Peer VP (20 teams) resisted Temporal orchestration → risk of deadline slip. T: Win buy-in within 9mo and move his org to Temporal without authority. A1 – Understand: 1-on-1s with VP + mgrs → fear of delay if tech failed. A2 – Build Proof: POC Temporal workflow → deploy 2wk → 3d speedup. A3 – Influence Chain: Engaged trusted mgrs early + co-ownership of approach. A4 – Pilot & Scale: Low-risk team 2wk trial → success → rollout to 20 teams. R: VP became champion; Temporal standardized across 20 teams; deploy time ↓ 70%. Used same method to influence 2 other VPs. TRAITS: Influence • Leadership • Stakeholder Mgmt (Q 11 12 13 24)
3. Capital One – Claims Modernization: Cross-Team Leadership
S: Sep 2024 → Feb 2025, Dist. Eng. Capital One Fraud Tech. 16 contractor teams (≈250 eng) rushed after Discover deal; ambiguous ownership. T: Stabilize and deliver critical workflows under 6-month timeline without formal authority. A0 – Pre-Exec: Audited 5 cross-team handoffs + reviewed 70 PRs → identified testing / ownership gaps. A1 – Define Structure: Mapped dependencies, drafted RACI matrix shared with VPs. A2 – Uplevel Leads: Ran code reviews + showed Ports/Adapters pattern through live refactor. A3 – Quality Push: Introduced unit + contract tests mandatory before integration. A4 – Delivery: Flagged Dec delay 6wk early → reset scope + coached teams for Feb launch. R: Feb milestone on time; first phase eliminated stuck claims ($34M/yr efficiency). Patterns replicated in 2 later modernizations. TRAITS: Execution • Leadership • Alignment (Q 6 14 16 30 39)
4. Capital One – Claims Modernization: Legacy Decommission Strategy
S: 2024 Q4 → Q1 2025. Legacy Java monolith (1M claims ≈ 50M risk). T: Within 3 months, migrate to Lambda Router + Step Functions w/out downtime or data loss. A1 – Map + Plan: Cataloged 5 resolution strategies; pin-pointed dual-write fault zones. A2 – Design Router: Workflow-agnostic routing policy by strategy; idempotent payloads + audit IDs. A3 – Pilot: Cut over 2 strategies (40% volume); shadow diffs verified 0 state drift. A4 – Operationalize: Runbook + rollback templates → 16 teams trained in 2 weeks. R: Stuck-claim rate 0% on migrated flows (~$20M risk removed); pattern became Fraud Tech standard. TRAITS: Strategy • Risk Mgmt • Reliability (Q 5 6 11 28 29 30)
5. Capital One – Claims Modernization: Milestone Delay & Recovery
S: Joined Sep 2024 into project started Jun; first deadline (Dec) already at risk. T: Assess and communicate delay within 30 days → recover Feb release. A1 – Audit: Found over-granular Step Functions (>30 states) → slow + fragile. A2 – Report: End Sep → VP review presenting quality gaps + mitigation plan. A3 – Redesign: Rebuilt 2nd workflow (Ports/Adapters; Lambda OOP; Step Fn for durability only). A4 – Deliver: Feb release on time + reusable testing/obs template for others. R: Dec delay acknowledged early (no surprise); Feb delivered on schedule, 0 stuck claims (~$20M saved). Lesson → lead with early risk escalation on all later projects. TRAITS: Execution • Ownership • Decision (Q 16 18 24)
6. Capital One – Claims Modernization: Conflict Resolution Between Tech Leads
S: Jan 2025. Two tech leads debating Lambda granularity (blocking workflow release). T: Resolve conflict in 1wk and standardize pattern across teams. A1 – Facilitate: Set joint session reviewing Step Fn→Lambda RPC semantics. A2 – Clarify: Compared approach to gRPC oneOf pattern; showed state cost of extra Lambdas. A3 – Decide: Consensus → single Lambda per activity type for traceability. A4 – Scale: Published design standard repo used by 5 teams. R: Conflict closed pre-launch; consistent Lambda pattern org-wide. TRAITS: Collaboration • Influence • Communication (Q 37 11 12)
7. Capital One – Fraud Defense: Team Transformation
S: 2024 Q3 → Q1 2025 | Dist. Eng., Capital One Fraud Defense Authoring. Team (12 engs) migrating EMR → Glue without big-data skills; system unstable, 5000 line YAML pipelines. T: Within 3 months, stabilize Glue jobs and build a self-sufficient team able to ship new fraud defenses independently. A0 – Assess: 1wk audit → Spark UI unused; jobs ran 1 executor (qa config in prod). A1 – Upskill: Built hands-on Spark/Glue curriculum + weekly labs. A2 – Modernize: Introduced DBT for SQL defenses (modularity + testing + lineage). A3 – Simplify: Replaced custom StepFn orchestration with Glue Workflows (-60% complexity). A4 – Mentor & Scale: Paired tech lead through 3 cycles → independent + coaching others. R: Incidents 40 → 12/mo (-70%), runtime ↓ 35%, $25M fraud prevented. Same training kit rolled out to 2 more teams. TRAITS: Leadership • Efficiency • Mentorship (Q 19 20 21 22 23 38)
8. Capital One – Fraud Defense: Glue Pipeline Incident Recovery
S: Oct 2024. Fraud Defense Spark pipeline failed 1 week after credit-card launch → ≈ $3M fraud loss. T: Contain incident within 24h and prevent reoccurrence org-wide. A0 – Assemble Response: Formed SWAT workgroup (Data, Infra, Fraud) same day; defined blast radius + owners. A1 – Root Cause: Analyzed Spark UI → 30:1 partition skew causing OOM on 1 executor. A2 – Stabilize Fast: Repartitioned data + autoscale executors; service restored in 18h. A3 – Institutional Fix: Wrote Spark tuning guide + post-mortem template; added skew alerting dashboard. A4 – Upskill: Led debug workshops for 3 teams → incidents self-diagnosed after. R: Outage resolved < 24h, 0 recurrence 12mo; playbook adopted by 4 teams + Fraud Platform on-call. Lesson → treat incident as systemic learning moment. TRAITS: Reliability • Collaboration • Leadership (Q 9 27 29 19 38)
9. Capital One – VP Trust: Temporal Adoption for Core Mod
S: Q4 2024 | Dist. Eng., Capital One Core Modernization. Org leaning on event-driven SQS/Lambda design for core account workflows. T: In < 2mo shift executive direction to Temporal orchestration as enterprise pattern. A1 – Assess: Mapped 15 async steps / 8 integrations → fragile state mgmt & months debug risk. A2 – POC: Built Temporal Saga for account booking; auditable + rollback in minutes. A3 – Address Consistency: Demoed strong-read API via Temporal signal + read-side materialization. A4 – Align Execs: Presented latency ↓ 70%, failure ↓ 90%; reframed as risk reduction not tech debate. R: Adopted as enterprise standard across Core Mod; 20+ teams migrated; code complexity ↓ 40%. Pattern carried to later modernizations. TRAITS: Strategy • Influence • Exec Alignment (Q 12 13 31 40)
10. Pinterest – Temporal Evaluation
S: May → Jun 2023 | Staff Eng., Infra Governance team. Partner team building entitlement platform leaned toward SQS/Lambda choreography. Risk = distributed state mgmt nightmare + no observability. T: In 3 weeks evaluate alternatives and influence architecture choice without authority. A1 – Analyze Options: Mapped SQS/Lambda, Airflow, Temporal → benchmarked state visibility, latency, error recovery. Found queues = manual compensation, poor traceability. A2 – POC: Built Temporal workflow for budget reservation Saga; demo rollback & state query. Validated low latency (< 200ms vs 3 min Airflow). A3 – Align Team: Presented to entitlement leads; acknowledged their SQS expertise, framed Temporal as safer for distributed tx. Let them run both approaches 1 week → Temporal wins observability metrics. A4 – Document Decision: Wrote trade-off doc (pros/cons per option); submitted to architecture review board. R: Team adopted Temporal; 6mo debug saved, failure handling standardized. Decision template reused for 2 tech evaluations. TRAITS: Strategy • Influence • Decision Making (Q 7 11 31 40)
11. Pinterest – Budget Planning (Trust During Onboarding)
S: Aug → Dec 2023 | Month 1 of onboarding. Infra Gov team owning budget-aware provisioning. 80 tables + 50 pipelines duplicated; no tests; contractors underperforming. T: Ship production system in 5mo and earn cross-org trust (Finance, Platform, Data). A0 – Research / Trust Map: Met each org → Finance wanted auditability, Platform accuracy, Service owners simplicity. Noted no shared vision. A1 – Design w/ Quality Front-Load: Documented trade-offs (MVC vs Ports/Adapters) → chose Ports/Adapters for testability of junior team. A2 – Pre-Exec Pilot: POC GraphQL hierarchical queries + Cedar authz for audits. Used early feedback to lock design. A3 – Build / Launch: 6-stage approval workflow, audit changelog, real-time GraphQL subscriptions. Integrated Docker Compose in Bazel for local testing. A4 – Operationalize: Runbooks + monitoring; paired w/ junior engs to hand off ownership. R: Prod launch on schedule; 0 incidents; pattern reused by 2 systems. Established cross-org trust in first quarter. TRAITS: Execution • Trust • Leadership (Q 4 11 23 24 36)
12. Pinterest – dbt Company-Wide Introduction
S: 2023 | Staff Eng. Infra Gov. Pinterest had zero dbt adoption company-wide. 150+ tables, monolithic templated SQL (30+ CTEs, 500+ lines), no unit testing. System allocating $700M/year in cloud spend couldn’t be safely changed. T: Introduce modern data modeling discipline to Pinterest and make it viable within Spinner (heavily customized Airflow fork). A1 – Diagnose: Identified missing modeling discipline as root cause. Wrote influential paper proposing a new logical model that decoupled attribution from aggregation. A2 – Pilot: Brought dbt to the team; proved value on first platform migration. A3 – Partnership: Engaged Data Platform team; they built initial DAG renderer. I extended it with Iceberg WAP support and additional metadata for our use cases. A4 – Evangelize: Shared results across Infra Governance; other teams adopted the dbt-on-Spinner pattern. R: dbt became standard for Infra Governance pipelines. 6 platforms migrated in 6 months with 2 engineers. Pages 200/mo → 5/mo. SLA breaches → 0. TRAITS: Strategy • Influence • Evangelism (Q 3 12 38 40)
13. Pinterest – Developer Tooling That Scaled Company-Wide
S: 2023 | Staff Eng. Infra Gov. Spark-based dev workflow had 5-min minimum latency per iteration; engineers avoided running tests locally. T: Unblock team velocity without waiting for Data Platform team’s roadmap. A1 – Presto Adapter: Built custom dbt adapter wrapping official dbt-presto for Pinterest’s custom authentication layer. Dev/test in seconds vs 5-min Spark. A2 – DuckDB Local Env: Wrote sampling scripts to create local DuckDB from production data. Engineers could run dbt models and tests offline. A3 – Tag Workflows: Designed tag-based project structure so multiple independent platforms could be managed as a single dbt project but tested as isolated subsets. A4 – Handoff: Documented and shared tooling; didn’t gatekeep. R: ~100× faster feedback loops; adopted org-wide. Testing went from avoided to default behavior. TRAITS: Initiative • Efficiency • Platform Thinking (Q 10 19 20 38)
14. Pinterest – PagerDuty Reliability Overhaul
S: 2023 | Staff Eng. Infra Gov. ~200 PagerDuty pages/month. Email-based paging with regex parsing to infer failures. No routing to owning teams. T: Replace paging system with proper failure classification and routing. Used as development opportunity for junior engineer new to Airflow/infra entirely. A1 – Diagnose: Mapped failure modes. Most pages were noise: upstream platform data issues triggering attribution alerts. A2 – Joint Design: Paired with junior on design. Walked them through Airflow callback internals, PagerDuty API model (incidents, services, escalation policies), low-level PD client. A3 – Ownership Transfer: Junior owned implementation. I reviewed and coached through challenges—callback handler structure, incident key mapping, routing logic testing. They built the classification: upstream → platform team; attribution → our team. A4 – Growth: Junior became team’s go-to for PagerDuty/alerting. Independently owned next operational tooling improvement. R: 200 pages/mo → 5. Failures route to owning team. Junior went from zero infra experience to independently owning operational tooling. TRAITS: Reliability • Mentorship • Leadership (Q 21 28 29)
15. Pinterest – Cross-Org Platform Migration
S: 2023-2024 | Staff Eng. Infra Gov. 12 platform teams each owning usage data for cost attribution. Old setup: bespoke SQL per platform, ~1 year to onboard. T: Migrate 6 platforms to new dbt-based setup while coordinating with ~10-12 upstream teams per platform. A1 – Standardize: Defined repeatable migration pattern: onboard usage data → validate chargeback model → replace legacy SQL → verify cost attribution. A2 – Engage: Met each platform team to understand data delivery contracts, cadence, constraints. A3 – Execute: 6 platforms in 6 months with 2 engineers. Each migration validated financial correctness for C-level reporting. A4 – Scale Pattern: Documented process. Currently onboarding a platform not in original implementation. R: Per-platform onboarding ~1 year → ~1 month. 50% of system migrated. SLA breaches → 0. TRAITS: Execution • Cross-Org Influence • Delivery (Q 14 16 39)
16. Pinterest – Cost Hierarchy (Stepping Up Beyond OKR)
S: Mar → Jun 2023. Org reorgs broke 80 cost pipelines; Finance spent weeks manual fixing. Not on my OKR.
T: Solve structural problem in under 3mo w/out ownership mandate.
A1 – Research: Mapped roll-up logic across 50 pipelines; dup everywhere.
A2 – Design: Proposed cost_center_hierarchy table (parent/child + effective dates).
A3 – Align: Met Finance lead; demoed simple org-change update.
A4 – Implement: DBT dimension + traversal macros → replaced 5 pipelines initially.
R: Org change weeks → minutes; pattern reused 50 pipelines; concept replicated to 2 other hierarchies.
TRAITS: Initiative • Influence (Q 11 31 32)
17. Pinterest – DBT Migration (Improving Productivity)
S: 2023 | Staff Eng. Infra Gov. 50 Python/SQL pipelines 90% duplication → velocity collapse. T: In 6mo, replace copy-paste jobs with reusable DBT macros. A1 – Research: Cataloged 50 pipelines → grouped by pattern (cleanup, join, agg). A2 – Plan: 3-phase migration (macro → native → multi-tenant). A3 – Pilot: AWS platform subset 15 pipelines; validated lineage + CI/CD. A4 – Scale: Built macro library + auto validation on PRs; ran team training session. R: Dev cycle weeks → days; velocity × 3; pattern adopted by adjacent teams. TRAITS: Execution • Efficiency (Q 10 19 20)
18. Credimi – COVID Decision Under Pressure
S: Mar → May 2020 | CTO at Credimi (digital lender, €2B loans issued). COVID lockdown paralyzed banks; SMBs needed funds in days. T: Within 6 weeks, scale platform from 400 → 1300 loans/mo while keeping credit risk controls intact. A1 – Rapid Assessment: Met Risk & Ops; identified bottlenecks; segmented requests (auto-approve / manual / reject). A2 – Rule Design: Created auto-decision engine: good history + < €50k → auto-approve; high-risk sectors → manual. A3 – Stakeholder Buy-in: Presented to 5 bank partners; aligned on daily risk reporting + escalation process. A4 – Pilot → Scale: Launched with 1 bank; validated defaults; scaled to all 5 within 3 weeks. R: 1300 loans/mo (3× baseline), 97% satisfaction; became Generali’s emergency-funding platform. TRAITS: Execution • Decision • Urgency (Q 17 26 33)
19. Sapient Bioanalytics – Learning from Failure
S: 2018 → 2019 | Head of Software, $15M Gates Foundation project. Funder wanted analytics features; grantees needed simple data tools. T: Deliver usable platform in 4 months balancing funder vs user needs. A1 – Early Mistake: Focused solely on Foundation feedback → ignored end users. A2 – Miss & Impact: Released MVP meeting funder criteria but grantees couldn’t use it. A3 – Recovery: Re-engaged users via bi-weekly office hours + shadow sessions; logged pain points. A4 – Redesign: Simplified flows + tool integration; ran joint UAT with grantees. R: Platform adopted 3mo later; 40% features redesigned; stakeholder trust restored. Lesson → always involve end users when funder ≠ user. TRAITS: Learning • Stakeholder Mgmt (Q 8 35)
Dimension Quick-Lookup
| Dimension | Stories |
|---|---|
| Strategy / Technical Vision | 2, 9, 10, 12, 16 |
| Complex Problem Solving | 1, 8 |
| Cross-Functional Influence | 2, 3, 6, 9, 11, 15 |
| Execution / Delivery | 1, 3, 4, 5, 7, 15, 17, 18 |
| Leadership / Mentorship | 3, 7, 8, 11, 14 |
| Scalability / Reliability | 4, 8, 14 |
| Decision-Making / Trade-Offs | 5, 10, 16, 18 |
| Communication / Evangelism | 6, 12, 13 |
| Initiative / Beyond OKR | 13, 16 |
| Failure / Learning | 19 |