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.

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.

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.

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)

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.

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.

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.

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.

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.