TL;DR
An engineer describes leaving YouTube after repeated promotion denials despite doing higher-level work. The post chronicles job hunting while employed, navigating NDAs in interviews, and an exhausting interview loop that exposed organizational friction.
What happened
The author recounts leaving a high-profile role at YouTube after multiple unsuccessful promotion attempts from L4 toward senior levels. Although they were performing work aligned with senior or staff expectations—architecting systems, leading teams, and launching features—the formal promotion committee repeatedly cited insufficient "impact." Rather than continue to invest extra effort into another uncertain promotion cycle, the engineer pursued opportunities outside the company and aimed for a two-level jump in interviews. They balanced a demanding full-time job with late-night interview preparation and took creative measures to avoid NDA violations, emphasizing transferable engineering principles instead of product specifics. One application process required 13 interviews, which the author interprets as a sign of decision-making dysfunction; other companies with 5–8 rounds felt more decisive. The departure conversation with a supportive manager was emotional, and the author frames leaving as necessary growth rather than a reaction to poor leadership.
Why it matters
- Formal leveling determines compensation, equity and the scope of work engineers are permitted to own.
- Long or opaque promotion processes can push high performers to seek external validation and offers.
- Managing job searches while employed creates significant cognitive load and risks burnout.
- NDAs constrain how candidates can present accomplishments, requiring careful abstraction of technical work.
- Extended interview loops may reflect organizational indecision and can deter candidates or reveal cultural issues.
Key facts
- The author repeatedly applied for promotion from L4 toward L5 and received denials citing lack of "impact."
- They believed they were operating at L5/L6 responsibilities—architecting systems and leading roadmaps—while titled below that level.
- Instead of staying to pursue further internal promotion cycles, the author opted to search the external market and attempt a double-level jump.
- Job hunting was conducted while employed, involving late-night study, interviews taken in personal time, and creative scheduling.
- To avoid NDA breaches, the candidate focused interview narratives on high-level engineering patterns and system metrics rather than proprietary product details.
- One company required 13 interviews for a single role; the author contrasts this with companies whose loops were 5–8 rounds.
- The author felt companies with fewer rounds demonstrated clearer internal alignment on hiring decisions.
- The final resignation conversation with the manager was empathetic; the author left despite respect for their team and leaders.
What to watch next
- The length and structure of interview loops at prospective employers as an indicator of decision-making and hiring culture.
- How companies balance confidentiality with a candidate’s need to demonstrate relevant, high-impact work under NDA constraints.
- not confirmed in the source
Quick glossary
- Leveling: A hierarchy of job grades in tech companies (e.g., L3–L6) that signals seniority, pay bands, and expected scope of responsibility.
- NDA (Non-Disclosure Agreement): A legal contract restricting disclosure of confidential information about products, systems or business practices.
- Promo cycle: An internal review process where employers evaluate employees for advancement to higher levels or titles.
- System design: High-level architectural planning of software systems, including decisions about scalability, performance and data flow.
- Interview loop: A sequence of interviews—technical, design and behavioral—used by companies to evaluate candidates for a role.
Reader FAQ
Why did the author leave YouTube?
They left after repeated promotion denials and feeling they had outgrown the role; they sought external validation and appropriate leveling.
Did the author manage to secure a higher-level role externally?
not confirmed in the source
How did they discuss proprietary work during interviews?
They avoided product details and emphasized transferable engineering principles, system scale and architectural patterns.
Was the author's manager supportive when they resigned?
Yes; the final conversation was described as empathetic and emotionally difficult for both parties.
24 DEC 2025 6 MIN READ How I Left YouTube Me when I first joined Google/YouTube I remember sitting down in a meeting room hearing the results of my third…
Sources
- I Left YouTube
- Thinking about quitting as engineer after management …
- Software Developer Promotions: Advice to Get to That Next …
- Should I stop doing YouTube? I have been making a lot …
Related posts
- Waymo outlines response after PG&E blackout that darkened a third of San Francisco
- Google’s year in review: 8 areas with research breakthroughs in 2025
- Google may soon let users swap one @gmail.com address for another