Philip's Advice To His Younger Self

In this final lesson, Philip reflects on the advice he would give himself at the beginning of his career. After years of aggressively pursuing promotions and professional milestones, he realized that achieving a goal quickly matters far less if you haven't first considered whether that goal will actually lead to the life you want.

- **Get clear on your values before optimizing your career.** Knowing what you genuinely want makes career decisions easier—but it’s equally important to question whether reaching that destination will actually give you the life you want once you arrive.
- **Don't sacrifice irreplaceable things just to arrive faster.** Reaching a terminal career level at 30 instead of 38 may matter very little over a decades-long career, while relationships, family, health, and other parts of life can sometimes be permanently damaged in the process.
- **Advice only works when you're ready to receive it.** Philip acknowledges that his younger, intensely ambitious self probably wouldn't have listened to the advice he gives today. Some lessons require experience and maturity before their meaning truly becomes clear.

Original podcast link: [**https://www.youtube.com/watch?v=v2JxdjTi_1I**](https://www.youtube.com/watch?v=v2JxdjTi_1I)

Should You Be A Generalist or A Specialist?

In this lesson, Philip explores one of the fundamental career decisions for engineers: whether to become a generalist or specialize deeply in a particular area. Drawing from his own career as a generalist, he argues that while specialization can be incredibly valuable for people with an exceptional aptitude or passion for a specific field, most early-career engineers may benefit from exploring broadly before committing to one path.

- **Explore before you specialize.** Unless you already have an unusually strong aptitude for a particular field, Philip recommends experimenting with different areas early in your career before committing deeply to one specialty.
- **Avoid over-specializing at the expense of broader capabilities.** Developing breadth gives you a better understanding of your strengths and helps prevent becoming so narrowly focused that you lack useful skills outside your specialty.
- **Consider the longevity of the field you specialize in.** Technologies can become obsolete, potentially leaving highly specialized professionals with skills that are less valuable. Generalists may have an advantage in adapting as technology, AI, and industry needs evolve.

Building Credibility As A Young Manager

In this lesson, Philip reflects on becoming a manager at just 24 years old and the challenges of leading people who were older, more experienced, and sometimes more senior than he was. Looking back, he openly acknowledges that ambition and technical ability got him into management before he had developed the maturity and leadership skills necessary to manage others effectively.

- **Being a strong engineer doesn’t automatically make you a strong manager.** Philip’s technical performance helped him enter management early, but leading experienced people required an entirely different set of skills that he still needed to develop.
- **Self-awareness and continuous learning are essential to becoming a better leader.** Philip improved by actively seeking mentors, requesting feedback, studying management, and acknowledging his mistakes rather than assuming that seniority would naturally make him a better manager.
- **Great leadership doesn’t require being great at everything.** Philip recognizes that giving difficult feedback remains a weakness, while inspiring people around a shared mission is one of his strengths. Effective leadership includes understanding where you excel, where you struggle, and where you still need to grow.

Becoming Valuable Over Time As An SWE

In this lesson, Philip reflects on how the skills that make an engineer valuable change over the course of a career. Early on, he distinguished himself through raw execution speed and an ability to outwork others. With experience, however, his advantage shifted from simply moving faster to developing better judgment—knowing which direction to pursue, recognizing warning signs earlier, and preventing teams from wasting time on the wrong problems.

- **Experience can turn speed into efficiency.** Younger engineers may execute faster, while experienced engineers can create greater impact by recognizing dead ends, anticipating problems, and ensuring their effort is directed toward the right things.
- **Alignment can matter more than finding the perfect answer.** Philip learned that an entire team moving together in a direction that is slightly imperfect can accomplish more than a divided team debating the theoretically optimal path—an idea reflected in the principle of “disagree and commit.”
- **Your strengths can evolve throughout your career.** Physical stamina and raw execution speed may decline, but judgment, pattern recognition, prioritization, and leadership can continue improving, allowing experienced engineers to create value in different—and potentially more leveraged—ways.

Writing Well As A Software Engineer

In this lesson, Philip explains how he transformed from someone who dismissed writing and other “soft skills” into a prolific writer who considers communication essential for technical professionals. He shares how reading great literature changed his appreciation for language and how deliberate practice—especially rewriting and editing his own work—helped him develop his distinctive writing style.

- **To write well, read well.** Philip developed his appreciation for writing by reading exceptional authors and paying attention to how they structure sentences, tell stories, and communicate ideas. He continues to notice and learn from effective rhetorical techniques in other people’s writing.
- **Great writing comes through rewriting.** Many of Philip’s posts went through multiple revisions before publication. Being willing to edit heavily, discard material, experiment with structure, and occasionally seek professional feedback helped him continually improve.
- **Writing creates leverage for technical ideas.** Strong communication allows engineers to share knowledge beyond the people they work with directly. Philip’s Great Posts Explorer extended this idea by helping employees rediscover valuable, evergreen writing that might otherwise have disappeared into the company’s history.

Joining OpenAI

In this lesson, Philip explains what brought him back to the technology industry after leaving Facebook, pursuing nonprofit work, and spending time away from traditional tech companies. Philip shares why he chose to apply only to OpenAI, how his experience at Facebook shaped his preference for working with a market leader, and what impressed him about OpenAI’s exceptionally high concentration of engineering talent. 

- **Recognize major technological transitions and decide whether you want to participate in them.** After experiencing the internet and mobile revolutions from Microsoft and the rise of social networking from Facebook, Philip viewed AI as a potentially even larger shift and deliberately chose to re-enter the industry to be part of it.
- **Market leaders have the freedom to experiment.** Philip prefers working for the category leader because a strong market position creates room to take ambitious risks, tolerate failures, and explore unconventional ideas rather than spending most of the organization’s energy catching up with a competitor.
- **Technical breakthroughs eventually need great products.** Philip was struck by OpenAI’s extraordinary engineering talent, but also observed that as competition grows, technical superiority alone becomes less sufficient. Turning research into reliable, compelling products becomes increasingly important.

Leaving Facebook

In this lesson, Philip explains why he chose to leave Facebook despite having a successful career at the company. Part of his decision came from wanting to focus his energy on broader societal challenges, including income inequality and his early concerns about technology-driven unemployment. 

- **Your value to an organization can change as the company grows.** Philip’s generalist skill set allowed him to make an outsized contribution when Facebook was smaller, but as the company scaled to thousands of engineers, he felt his particular strengths were becoming less differentiated.
- **Generalists can have an advantage in smaller companies.** Startups frequently have work that doesn't justify a dedicated full-time role, making people who can move between engineering, product, hiring, operations, and other responsibilities particularly valuable.
- **Scale creates greater demand for specialization.** As organizations grow, previously fractional responsibilities become full-time jobs. At that point, deep specialists can provide more value in a particular domain, while some of a generalist’s broader skill set may go unused.

Gratitude & Paying It Forward

In this lesson, Philip shares the story behind spending more than $23,000 to buy coffee for everyone at Facebook on his final day at the company. What began years earlier as a simple Christmas gesture became a meaningful way to close out a chapter of his career and express gratitude to a company that had given him extraordinary opportunities, mentorship, and financial success.

- **Recognize the role luck plays in success.** Philip credits hard work for parts of his career, but also acknowledges circumstances outside his control—from when and where he was born to joining Facebook at an unexpectedly transformative moment.
- **Gratitude can be expressed by paying success forward.** After Facebook’s IPO, Philip donated his proceeds to charity, and when he eventually left the company, buying coffee across several offices became another way to give something back.
- **Small gestures can create an outsized impact.** What began as buying coworkers coffee for a day created genuine joy and became a memorable tradition—showing that generosity doesn't always need to be complicated to be meaningful.

Working With Zuck And Other Impressive ICs

In this lesson, Philip reflects on what he learned from working alongside some of Meta’s most influential leaders and senior engineers. He shares what stood out about leaders like Mark Zuckerberg and Andrew “Boz” Bosworth—particularly their willingness to seek feedback, continually develop their skills, and make deliberate improvements even after reaching highly influential positions.

- **Exceptional leaders remain committed to their own growth.** Philip observed that leaders like Zuckerberg and Bosworth continued to seek coaching, respond to feedback, and deliberately improve their skills rather than assuming they had finished developing once they reached senior positions.
- **The best engineers can create impact far beyond their immediate responsibilities.** Philip recalls John Carmack quickly identifying technical and performance improvements in a product he hadn't worked on for months, demonstrating the depth of insight that can distinguish exceptional technical talent.
- **The highest-impact ICs are often force multipliers.** Scott Renfro stood out not only for his ability to deliver large, complex initiatives, but for making the engineers around him better through thoughtful feedback, supportive code reviews, and a willingness to invest time in others’ success.

Building A Strong Team Culture

In this lesson, Philip shares how he built and maintained a strong engineering culture while launching Meta’s London engineering office. Drawing on lessons from Meta’s Seattle expansion and advice from leaders who had built engineering sites at other companies, he explains how deliberately choosing the right founding team can shape a new office for years to come.

- **Learn from other teams before building your own.** Philip drew on both mistakes he observed while helping grow Meta Seattle and lessons from experienced site leaders to avoid reinventing the wheel when launching London.
- **A committed core team helps preserve culture during rapid growth.** Philip believes short three- or six-month landing teams leave too little time to establish a durable culture. Having experienced employees commit for two years provided stability while large numbers of new hires joined.
- **Select founding team members for culture, leadership, and technical strength.** Philip evaluated nearly 50 volunteers to choose 12 people who understood Meta’s culture, could bring and lead meaningful work, and would help establish strong hiring standards for the new office.

IC7, IC8, and IC9 Expectations

In this lesson, Philip breaks down how expectations change across senior engineering levels, from E7 through E9. Rather than viewing career progression as a checklist of increasingly difficult tasks, he explains that seniority is largely defined by the **scope, duration, and value of the impact you can reliably create**—whether through leading larger organizations, delivering increasingly complex initiatives, or possessing technical expertise that cannot easily be replicated by adding more engineers.

- **Higher levels are defined by expanding scope and influence.** An E7 might influence the work of roughly 50 people and independently drive long-term initiatives, while E8 and E9 impact expands further through organizational breadth, technical depth, strategic importance, or uniquely valuable expertise.
- **At the highest levels, promotion becomes increasingly qualitative.** There is no universal checklist for reaching E8 or E9. Senior engineers can create exceptional value through different archetypes, and recognition at these levels often depends on whether other senior leaders view your impact as operating at their level.
- **Surround yourself with people who create room for growth.** Being the strongest person on a weak team can limit your development and make it difficult to accurately assess your abilities. When senior role models are scarce, finding an experienced coach who can give candid, qualitative feedback may be even more valuable than finding someone whose career you can directly imitate.

Getting Promoted To IC9

In this lesson, Philip explains what operating at the E9 level looked like during his time leading Meta’s London engineering office. After arriving with just 12 engineers, he helped grow the organization to roughly 400–500 people—a shift that dramatically changed the complexity, ambiguity, and time horizon of the decisions he was responsible for making.

- **Greater seniority means solving increasingly ambiguous problems.** As organizations grow, decisions become less black-and-white, requiring leaders to navigate complexity, competing priorities, and uncertainty.
- **Senior-level impact requires thinking much further ahead.** At E9, Philip was making data-driven decisions about hiring and organizational needs as much as 18 months before their effects would be realized.
- **Scope is measured by both breadth and time horizon.** Progressing to the highest levels means influencing larger groups of people while identifying strategic problems and opportunities that others may not yet be thinking about.

Taking a Step Back from IC9 to IC7 at Meta

In this lesson, Philip shares the story behind his decision to move from E9 to E7 at Facebook after transitioning from site leadership back to an individual contributor role. Rather than viewing the change as a career setback, he saw it as an opportunity to align his level, compensation, and expectations with the work he actually wanted to do—and knew he could perform well.

- **Optimize for the role where you can perform well, not the highest title you can hold.** Philip preferred excelling at E7 over struggling to meet expectations at E9 and believed his level and compensation should reflect his actual contributions.
- **Moving down requires separating status from career satisfaction.** Going from leading hundreds of people to becoming an individual member of a team requires being comfortable giving up hierarchy, influence, and prestige in exchange for work that better fits you.
- **When you leave leadership, you also need to relinquish the authority that came with it.** Successfully stepping back means supporting the new leaders rather than continuing to use your previous influence to shape decisions that are no longer yours to make.

Management vs IC Transitions

In this lesson, Philip reflects on his experience moving between individual contributor (IC) and management roles throughout his career. He explains why he initially pursued management, why he ultimately prefers being an IC, and how he has managed to switch between the two tracks multiple times—even when doing so meant willingly stepping down in level.

- **Choose management because you want to lead—not simply because it feels like the next promotion.** Before becoming a manager, consider whether your team would genuinely want you to lead them and whether you would want to work for yourself.
- **Be careful of turning management into a one-way door.** Moving away from hands-on technical work can make returning to the IC track difficult, particularly if maintaining your title, level, or compensation becomes more important than making the right career move.
- **IC and management skills can converge at senior levels.** Senior ICs often need many of the same capabilities as strong leaders—including communication, vision, coaching, business understanding, and the ability to lead complex initiatives—although highly specialized technical roles may follow a different path.

Original podcast link: [**https://www.youtube.com/watch?v=v2JxdjTi_1I**](https://www.youtube.com/watch?v=v2JxdjTi_1I)

Becoming Senior Staff IC7 at Microsoft

In this lesson, Philip reflects on his rapid career progression at Microsoft and the factors he believes contributed most to his growth as an engineer. He discusses the value of working alongside exceptionally talented colleagues and mentors, deliberately accumulating experience early in your career, and the role that hard work can play in accelerating professional development.

- **Career growth is a combination of luck, talent, and hard work.** While some factors are outside your control, putting yourself in strong environments and learning from exceptional people can accelerate your development.
- **More experience can compress the learning curve.** Taking on a high volume of meaningful work early in your career can expose you to situations and problems that might otherwise take years to encounter.
- **Hard work has diminishing returns—and real trade-offs.** Longer hours may increase total output and experience, but each additional hour can become less productive, and career acceleration can come at the expense of health, relationships, and balance.

Original podcast link: [**https://www.youtube.com/watch?v=v2JxdjTi_1I**](https://www.youtube.com/watch?v=v2JxdjTi_1I)

Adam’s Advice to His Younger Self

In this final lesson, **Adam Ernst**, Software Engineer at **Meta**, reflects on his career journey and the advice he would give to aspiring engineers. Looking back, Adam believes he would not change the path he took because it aligned with his genuine interests and strengths. He emphasizes that long-term success comes from enjoying the work itself—especially the challenge of solving difficult problems—rather than chasing titles or following trends. By pursuing work that naturally fuels curiosity and motivation, engineers are more likely to sustain high performance and meaningful career growth.

- **Follow Work You Genuinely Enjoy:** Adam believes the best career decisions come from pursuing work that you find intrinsically rewarding. Passion creates the motivation needed to continually learn, improve, and produce high-quality work over the long term.
- **Love Solving Problems, Not Just Writing Code:** While not every task is enjoyable, Adam finds fulfillment in tackling challenging engineering problems. A genuine curiosity for problem-solving is what keeps difficult work engaging and ultimately leads to sustained success.
- **There's No Perfect Career Blueprint:** Rather than trying to optimize every career decision in hindsight, Adam's experience suggests that success comes from consistently following opportunities that align with your interests and strengths. When what you enjoy also meets the needs of the industry, you're in an ideal position to thrive.

Original podcast link: [**https://www.youtube.com/watch?v=YA_OYJF3Mmw**](https://www.youtube.com/watch?v=YA_OYJF3Mmw)

Senior Managers Adam Admires

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, reflects on the engineers he most admires throughout his career and the qualities that set them apart. Rather than attributing success to a single skill, Adam highlights how exceptional engineers excel in different ways—from writing code and debugging complex systems to communicating ideas, launching new initiatives, and aligning teams. He emphasizes that there is no single blueprint for becoming a high-impact Individual Contributor.

- **Exceptional Engineers Have Different Superpowers:** Adam highlights colleagues who excel in distinct areas, including high-volume coding, deep debugging, launching ambitious projects, technical communication, and organizational alignment. There is no single path to becoming an outstanding engineer.
- **Leverage Your Strengths While Appreciating Others':** Adam recognizes that his own strengths lie in hands-on engineering, while others surpass him in areas such as cross-team leadership, strategic communication, and stakeholder management. Great engineering organizations thrive because individuals bring complementary skills.
- **Learn from Role Models, Not Copies:** Rather than trying to emulate one person completely, Adam encourages engineers to study the specific qualities they admire in others—whether it's technical depth, problem-solving, writing, or leadership—and incorporate those strengths into their own unique career path.

Original podcast link: [**https://www.youtube.com/watch?v=YA_OYJF3Mmw**](https://www.youtube.com/watch?v=YA_OYJF3Mmw)

IC9 Expectations

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, shares how his mindset evolved after reaching the highest levels of the Individual Contributor career path. Rather than obsessing over whether his work was "IC9-level," Adam explains why he stopped measuring success by job expectations and instead focused on solving meaningful problems. He discusses the importance of trusting feedback from managers, staying aligned with organizational priorities, and pursuing work that is both impactful and personally motivating.

- **Stop Chasing the Title, Start Solving Problems:** Adam believes that constantly worrying about whether your work is "senior enough" is counterproductive. Instead, focus on delivering meaningful solutions to the most important problems facing your organization.
- **Use Feedback as a Course Correction:** Regular check-ins with your manager help ensure you're investing your time in high-impact work. Honest performance feedback should be viewed as guidance to adjust direction—not as a measure of personal worth.
- **Do Work You Enjoy:** Adam attributes much of his long-term success to working on problems he genuinely enjoys. By aligning personal interests with organizational priorities, engineers can produce their best work without becoming consumed by the pressure of meeting a particular career level.

Original podcast link: [**https://www.youtube.com/watch?v=YA_OYJF3Mmw**](https://www.youtube.com/watch?v=YA_OYJF3Mmw)

Technical Depth vs Breadth

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, shares his perspective on what it takes to reach the highest levels of the Individual Contributor (IC) career ladder. Rather than choosing between technical depth and breadth, Adam explains how he developed both by following curiosity and solving real engineering problems. He describes a practical approach to learning unfamiliar systems, collaborating effectively across teams, and continuously expanding his expertise through hands-on experience instead of formal study.

- **Develop Both Depth and Breadth:** Adam believes senior engineers benefit from deep expertise in their primary domain while gradually building knowledge across adjacent systems. This combination enables engineers to solve complex cross-functional problems and make a broader organizational impact.
- **Learn Through Real Problems:** Instead of studying technologies in isolation, Adam dives deeply into unfamiliar systems only when they become relevant to the problem at hand. Solving real engineering challenges creates meaningful learning opportunities and builds lasting expertise.
- **Become Self-Sufficient and Collaborative:** By investigating issues independently before asking for help, engineers not only reduce the burden on partner teams but also arrive with informed questions and potential solutions. This approach accelerates learning, builds credibility, and strengthens cross-team relationships.

Original podcast link: [**https://www.youtube.com/watch?v=YA_OYJF3Mmw**](https://www.youtube.com/watch?v=YA_OYJF3Mmw)

Thoughts On Management

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, explains why he chose to remain on the **Individual Contributor (IC)** career path instead of transitioning into engineering management. He discusses how understanding his strengths, interests, and motivations helped shape his career, why deep technical expertise can be more valuable than constantly switching domains, and how long-term specialization enabled him to become a trusted expert within Meta's mobile engineering organization.

- **Know What Motivates You:** Adam chose to remain an Individual Contributor because his greatest passion is writing code and solving technical problems. He recognized that management requires a different skill set—such as organizational leadership, direction setting, and people management—that did not align with his strengths or interests.
- **Build Deep Expertise Over Constant Change:** Rather than frequently changing teams or technologies, Adam stayed within mobile engineering, allowing him to develop deep institutional knowledge and become an expert in the architecture, tooling, and infrastructure that powered Meta's iOS ecosystem.
- **Career Paths Should Match Your Strengths:** Adam emphasizes that there is no universally "correct" career path. While some engineers thrive by exploring new domains such as AI or AR/VR, others create greater impact by mastering a specific area. The key is aligning your career choices with the type of work you genuinely enjoy and excel at.

Original podcast link: [**https://www.youtube.com/watch?v=YA_OYJF3Mmw**](https://www.youtube.com/watch?v=YA_OYJF3Mmw)

Tech Career Growth Videos

Our instructional videos provide software engineers with insights needed for career growth. Masterclasses go incredibly in-depth on a specific tech topic while case studies are real examples from established engineering leaders.