Defending Your Org

In this lesson, we discuss how to **build enough influence and organizational strength that targeting you—or your team—simply isn’t worth the effort**. Whether dealing with a self-interested colleague or another organization competing for your scope, protection comes from understanding other people’s motivations, building strong support around your work, maintaining high performance, and creating a compelling narrative for why your organization should remain intact.

1. **Build enough soft power to become an unattractive target:** Strong relationships, allies, organizational support, and a track record of performance can make attempts to undermine you significantly more difficult and costly.
2. **Understand the story other people tell themselves:** People rarely view their own actions as malicious. Understanding how others rationalize their behavior can help you anticipate their moves and frame cooperation with you as the most practical choice.
3. **Defend your organization with performance and narrative:** When other teams compete for your scope, demonstrate the value and complexity of your work, highlight the costs and risks of disruption, and clearly articulate why keeping the organization intact serves the broader business.

Original podcast link:[ https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s](https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s)

Be Interpersonally Warm & Professionally Firm

In this lesson, we discuss how to **communicate what you want while remaining collaborative, empathetic, and persuasive**. The key is to be “interpersonally warm” while staying “professionally firm”—clearly advocating for your needs without turning the conversation into a confrontation. By treating the other person as a human being with their own pressures and priorities rather than an obstacle to overcome, negotiations can become opportunities to find mutually beneficial solutions.

- **Be warm personally, but firm professionally:** Clearly communicate what you need while remaining friendly, calm, and respectful instead of introducing unnecessary tension or an “us versus them” dynamic.
- **Ask for help rather than make demands:** Phrasing requests around questions like “How can you help me?” invites collaboration and creates an opportunity to understand what both sides need to make an agreement work.
- **Treat people as partners, not obstacles:** Whether negotiating with your manager or another team, understanding the other person’s constraints and motivations can help you find solutions that work for both sides—while recognizing that even excellent communication cannot guarantee agreement.

Original podcast link:[ https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s](https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s)

How Mutiny Works

In this lesson, we discuss what happens when **employees believe their manager is underperforming and consider escalating the problem to their skip-level leader**. Raising concerns about a manager can be difficult because acknowledging the problem creates significant work for senior leadership. The conversation explores why a single complaint may be dismissed and how multiple independent reports can make an organizational problem much harder to overlook.

- **Understand your skip-level manager’s incentives:** Accepting that a manager is failing may mean managing them out, finding and training a replacement, and temporarily absorbing their responsibilities—giving senior leaders practical reasons to be cautious before acting.
- **A single complaint may be interpreted as an individual conflict:** When only one employee raises a concern, leadership may question whether the issue lies with the manager or the employee making the complaint.
- **Corroborating experiences make concerns more credible:** When several employees independently report the same pattern of behavior, it becomes easier for senior leadership to recognize that the problem may be systemic and requires investigation or action.

Original podcast link:[ https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s](https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s)

Scope Grabs And The "Polite Fiction"

In this lesson, we discuss how leaders manage **high-performing employees who are also highly ambitious and demanding about their career progression**. Rather than viewing those ambitions as a problem, effective managers can turn them into mutually beneficial agreements—clearly defining what the employee needs to accomplish and, in return, committing to advocate for the opportunity or promotion they want.

- **Turn career demands into mutually beneficial deals:** When a high performer wants a promotion or greater opportunity, managers can establish clear expectations: deliver exceptional results on important business priorities, and leadership will help create the case for advancement.
- **Trust depends on following through:** These informal agreements only work when leaders honor their commitments. Circumstances can change, but employees can often distinguish between a manager who breaks a promise and one who genuinely loses the ability to deliver it.
- **Senior promotions often involve a queue:** At higher levels, promotions become rarer, more expensive, and sometimes constrained by organizational needs or quotas. Leaders may maintain forward-looking promotion plans, making career progression partly about understanding where someone sits in the pipeline and what they need to demonstrate to move forward.

Original podcast link:[ https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s](https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s)

Deal Making with Your Manager

The Hidden Agenda In Reorganizations

In this lesson, we discuss the **hidden considerations that can shape company reorganizations beyond their stated business purpose**. While reorgs are often triggered by legitimate changes such as entering a new market, launching a project, integrating an acquisition, or responding to a leader’s departure, senior leaders may also use them as an opportunity to address promotions, retention, performance, and leadership development at the same time.

