From Senior to Staff: Pinterest Engineer's Promotion Secret Isn't Writing More Code
> Source: Real promotion case from Jordan Cutler, Staff Engineer at Pinterest > Original: https://newsletter.eng-leadership.com/p/how-to-grow-from-senior-to-staff > Core thesis: The Senior → Staff transition is not about technical depth—it's a qualitative change in mindset.
Why Many Senior Engineers Get Stuck
Engineers often keep writing code faster and mastering deeper architecture, yet never get promoted. Jordan Cutler's observation: engineers stuck at Senior keep improving along the *same* dimension, while those who reach Staff switch to a different one entirely.
Senior engineers ask: "How can I write better?" Staff engineers ask: "How can I make 10 people write better?"
That's the Multiplier Mindset.
1. Expand Your Influence — Don't Wait for Assignments
Pinterest never asked Jordan to promote AI tooling. His actual job was developer experience on the Web Platform team. But he noticed AI reshaping engineering workflows with no internal owner, so he:
1. Experimented himself with different AI coding tools 2. Recruited a small group, starting with one interested colleague 3. Secured backing from managers and Staff+ engineers before launching
He created the #how-i-ai Slack channel:
- Day one: 200+ members
- Months later: 1,200+ members
- Praised at all-hands meetings; incorporated into company-level tooling plans
- "CI feels slow" became "CI pipeline is red, averaging 19 minutes"
- Quarterly planning now starts from the spreadsheet: red first, yellow next
- From whack-a-mole to data-driven decisions
- Expand scope: Find an unowned but valuable area adjacent to your work and start a channel, doc, or tool
- Cross-team communication: Next time you raise a problem, force yourself to include a cost estimate and a proposed fix
- Build metrics: Turn your team's vaguest complaints ("builds are slow," "tests are flaky") into a red/yellow/green dashboard
The compounding chain: visibility → invited to monthly executive demos → invited by the chief architect to the "AI Coding Pathfinders" group → leading company-wide AI coding standards. He later shipped tools like a Claude dispatcher, documentation generator, slide generator, and MCP integrations.
> Key insight: These opportunities weren't assigned. He created the space, planted value, and let compounding happen.
2. Cross-Team Impact — Lower the Cost of Action
In his first Pinterest project—auditing Search page performance—Jordan's detailed report was ignored. The owning team couldn't see why it mattered *now*.
His fix was reframing. Instead of:
> "The JSON payload is 500KB, too big."
He said:
> "The Search response is 500KB, far exceeding what user experience needs. Fixing it makes search results appear ~100ms faster. The approach: reduce item counts in query parameters and standardize response format."
Three elements: the problem (500KB response), the cost (100ms user delay), the fix (a concrete, simple plan). This version was adopted.
Then he scaled it: he asked the managers of Home Feed and Pin Page (Closeup)—covering ~80% of Pinterest traffic—for a quick audit of their pages too. An easy yes. One finding: Closeup showed a background color while the HD image loaded, so he proposed reusing the Home Feed's medium-resolution image as the initial display.
Result: 30%+ performance improvements across three core pages—while he was still a Senior.
> Key insight: "Your page is slow" gets ignored. "Here's the problem, here's the data, here's the fix, and I'll help" drives action.
3. Build Scalable Systems — Let Metrics Speak
When asked "How is our developer experience, actually?", nobody could answer. Data was scattered across Buildkite, GitHub, JIRA, Honeycomb, and DX surveys—priorities were driven by whoever complained loudest in Slack.
Jordan built a framework connecting three layers:
| Layer | Content | Example | |-------|---------|---------| | Team-controllable | Metrics teams directly affect | Build times, test pass rate | | Developer experience | What engineers feel daily | CI pipeline duration, tool friction | | Leadership view | Numbers on the CTO dashboard | DX Index |
Every metric got red/yellow/green thresholds. Example: CI pipeline < 12 min = green, 12–18 min = yellow, > 18 min = red—based on industry percentile data and developer feedback.
Effects:
Then he made the system self-running: teams define one config object (metric names, categories, thresholds), and a weekly pipeline pulls data, computes changes, and posts a formatted Slack report every Monday morning. The same data syncs to Google Sheets for long-term trends.
Scalability proven: the API Platform team adopted it in one day with just a config file; the mobile team is considering it; Web Modernization added a new "unused code" monthly report with one PR. Jordan no longer touches it.
> Key insight: Staff-level contribution isn't "how many problems I fixed"—it's building a system where problems surface automatically, priorities order themselves, and the team runs on its own.
The Unifying Thread: Multiplier Mindset
| Dimension | Senior mindset | Staff mindset | |-----------|---------------|---------------| | Scope | "Do my assigned work well" | "Fill gaps no one owns; create compounding value" | | Cross-team | "Point out problems, wait for fixes" | "Lower the cost of action; make change happen" | | Systems | "Fight fires where they burn" | "Build self-running infrastructure" |
The progression: personal output → team output → system output.
Crucially, Jordan did all this *while still a Senior*. He worked like a Staff engineer first—the title followed. The correct order is change first, promotion second.
Takeaways You Can Apply Today
Closing Thought
Coding speed, complex architecture, and technical depth are differentiators at Senior—but merely table stakes at Staff. The real questions become: Can you spot gaps no one else sees? Can other teams trust and act on your proposals? Can you build a system that runs without you?
The multiplier mindset isn't having 10 people write code for you—it's enabling 10 people to write faster, better, and happier because of your work. You can start practicing at Senior level, rather than waiting for the title.
> References > - Jordan Cutler, "How to Grow from Senior to Staff", eng-leadership.com > - Jordan Cutler, "The Multiplier Mindset" (O'Reilly early release)