Owned partner-tier scoring v2 end-to-end. RFC, build, ship, monitor. 12 weeks. Adoption 92.9% within a quarter.
Eng-PM hybrid cultures evaluate on writing quality, scope discipline, and bias to running code over slide decks.
These are the cultures we tuned the TPM rewrite against. Not exhaustive, just representative.
Two columns. Phrases on the left signal the archetype. Phrases on the right disqualify you in 5 seconds of skim.
Same operator, same outcomes. Three bullets rewritten in the TPM register so you can hear how the voice changes.
Owned partner-tier scoring v2 end-to-end. RFC, build, ship, monitor. 12 weeks. Adoption 92.9% within a quarter.
Wrote the partner-tier pipeline RFC in 800 words, three reviewers, two revisions. Cycle time dropped 41% post-merge.
Shipped a partner-tier scoring service behind a feature flag, instrumented day one. 130K records, 92.9% adoption, two paged incidents in 90 days, both inside SLO.
The bar past the resume. If the rewrite gets you in the room, these are the criteria the loop will weigh once you are there.
The TPM archetype is pre-selected on the sandbox. Hit Run and watch a real partner-ops resume rewrite itself with word-level diff.