Source: Jordan Cutler (Staff Engineer, Web Platform at Pinterest), original article: https://newsletter.eng-leadership.com/p/how-to-grow-from-senior-to-stuck
Core thesis: The leap from Senior to Staff is not a contest of technical depth — it is a qualitative change in mindset.
Why Many Senior Engineers Get Stuck
Many engineers write code faster, master more complex architectures, and go deeper technically — 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 dimension entirely.
- Senior mindset: "How can I write better?"
- Staff mindset: "How can I make 10 people write better?"
- Day one: 200+ members joined
- A few months later: 1,200+ members
- Repeated shout-outs at all-hands meetings
- Included in company-level tooling planning
- Don't say: "The JSON payload is 500KB, too large."
- Say: "The Search response is 500KB, far exceeding what UX needs. Fixing it makes results appear ~100ms faster. The fix: reduce item counts in query parameters and normalize the response format."
- The API Platform team onboarded in one day with a single config file
- The mobile team is considering adoption
- Web Modernization added an "unused code" monthly report via one PR
- Cutler no longer needs to touch it
- Pick an unowned but valuable initiative adjacent to your domain and create a channel, doc, or tool
- Always attach a cost estimate and a concrete fix when raising problems
- Turn your team's vaguest complaints ("builds are slow", "tests are flaky") into a red/yellow/green dashboard
The latter is the Multiplier Mindset.
Dimension 1: Expand Your Scope — Don't Wait for Assignments
Pinterest never asked Cutler to promote AI tooling. But noticing an industry-level trend with no internal owner, he:
1. Experimented with AI coding tools himself 2. Privately gauged interest from a like-minded colleague 3. Secured backing from managers and Staff+ engineers
He launched the #how-i-ai Slack channel:
Chain reaction: monthly executive demos → invitation to the "AI Coding Pathfinders" group → leading company-wide AI coding standards.
Key insight: These opportunities were not assigned. He created the space, planted value, and let compounding happen. He later shipped Claude orchestration tooling, doc generators, slide generators, and MCP integrations — all starting from spotting a gap.
Dimension 2: Cross-Team Influence — Lower the Cost of Action
His first Pinterest project was auditing Search page performance. His initial detailed audit report was not prioritized — the owning team couldn't see why to act now or what the payoff would be.
His fix was in how he framed problems:
Three elements: the problem (500KB), the cost (100ms user delay), and a concrete fix.
He then replicated this: Home Feed and Pin Page (Closeup) — covering 80% of Pinterest's traffic — were an "easy yes" to audit. One finding: reuse the Home Feed's medium-resolution image as the Closeup placeholder while the HD image loads in the background.
Result: 30%+ performance improvement across three core pages — while he was still a Senior Engineer.
Key insight: "Your page is slow" gets ignored. "Here's the problem, the data, the fix, and I'll help" drives action.
Dimension 3: Build Scalable Systems — Let Metrics Speak
Asked "How is our developer experience, really?" his team couldn't answer. Data was scattered across Buildkite, GitHub, JIRA, Honeycomb, and DX surveys — with no unified view. Priorities were set by whoever complained loudest in Slack.
Cutler built a framework connecting three layers:
| Layer | Content | Examples | |-------|---------|----------| | Team-controlled | Metrics the team directly affects | Build time, test pass rate | | Developer experience | What engineers feel daily | CI pipeline duration, tool friction | | Leadership view | CTO dashboard numbers | DX Index |
Every metric has red/yellow/green thresholds (e.g., CI pipeline: <12 min green, 12–18 min yellow, >18 min red), based on industry percentile data and developer feedback.
The system then runs itself: teams define a config object (metric names, categories, thresholds); a pipeline pulls data weekly and posts a formatted Slack report every Monday morning. Regression issues get pinned; improvements link to recent launches.
Key insight: Staff-level contribution is not "how many problems I fixed" but "I built a system where problems surface, priorities sort, and the team runs automatically."
The Unifying Principle: Multiplier Thinking
| Dimension | Senior Mindset | Staff Mindset | |-----------|---------------|---------------| | Scope | "Do my assigned work well" | "Fill gaps nobody owns; create compounding value" | | Cross-team | "Report problems, wait for fixes" | "Lower the cost of action; make change happen" | | Systems | "Fight fires where they start" | "Build self-running infrastructure" |
The progression: individual output → team output → system output. Critically, Cutler did all of this while still a Senior. The correct order is: change first, promotion follows — not the other way around.
Mapping to Chinese Tech Career Ladders
Chinese big-tech levels (e.g., Alibaba P6→P7→P8, ByteDance 2-1→2-2→3-1) don't map one-to-one to Pinterest's ladder, but the logic transfers:
| Stage | Rough Equivalent | Key Shift | |-------|------------------|-----------| | Senior (P6/P7) | Senior | Technical depth + module ownership | | Staff (P7/P8) | Staff | Cross-team influence + system building | | Expert (P8+) | Principal+ | Organization-level multiplier effect |
Common pitfalls to avoid:
1. Chasing only technical depth (e.g., discussing algorithm optimization in a P8 interview instead of "how I got three teams to co-build a platform") 2. Waiting for your manager to assign cross-team projects — Staff-level opportunities must be self-created 3. Firefighting as a badge of honor, when reviewers see no systematic output
Actions you can take immediately:
Conclusion
Senior is the ceiling most people reach through effort. Beyond that, the direction of effort must change. Faster code and deeper architecture become the baseline at Staff level, not the differentiators. The real differentiators: spotting gaps nobody sees, making other teams want to listen, and building systems that don't need you. You can start practicing at Senior level — you don't need to wait 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)