L8 Explains Career for Software Engineers
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
L8 Principal's Agentic Engineering Workflow
Kun Chen
50.6k views
AI Tech Layoffs Explained by ex-Meta Principal Engineer
Kun Chen
81.8k views
Ken Burns Explains the Revolution’s WARNING for America
Legal AF
43.0k views
Why Is U.S. Intel So BAD? Former CIA Analyst Explains
Kim Iversen
9.9k views
Software engineering is dead now
Theo - t3․gg
165.4k views
Anthropic confirms software engineering is NOT dead
ThePrimeTime
341.6k views
My honest advice to aspiring software engineers
Tech With Tim
34.9k views
How to Prepare for a Nuclear Apocalypse, Explained by a Chemical Engineer
Tucker Carlson
596.1k views
Tucker Carlson Explains How To Solve The Israel-Palestine Issue
Kim Iversen
76.3k views
What the $100k H1B Visa Means for Software Engineers
Tech With Tim
45.8k views
Top Comments (10)
Perfect timing! I just got a job at Google and I'm really trying my best to prepare for the next few weeks before I start so that I can be of value to my team as soon as possible and start working my way up. Thank you for the insight.
Great video! I think there are various archetypes of senior++ engineers. The one you mentioned in this video is TL type of engineers that focuses on the strategical planning on the technique side. They are the ones to make ambiguous problem clear. One other type of senior++ engineers are the one to solve the clear (in terms of problem formulation) but difficult problems, they are usually the domain experts. Many such problems exist in the infra or ML side, so those team usually have higher ratio of senior++ engineers, even though the team size may still be small.
Wow this was great! I really liked the feature breakdown analogy
Hey Kun, great video ! Explains the ladder quite well.
Great content, Kun!
Great content and topic! It can get even better with an improved audio input (at least with a microphone) :)
Brilliant insights! Thanks
Wow I actually learned so much from this. I’m currently going into 9th grade and taking computer science classes because I really want to be a software engineer some day and I learned so much from each level and what to focus and master to get promoted. It will probably take me a couple years but I WILL become a software engineer some day!!
Thank you for putting together this very informative video 🙏 I was recently promoted to a L4 equivalent SWE role and was asked how I intend to grow in my new position. I had vague ideas of what I can still improve on, but didn’t know how to approach those issues. Now that I have a better idea of what the next level of organization is (L5), I feel more confident in coming up with a career plan to reach that role as my next milestone.
Superb presentation, Kun. Thank you for putting these videos together. I'm curious about one thing. I'm curious about the line between L3 and L4, which to me seems kinda fuzzy. Eg would deciding on which language-runtime-framework to use be definitely L4 and everything below that L3?
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
Perfect timing! I just got a job at Google and I'm really trying my best to prepare for the next few weeks before I start so that I can be of value to my team as soon as possible and start working my way up. Thank you for the insight.
Great video! I think there are various archetypes of senior++ engineers. The one you mentioned in this video is TL type of engineers that focuses on the strategical planning on the technique side. They are the ones to make ambiguous problem clear. One other type of senior++ engineers are the one to solve the clear (in terms of problem formulation) but difficult problems, they are usually the domain experts. Many such problems exist in the infra or ML side, so those team usually have higher ratio of senior++ engineers, even though the team size may still be small.
Wow this was great! I really liked the feature breakdown analogy
Hey Kun, great video ! Explains the ladder quite well.
Great content, Kun!
Great content and topic! It can get even better with an improved audio input (at least with a microphone) :)
Brilliant insights! Thanks
Wow I actually learned so much from this. I’m currently going into 9th grade and taking computer science classes because I really want to be a software engineer some day and I learned so much from each level and what to focus and master to get promoted. It will probably take me a couple years but I WILL become a software engineer some day!!
Thank you for putting together this very informative video 🙏 I was recently promoted to a L4 equivalent SWE role and was asked how I intend to grow in my new position. I had vague ideas of what I can still improve on, but didn’t know how to approach those issues. Now that I have a better idea of what the next level of organization is (L5), I feel more confident in coming up with a career plan to reach that role as my next milestone.
Superb presentation, Kun. Thank you for putting these videos together. I'm curious about one thing. I'm curious about the line between L3 and L4, which to me seems kinda fuzzy. Eg would deciding on which language-runtime-framework to use be definitely L4 and everything below that L3?