In this video, a Meta Staff Software Engineer shares 40 hard-earned lessons from his 10-year career to help aspiring and current engineers. Key takeaways include mastering a single programming language deeply, then adding a strongly typed one, and understanding foundational concepts like data structures, algorithms, and design patterns. He emphasizes the importance of debugging, thinking in first principles, and shipping full applications. Career advice focuses on the benefits of joining FAANG, treating interviews as a learnable skill, and the strategic value of long-term project commitment over frequent job hopping. Personal growth lessons highlight self-advocacy through brag documents, managing stress, the occasional benefit of early-career burnout, and continuously investing in oneself.
The speaker's career progression from Accounting to Program Manager, then to Software Engineer after a bootcamp, culminating in Staff Engineer at Meta
[
00:00:20
]
While dynamic languages like JavaScript and Ruby are common, learning a strongly typed language (e.g., Java, Kotlin, Swift) changes your programming paradigm.
Visual representation of switching from dynamic languages like JavaScript and Ruby to mobile development, which often uses strongly-typed languages
[
00:02:21
]
Strongly typed languages help with compile-time error corrections and structuring programs, unlocking scalability for code.
A visual of code, highlighting how strongly typed languages provide compile-time error corrections
[
00:02:35
]
3. Learn Data Structures, Algorithms, and Design Patterns [2:48]
Contrary to a common online trope, data structures and algorithms (DS&A) are frequently used in building complex systems.
A common online sentiment suggesting that Data Structures and Algorithms (DSA) are not used in everyday work
[
00:03:01
]
Examples include Facebook's reliance on graph traversal/searching problems.
Logos of popular applications (Facebook, X, Instagram, WhatsApp) which extensively use data structures and algorithms
[
00:03:15
]
Learning design patterns helps in quickly picking up new languages, frameworks, and systems as underlying principles are often shared.
A code editor displaying a 'Favorite Framework,' often built on underlying design patterns
[
00:03:34
]
DS&A knowledge is essential for getting into FAANG companies.
Debugging is a foundational skill for software engineers.
Methods include using debuggers to step through code or adding print/console logs.
A visual representation of code with a bug icon, symbolizing the act of debugging
[
00:04:25
]
The speaker, often pulled into unfamiliar workstreams to fix bugs, emphasizes that advanced debugging involves understanding performance tools (e.g., systrace) and error logs.
5. Think in First Principles and Dig In For Yourself [5:05]
New engineers often accept explanations without questioning, but it's crucial to think from first principles and investigate personally.
The speaker recounts finding critical bugs that others dismissed, such as a back button issue that improved app regression by 30%.
A team chat exchange where a problem is initially dismissed as 'fine,' highlighting the need to dig deeper
[
00:06:00
]
Great engineers question the status quo and dig deep, choosing when to apply this critical thinking.
Shipping an entire application provides invaluable experience in the full development lifecycle, from bundling and account setup (iOS, AWS) to deployment and maintenance.
The speaker learned this even before becoming an engineer, initially as a game asset designer around 2010.
A calendar set to 2010, marking the speaker's early foray into app development
[
00:07:36
]
Working only on small portions of an app at large companies limits this comprehensive learning.
A pie chart illustrating how engineers at large companies might only work on a small segment of an application
[
00:08:09
]
This experience helps in understanding end-to-end challenges, including setting up bundles, iOS accounts, and cloud formations for deployments.
Key steps involved in shipping an app, such as setting up bundles, iOS accounts, and cloud formations
[
00:08:28
]
At large companies, frequent reorgs make it difficult to stay on one project long-term.
Staying on a project for an extended period (e.g., over a year) allows engineers to learn from their architecture and system design choices when they are truly tested at scale.
Long-term involvement reveals flaws in code extensibility, evolution, or cloud setups, enabling better future decisions.
The tech industry, especially web development, sees new frameworks constantly. Most are fleeting.
New frameworks stacked on top of each other, illustrating the rapid introduction of new technologies
[
00:03:44
]
Instead of frameworks, prioritize learning fundamental design patterns.
For new projects, choose battle-tested technologies used by large companies to avoid scalability issues.
A search bar prompting inquiry into technologies already widely adopted by large companies
[
00:10:54
]
Chasing frameworks is an early-career trap; experienced engineers understand that the right tool for the job is what matters, and new frameworks can be learned quickly if needed.
Software engineering can seem complicated with complex systems and jargon (e.g., Kafka terms).
It's important not to be intimidated; at its core, it's just code making requests and connections.
The speaker recalls feeling out of place after a reorg when new to a team that used unfamiliar terms like Kafka topics and producers.
A visual distinguishing between team members 'used to all these terms' and 'new' members following a reorg, illustrating changes in expertise
[
00:12:07
]
Embrace curiosity and investigate new concepts. The speaker references Steve Jobs' quote about life being built by people no smarter than you.
Steve Jobs' quote: 'Life can be much broader once you discover one simple fact: Everything around you that you call life was made up by people that were no smarter than you and you can change it.'
[
00:13:19
]
The software engineering industry is vast (backend, frontend, cloud, AI, security).
A pie chart representing various domains within software engineering: backend, frontend, cloud computing, and AI
[
00:13:54
]
While you can't be an expert in everything, having a broad understanding of technologies (e.g., crypto, AI) and industry trends is crucial.
Curiosity allows engineers to cross-pollinate learnings from different domains into their own. For instance, the speaker's knowledge of React helped him quickly pick up Compose and Swift UI.
Folders representing different industries, with dotted lines indicating how knowledge can be cross-pollinated into one's own domain
[
00:14:45
]
AI is one of the most important lessons. Engineers should actively learn to leverage AI in their workflows. The speaker started exploring AI features and tools around April 2022.
A calendar showing April 2022, marking the period when the speaker began focusing on AI's boom
[
00:15:26
]
A screenshot of Jonny K's YouTube channel, which he uses to explore AI features and tools
[
00:15:45
]
Understanding how to run models locally, differentiate between model types (e.g., stable diffusion vs. auto-regression), and use AI for video/voice generation is becoming critical.
Key questions indicating deep understanding of AI, such as running models locally and differentiating between model types
[
00:16:21
]
The next generation of high-skilled engineers will be those who can effectively use AI to create features and achieve "10x or 100x" productivity by writing efficient code with less tech debt.
Getting into FAANG (Facebook/Meta, Apple, Amazon, Netflix, Google) is described as "winning the lottery" due to significant income increases (e.g., 50% for the speaker despite a down-level).
An illustration showing a 50% increase in income after joining a FAANG company
[
00:17:18
]
The speaker joined Meta as a rotational engineer after being a Principal Associate at Capital One, effectively a down-level.
A visual showing the speaker's down-level from Principal Associate at CapitalOne when joining Meta
[
00:17:25
]
He successfully proved himself within six months and progressed quickly through levels E4 to E6 (Staff Engineer).
A calendar indicating the timeline 'within a year' for proving oneself at the E4 level at Meta
[
00:17:38
]
Beyond compensation, FAANG offers access to highly skilled engineers, mentors, and a top-tier professional network.
A visual representation of an expanding professional network
[
00:18:51
]
While job hopping can increase compensation in the short term, it may hinder career progression to staff-plus engineer levels, despite common advice to hop every 1-2 years.
An online comment suggesting frequent job hopping (every one or two years) for career advancement
[
00:20:54
]
Senior roles require relevant experience and significant project ownership, which takes time to earn within a company (typically 3+ years to gain trust for critical projects).
Consistent high performance over several years is key to earning trust and being assigned high-impact projects.
An engineer's performance ratings, showing consistent high marks over five years at a company
[
00:22:17
]
Constant job hopping means perpetual onboarding, limiting opportunities for high-impact work and deep organizational trust.
A virtuous cycle illustrating how doing well leads to recognition, which in turn leads to more important projects
[
00:22:42
]
A brag document is a personal journal of accomplishments, skills, and contributions, updated weekly.
The speaker encourages his many mentees (over 15) to use brag documents.
A visual representing the speaker's extensive mentorship of over '15+ Mentees.'
[
00:28:08
]
It helps track small and large achievements (e.g., design comments, tasks fixed, project impact).
A comprehensive definition of a 'brag document' as a personal record of accomplishments and contributions
[
00:28:26
]
Examples of contributions to include in a brag document, such as design comments, fixed tasks, and project updates
[
00:28:43
]
This document helps you see the volume of your contributions and ensures that "impact on the table" isn't left out of performance reviews, aligning with the saying "You can't measure what you don't track."
The maxim 'You can't measure what you don't track,' applied to career progress and performance
[
00:29:09
]
Regular review with a manager allows for early course correction, ensuring alignment with promotion criteria.
Calendars showing progression through months (January, February, March), illustrating the ability to course-correct early with a brag document
[
00:31:03
]
You are the primary advocate for your career; avoid blaming external factors like reorgs for lack of promotion.
Good work alone doesn't guarantee fair treatment; you must actively fight for visibility and recognition.
While work-life balance or a happy environment can be personal optimizations, career velocity requires proactive control and strategic thinking about promotion paths.
Within FAANG companies, the "top 1%" of engineers often receive "additional equity" as a retention strategy.
A visual suggesting the existence of a 'top 1%' of engineers even within top companies
[
00:33:18
]
This extra pay, usually at a director's discretion, makes it challenging to leave the company due to the significant financial incentive.
A visual emphasizing that the 'Top 1% of the 1%' of engineers receive significantly higher compensation, often through additional equity
[
00:34:06
]
The distribution of this additional equity is not equal; it targets engineers whose loss would be most expensive or impactful to the company.
22. Soft Skills Matter More Than You Think [34:37]
Technical prowess alone isn't enough for advanced career levels; soft skills, particularly Emotional Intelligence (EQ), become critical.
Text highlighting 'Soft Skills' as a common barrier to career advancement for engineers
[
00:34:39
]
A visual suggesting that while being technically adept and knowing frameworks are important, other factors (like soft skills) can be limiting
[
00:34:48
]
Effective collaboration with product managers, designers, and cross-functional teams is essential for making broader impact.
Soft skills are trainable and should be actively practiced alongside technical skills to build strong professional relationships.
The tech industry, especially in Silicon Valley, is small; people frequently re-enter your professional life.
Maintaining good relationships makes working easier and can lead to positive re-encounters.
A visual indicating former colleagues reconnecting 'around 2 years later,' emphasizing the importance of maintaining good relationships
[
00:37:12
]
The speaker recounts a time he gave fair, mostly positive feedback to a lazy coworker, who later reappeared in his organization and was grateful because he had been going through personal issues.
A thank-you message from a former colleague, illustrating the positive long-term impact of maintaining good relationships
[
00:37:27
]
Unless absolutely necessary to stand up for yourself or organizational health, avoid making enemies.
As a software engineer, you spend significant time at a computer, making a good ergonomic setup (e.g., Herman Miller chair, standing desk) a worthwhile investment.
The speaker showcasing his ergonomic office setup, including a Herman Miller chair and a standing desk
[
00:39:45
]
A clock on a laptop screen, symbolizing the significant amount of time engineers spend in front of computers
[
00:39:59
]
Prioritizing physical well-being (like needing a good bed for sleep) is crucial for long-term career sustainability, akin to an athlete taking care of their body.
This is a metaphor for getting outside and having a life beyond work to prevent burnout.
Engaging in activities like golf or other hobbies helps clear your mind and provides a necessary break from the intensity of engineering.
The speaker playing golf, illustrating 'touch grass' as a metaphor for taking breaks and engaging in hobbies to prevent burnout
[
00:43:48
]
31. Early Career Burnout Is Sometimes Okay [44:34]
While generally to be avoided, strategic periods of intense work or "burnout" (e.g., during bootcamp, interview prep, or first few years) can accelerate growth significantly.
The speaker's two-year grinding period to get into Meta, including two months of daily 4-hour prep sessions, was exhausting but ultimately life-changing.
A calendar showing consistent, daily grind (green checks) during intense interview preparation periods
[
00:45:11
]
A mentor can provide crucial guidance, course corrections, and accelerate your career velocity.
Even seasoned engineers can benefit from mentorship in new domains (e.g., performance optimization, mobile, backend, debugging distributed systems, choosing the right abstraction).
Examples of advanced engineering topics where a mentor can provide guidance, such as 'Debugging distributed systems' or 'Choosing the right abstraction.'
[
00:46:44
]
Actively seek out experienced individuals who can help you learn and grow, especially early in your career.
A magnifying glass highlighting an individual within a group, symbolizing the search for a mentor
[
00:46:55
]
Avoid hoarding information or critical scope, a common tendency early in one's career; the speaker admits to this initially.
A visual depicting the speaker at the center of a group, representing the desire to be involved in the 'Most Important things' early in his career
[
00:48:14
]
Being open, generous, and helpful with your knowledge fosters greater growth.
Fears about ideas or scope being "stolen" are often overblown; most people don't act on shared knowledge. Giving often leads to receiving more in return.
Never assume you know everything or are a "rockstar engineer." There's always someone better, and the tech industry evolves too quickly to be on top of everything.
A bar chart where one bar significantly towers over others, symbolizing an inflated ego or the belief of knowing everything
[
00:49:18
]
The speaker's own experience of rejection from FAANG companies despite being a senior engineer at Capital One humbled him, forcing him to take interview prep seriously.
The speaker's title as 'Senior Engineer' at CapitalOne, prior to a humbling experience with FAANG interviews
[
00:49:40
]
A 'REJECTED' stamp over the speaker's profile, indicating his initial setbacks in FAANG interviews despite previous promotions
[
00:49:59
]
Approach new domain areas or workstreams with an open mind to continue learning and growing.
Especially in Silicon Valley, identity can become intertwined with one's job (e.g., "Staff Software Engineer at Meta"). The speaker admits this is still somewhat true for him.
Actively work to separate your personal identity from your professional role.
If your identity is too tied to your job, negative events outside your control (e.g., reorgs, layoffs) can be devastating.
What you learn and invest in yourself (new skills, mastering frameworks, working out, building relationships) are the only things you truly keep, regardless of job changes or loss.
Key areas for self-investment, including 'Learning a New Skill' and 'Mastering a new Framework'
[
00:54:13
]
Regularly self-reflect on how to invest in your personal growth to maximize whatever personal goals you have (e.g., work-life balance, career advancement, total compensation).
The speaker views his YouTube channel as a form of self-investment, improving his clarity of thought, presentation skills, and ability to tell compelling stories, which directly translates to his professional work.