- **Reorgs often serve multiple objectives:** Once the business need for a reorganization is established, leaders may also consider who needs greater scope, which high performers they want to retain, and where different employees should sit within the new structure.
- **Retention and performance influence the design:** Leaders may use a reorg to give valued employees more attractive opportunities while structuring changes so that the potential departure of lower-priority employees is less disruptive.
- **Leadership changes can create cascading reorgs:** When a senior leader leaves or moves roles, entire teams may need to be reassigned, sometimes placing teams under unexpected leaders or using the transition as an opportunity to stretch someone into a broader leadership role.

Original podcast link:[ https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s](https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s)

Empire Building & Headcount Thresholds

In this lesson, we discuss **empire building**—the tendency for managers to focus on increasing the number of people they oversee rather than the actual impact their teams create. The conversation explores why headcount becomes a convenient proxy for leadership scope, how promotion requirements can unintentionally reward organizational growth, and how these incentives can lead to reorgs and staffing decisions driven more by career advancement than genuine business needs.

- **Why empire building happens:** Measuring a manager’s true impact is subjective and difficult, while headcount is simple and visible—making team size an easy proxy for leadership scope and promotion readiness.
- **Promotion incentives can encourage unnecessary growth:** When companies establish formal or informal headcount thresholds for senior roles, ambitious managers may be incentivized to acquire teams or additional reports simply to meet those requirements.
- **Headcount-driven incentives can distort organizations:** Teams may be moved between managers, temporarily reassigned, or reorganized to create the necessary “scope” for promotions—even when those changes have little to do with what is best for the business or employees.

Original podcast link:[ https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s](https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s)

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.

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.

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.

Leverage Your Unfair Advantage

We explain how to accelerate your job search after a layoff by intentionally leveraging the advantages already on your résumé. Here are the core points from the lesson:

- We should leverage company brand as an unfair advantage, since recognizable names (Big Tech, well-known startups, or respected niche companies) carry trust and credibility that immediately raise our odds versus the average applicant.
- We can increase our chances by targeting adjacent companies, customers, or competitors where our background naturally fits, instead of applying randomly to roles with no contextual advantage.
- We should confidently lean into domain and product association—using the halo effect of teams, products, or problem spaces we worked on—because perceived relevance often matters more than perfect technical alignment.

Verify Your Severance Package

We explain what to do immediately after a layoff to protect yourself financially and legally, and to reduce unnecessary stress. Here are the core points from the lesson:

- Most large tech companies provide severance due to legal requirements and long-term reputational incentives, but layoffs are messy, so you must carefully review all paperwork and verify dates, vesting, and severance amounts.
- Never sign termination documents on the spot; take time to review them, ask questions, and involve a lawyer if possible, especially for severance disputes or visa-related considerations.
- After a layoff, it’s critical to understand your personal burn rate and runway by reviewing your finances, since clarity around how long you can sustain yourself reduces anxiety and helps you plan your next steps.

Build Up Relationships

We highlight why building strong relationships and social capital is essential for career resilience, especially during layoffs. Here are the core points from the lesson:

- Relationships are a form of social capital, and having people who know you, like you, and will advocate for you can directly influence whether you survive layoffs or get new opportunities.
- Engineers often underinvest in relationship-building by staying heads-down, but proactively connecting with managers, skips, and peers across teams is increasingly important in today’s economy.
- Building relationships doesn’t require forced networking—it can happen naturally through code reviews, coffee chats, offsites, and one-on-ones if you are intentional about seeking opportunities.
- No matter how senior or skilled you are, everyone is expendable, so you should never rely on company loyalty alone and should continuously invest in relationships that outlast any single job.

Grow Fundamental Skills

We explain why growing fundamental, transferable skills is one of the most powerful ways to reduce layoff risk and strengthen long-term career resilience. Here are the core points from the lesson:

- There is far more to software engineering than coding, especially at scale, where communication, project management, leadership, and relationship-building determine whether work actually ships.
- Over-indexing on a specific technology, language, or product is risky, because teams, systems, and entire products can disappear, while transferable skills allow you to move across teams or companies.
- Engineers who can clearly design systems, think through edge cases, write thoughtful plans, and communicate tradeoffs create outsized impact compared to those who jump straight into code.
- So-called “soft skills” are actually the highest-leverage skills, because they compound across roles, companies, and industries, while technical tools and frameworks inevitably change.
- Focusing your time on high-leverage problems and influence, rather than low-level tooling details, is what drives career growth, adaptability, and durability during periods of layoffs.

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.