@ryanlpeterman: Philip Su grew quickly to a Distinguished Engineer at Facebook and OpenAI. We talked about the psychology behind peakin…
Summary
Philip Su, a Distinguished Engineer at Facebook and OpenAI, discusses the psychology behind peaking in a tech career, shifts in motivation, and finding fulfillment after high achievements.
View Cached Full Text
Cached at: 09/22/26, 01:45 AM
Philip Su grew quickly to a Distinguished Engineer at Facebook and OpenAI. We talked about the psychology behind peaking in a tech career and the pressure at the highest levels.
In this episode:
• Not wanting IC9 and requesting demotion
• How motivation changed across his career
• Fulfillment and motivation after FIRE
• Why sustaining IC9 was difficult
Where to watch:
• YouTube - https://youtube.com/watch?v=RMo04pSSiao… • Spotify - https://open.spotify.com/episode/3UfHNC1sCQIwV3mZ1qSUY6… • Apple Podcasts - https://podcasts.apple.com/us/podcast/the-peterman-pod/id1777363835… • Transcript - https://developing.dev/p/openai-and-meta-distinguished-eng…
Thank you to the sponsors of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://workos.com • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at https://jira.dev
Chapters:
00:00 Intro 00:37 Growth past IC9 05:39 Motivation changes over his career 11:36 Asking to not be promoted 17:33 What made it hard to sustain IC9 performance 22:22 What motivated him outside of promos 26:21 Is career advice useless 29:34 Motivation after you’ve hit FIRE 36:08 Meaning and fulfillment 38:17 Top book recommendation 40:14 What he would change 43:24 Outro
TL;DR: Philip Su, a Distinguished Engineer (IC9) at Facebook and OpenAI, discusses the psychology of reaching a career “asymptote”—the point where further promotion becomes unlikely—and how his motivation shifted from chasing levels to deriving fulfillment from empowering others.
The Concept of a Career Asymptote
Philip Su reflects on the idea that in any technical career, there is a point of diminishing returns for promotion. He compares this to reaching the highest levels, like IC9 or Distinguished Engineer, where the requirements for advancement become exponentially larger, and the opportunities for such roles are inherently scarce within an organization’s structure.
“The requirements get much higher, the scope of work that’s required is also much wider, and the roles that provide that scope are actually fewer.”
Su notes that during his early career, the progression seemed natural, but he later realized this growth must eventually slow. He mentions that at Microsoft, they often find that any given organization can only support about four Partners due to budget and business opportunity constraints.
Early Motivation and the Role of Levels
In his twenties and early thirties, Su was strongly motivated by quantifiable metrics, with job levels serving as a key achievement indicator.
“For me, promotion became one of the few quantifiable things… Levels became an achievement number.”
He describes his drive to reach IC7 at Microsoft, comparing it to enjoying tests and grades in school. However, this focus began to change as he progressed, because the nature of the work transforms at each level.
Transition from Promotion-Seeking to Impact-Driven Work
A pivotal shift occurred when Su began focusing on empowering others rather than climbing the ladder. This change in perspective made promotions feel like a natural byproduct of meaningful work, not the primary goal.
“The idea of cultivating others. I realized when your role becomes to empower people—not make them dependent on you, but help them grow and create space for them—that sense of accomplishment is completely different.”
This mindset was solidified during his time at Facebook. He recounts being unexpectedly promoted to IC8, not even knowing the company had a leveling system at the time, because his focus was on the mission and the work itself.
The Challenges of High-Level Positions
As engineers reach senior levels like IC6, IC7, and beyond, the role increasingly involves “meta-work” and collaboration with people. Su acknowledges that in large organizations, these positions require skills in navigating interpersonal dynamics and providing constructive feedback to peers—areas where he felt less proficient.
“A lot of the work is not actually about shipping software. It’s about the power dynamics that inevitably emerge when three or more people are in a room.”
He reflects that handling conflict, politics, and giving critical feedback are challenging skills that become essential at the highest individual contributor levels.
Accepting the Decline: A Psychological Struggle
Su candidly discusses the difficulty of voluntarily accepting a demotion from IC9 back to IC7. He frames this as a natural but painful part of a long career, comparing it to aging and giving up tools for hobbies one can no longer perform at a peak level.
“The rise is always enjoyable… Being at the peak is mixed—there are great parts and there are hard parts. And the descent, I think, in some ways is hard.”
He acknowledges the human aversion to losing status and the challenge of letting go of past achievements, even when one knows they are capable of more. The final question of the video—whether slower promotions would have led to more happiness—is left as a lingering reflection on the trade-offs of a rapidly ascended career.
Source: YouTube Video
Similar Articles
@system_monarch: This engineer just became a staff SWE at OpenAI and got an offer of $900k USD. Five things from his journey that everyo…
An engineer shares five key tips for succeeding in system design interviews after achieving a staff SWE position at OpenAI with a $900k offer, focusing on rapid design, clear reasoning, pattern knowledge, adaptability, and preparation.
@GergelyOrosz: IDK how or why but the last year, whenever I met a tech professional on this site who I thought "damn this person is su…
Gergely Orosz observes that impressive tech professionals he meets on the site are often recruited by OpenAI or Anthropic within a year, citing Kate's move to OpenAI to work on ChatGPT's web infrastructure.
Ryan Peterman (@ryanlpeterman) on X
Interview with Google DeepMind's pre-training area lead Vlad Feinberg about landing jobs at frontier AI labs, covering needed skills, research vs engineering differences, and scaling laws.
@antonsten: I've been fortunate to work alongside @MatthewEdanWoo for more than four years now. Here's a first glimpse into what we…
The author shares insights on pivoting from product-focused to research-oriented company building in AI, exploring future human-AI interfaces and referencing recent models like Kyutai's Moshi.
@charliermarsh: Talked with @ryanlpeterman about how software engineering is changing! I like the pull quote, which captures a lot of w…
Charlie Marsh and Ryan Peterman discuss the impact of AI writing code on software engineering, arguing that PR review costs remain constant while generation costs are zero, and share experiences building Ruff, emphasizing rapid iteration, authentic marketing, and the importance of performance benchmarking.