[Masterclass] How To Survive Tech Industry Layoffs

Layoffs: They will always be a part of the tech industry. 2022 was the first year of massive tech layoffs in the post-covid economy, and 2023 is sure to bear several more. Not even FAANG is safe with Meta, Microsoft, and Amazon all having layoffs in 2022.

There were a ton of important points from this masterclass, so here's our Top 5 (in no particular order):
- **Layoffs are effectively random for almost everyone** - Individual contributors (ICs) and more front-line managers are generally not privy to what happens behind the scenes with cut decisions. You can be a well-connected high-performer in a healthy revenue-generating org and still be laid off. It's crucial to recognize this reality and be at peace with it.
- **Stop freaking out** - Ironically, the worst way to deal with layoffs is to worry constantly and drastically alter your behavior to optimize for them. It's not healthy to go to places like Blind regularly to stay "up-to-date" with layoffs. The best way to deal with layoffs is to continue living your life as normal and double down on responsible software engineer behaviors. For more context on what those behaviors our, read this discussion: ["What are software engineering fundamentals?"](https://www.jointaro.com/question/3VNPK7wol76s89EkgFeW/what-are-software-engineering-fundamentals/)
- **Be deliberate with your performance review** - So many software engineers, junior ones in particular, assume that if they do good work and don't see any red flags, they'll get a good performance rating. This is very much not the case, especially at high-performance tech companies like FAANG. Maintain a transparent dialog about your performance with your manager and create a concrete growth plan. Here's our masterclass to help with that: [[Masterclass] How To Navigate Your Performance Review In Tech](https://www.jointaro.com/lesson/b0B8uqIAUnBLE10jJHJG/masterclass-how-to-navigate-your-performance-review-in-tech/)
- **Build a stellar, wide professional network** - It is more important than ever to build meaningful, high-quality relationships in the workplace. Tech is an inherently collaborative space: You need a multitude of connections to help you grow, vouch for you in performance review, and provide warm referrals for your next opportunity if you are laid off. If you want to deepen your network, watch this: [[Masterclass] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)
- **Getting laid off isn't the end of the world** - There's nothing wrong with you if you're cut during a layoff. Don't dwell on how you messed up or what you could have better to avoid the layoff: Focus on your next step. The silver lining is that getting laid off opens the door to your next opportunity and likely comes with some time in the form of a severance package to allow you to seriously think about your future. To optimize your next move, check out: [[Masterclass] How To Choose A Good Company And Team As A Software Engineer](https://www.jointaro.com/lesson/0WEmTNZOMIh8xAdfO3JH/masterclass-how-to-choose-a-good-company-and-team-as-a-software-engineer/)

Related resources:
- ["How to survive potential layoffs?"](https://link.jointaro.com/zGwioWXPLe8xhuA89)
- ["What are the signs of an impending layoff in an organisation that can help an employee prepare themselves better?"](https://link.jointaro.com/tkUnst8KKBdktPQq5)
- ["Staying motivated among lay-offs?"](https://link.jointaro.com/g9462CQrqy1KGtqR8)
- [Presentation Slides](https://docs.google.com/presentation/d/1Uyf04xDGTweN0ija_Z3nr9NZ_WsoDikh_54LR5AfZjU/)

System Design Series: Taro Playlists [Part 10] - This Is Just The Beginning

Congratulations, you made it to the end of our **system design** series! If you liked this series and want to see more like it, give this video and all the others in the playlist a like!

You can find the full [system design doc here](https://docs.google.com/document/d/15WaM8Ojan82g0m2mtz6kC2Hiyj0Q6VbjfqRmVNDI3qw/edit?usp=sharing) - Feel free to use it as a template for when you are working through a **system design** at your job!

Here are the core points from the video:
- Creating the **system design** doc is just the 1st step of the process: The next step is getting aligned from the team!
- Here are the steps to get strong alignment and the technical and overall product direction on a project:
  - Time-box the exercise: Have a firm date in mind on when this alignment needs to happen and work backwards from that date.
  - Share the doc with teammates and stakeholders and push them to leave feedback asynchronously. You can directly cc important people on relevant portions for them to look through.
  - Set up a tech review meeting as a forcing function to solidify all the alignment and talk through any remaining points of content. This meeting should probably be 45 minutes or more. Book it far ahead of time as senior+ engineers, tech leads, and managers tend to have very busy schedules.
  - Remind people before the meeting to go through your system design doc beforehand and try to resolve as many threads before the meeting as possible. You might need to do this several times.
- Everything covered in this system design series is effectively a requirement to be a competent senior+ engineer and tech lead, *especially* if you work at FAANG or some other Big Tech company.
- This can all be done reactively as well. If you're working on a small, tightly-knit team with very high synergy (common in startups), raw tribal knowledge and ad-hoc collaboration may be enough to ship projects consistently well. In this case, doing all this probably doesn't make sense. However, if your last couple projects have been pretty rocky, you might want to consider adding all the processes outlined in this series.

If after all this, you're still hungry for more **system design resources**:
- [How To Ace Your Big Tech Interview [System Design]](https://link.jointaro.com/NoVGhFiEErzfh61f6) - This is a full 1.25 hour masterclass, so prepare yourself for a **ton** of knowledge!
- ["How do I get better at building large scale systems without working directly on such projects?"](https://link.jointaro.com/Dm9wE33YC7ffwAPa6) - Question from a Senior Software Engineer at LiveRamp
- ["How to improve on non-technical skills like writing software design document?"](https://link.jointaro.com/T7GCmM4Z4CZhve4y5) - Question from a Mid-Level Software  Engineer at Microsoft
- ["My team has been doing architecture debates for months and we’re in gridlock."](https://link.jointaro.com/Zzx1NRMJFHvtHcvP8) - Question from a Senior Software  Engineer at Google
- ["How can I better contribute to system design discussions on my new team?"](https://link.jointaro.com/FH7ED2533nSTJSRc6) - Question from a Senior Software Engineer at Google

The Key Insight Behind Negotiation

Negotiation is fundamentally about leverage, and the strongest leverage comes from being able to walk away. Timing, preparation, and understanding the multifaceted nature of compensation are key to negotiating effectively.

- **Leverage is built through optionality**: The ability to walk away—especially when holding multiple offers—provides the greatest negotiating power. Desperation weakens a candidate’s position.
- **Don’t discuss compensation too early**: Deflect pre-interview compensation questions by focusing on mutual fit. Only begin negotiating after a formal offer is made.
- **Confirmed offers reflect high value**: By the time a company extends an offer, they've invested significant time and resources. With a low conversion rate from interviews to offers, candidates who make it to the offer stage are rare and valuable.
- **Companies don’t rescind offers for negotiating**: Especially in big tech, it’s extremely rare for a company to withdraw an offer just because a candidate is negotiating for better terms.
- **Compensation has multiple levers**: Salary, equity, and sign-on bonuses are negotiable components. Candidates can prioritize based on their risk profile and financial goals, trading one component for gains in another.

Ask Questions Well

What makes a high-quality question?

- You get the help you need
- You build trust with the person/group that you're asking the question to

Question asking is a deep skill that requires you to add sufficient context (but not too much) so people can easily help you.

- Prefer to ask in public forums
- Realize that your question may help others beyond you
- Your questions are a valuable signal to the team 

When you are asking a question, please don't just say hello and wait for them to respond: <https://nohello.net/en/>

Asking For A Promotion: The Wrong Way vs. The Right Way

We all want more money and a higher title. However, it's important to remember that it's not your engineering manager's primary goal to give you those things. When it comes to the promotion discussion, it's crucial to frame it in a mutually beneficial way.

Here are the core points from the video:
- **Do not**: Frame promotion as something that you inherently deserve from being on the team for a while, making the entire conversation seem like an exercise purely for *your* benefit.
- **Do**: Show your loyalty to the team and make it clear that investing into your growth and promotion is mutually beneficial. Your goal is to have more impact and empower the team - The money and title are more of a secondary benefit you'll happen to achieve along the way.

Related resources:
- [[Taro Top 10] Software Engineer To Engineering Manager (IC -> M Track)](https://www.jointaro.com/playlist/oz0mnJvHHgM8NfVF7rgp/)
- [[Masterclass] What Software Engineers Should Look For In Their Engineering Manager](https://www.jointaro.com/lesson/oeY7ncZhzJ5NO6dij5e7/masterclass-what-software-engineers-should-look-for-in-their-engineering-manager/)
- [[Taro Top 10] Getting Promoted Faster In Tech](https://www.jointaro.com/playlist/eZOEUatYEe7BBAZByuha/)

Why YOU Suck At Coding Interviews - From a Senior Engineer at Uber

[Edbert Chan](https://www.linkedin.com/in/edbert-chan-18a96950/) is a senior Android engineer at Uber. He wrote the popular guide “Welcome To The Coding Interview - You Suck” freely [available here](https://docs.google.com/document/u/1/d/1eKirumpmwDWTtKCJKn2HuoQ2NavEfR41whmTyaQcio4/mobilebasic) (and [here are the slides](https://docs.google.com/presentation/d/1vce04LepxDbu7K1ZyhtjVaSXC6Z0YYS9cAjNNztbEr4/edit#slide=id.p) presented).

If you want advice from Edbert, check out his AMA here: ["I'm Edbert, Ex-Apple current Uber Infra Android Engineer. AMA!"](https://www.jointaro.com/question/ftzODE689WYHw0FHGcl1/im-edbert-ex-apple-current-uber-infra-android-engineer-ama/)

This is a presentation about the common mistakes he has observed, and what you should do instead. Edbert believes that software engineers focus too much on the code and information during interview prep, and not enough on the engineering part of software **engineering**. Engineering is more than just coding, and a good interview process will be able to judge that.

The extensive guide is filled with practical tips for job seekers to pass the modern interview process at tech companies. Edbert covers the 9 mistakes that hold people back from passing technical interviews:

- Mistake 1: Not Putting Enough Time
- Mistake 2: Interview Approach Is Inconsistent
- Mistake 3: Your Interview Practicing Is Inconsistent
- Mistake 4: Not Fixing Your Own Mistakes
- Mistake 5: Not seeing how one decision or mistake leads to another
- Mistake 6: Not Understanding Your Own Solution Before Coding
- Mistake 7: Magic Bullets
- Mistake 8: Not Being Fast Enough
- Mistake 9: Being Full of Shit

Additional resources:

- [Ace Your Tech Interview And Get A Job As A Software Engineer](https://www.jointaro.com/course/ace-your-tech-interview-and-get-a-job-as-a-software-engineer/)
- [\[Taro Top 10\] Effective Interview Prep](https://www.jointaro.com/playlist/HLBYxJI7D1j8STolrwum/)
- [\[Masterclass\] How To Ace Your Big Tech Interview - Data Structures And Algorithms](https://www.jointaro.com/lesson/V4sTACzfOh22nMVcUV3w/masterclass-how-to-ace-your-big-tech-interview-data-structures-and-algorithms/)
- [\[Masterclass\] How To Ace Your Big Tech Interview - System Design](https://www.jointaro.com/lesson/J3I9fTW9ulr6T9KjxpqY/masterclass-how-to-ace-your-big-tech-interview-system-design/)

"How can I help with what you guys are doing with Taro?" - 9/13/2022

- If you can afford it, please [join Taro Premium](https://app.jointaro.com/membership)!
  - If you work at a Big Tech company, there's a good chance you have L&D (learning and development) budget that you can use to expense Taro and pretty much get it for free! Here's a [template](https://docs.google.com/document/d/1xpY2XBKTpiMN-o7U2c1pvqai5afQSVIuGMgQZiB-_Rg/edit) you can share with your manager to get Taro reimbursed.
  - Here are the companies we know of that can reimburse Taro: Meta, Google, Amazon, Robinhood, Airtable, Yelp, Gusto, Shopify, Gusto, New Relic
- Send us your feedback!
  - As an early user of Taro, you have outsized power for taking a bet on us. We listen very closely to all user feedback at this stage.
  - On the mobile apps, we have a "Send feedback" button in your profile.
  - We're also on LinkedIn and the [Tech Career Growth Slack](https://join.slack.com/t/techcareergrowth/shared_invite/zt-lt2tbjcn-LOAVIDuGPI~nkuc4woHDLg).
- If the Taro's content is helpful for you, share it!
  - In the mobile apps, there's a share button on every Q&A and video.
  - We spent a lot of time on the underlying tech for this sharing, using something called "dynamic links". They work on every platform, matching the user to the Taro web app, iOS app, or Android app accordingly.
  - Fun fact: Taro content links will open up within the Android app after you install it and sign-in if you are shared a piece of Taro content and didn't have the app yet.
- If you're on Taro Premium, please share your perspective and answer questions! One of our core goals is to diversify the perspective on the platform.

Voicing Your Problems And Frustrations Productively

Which of these are important things to remember as you are voicing your problems and frustrations?

Is the following a good way to voice a problem: I really hate how John thinks about the product. His vision does not make sense, and it will drag down the team. You can tell that he does not have enough experience.

"I really hate how John thinks about the product. His vision does not make sense, and it will drag down the team. You can tell that he does not have enough experience." - What is wrong with how this frustration is presented?

Effective communication of concerns in a one-on-one, especially with a manager, hinges on emotional intelligence and thoughtful phrasing. Expressing discontent is important, but how it’s framed can determine whether it leads to meaningful change or defensiveness.

- **Words and tone matter deeply**: It’s not about suppressing feelings, but about communicating them in a way that leads to constructive outcomes. Saying “This is holding me back” is more impactful than “I hate this person/project/org.”
- **Start with your experience**: Begin by describing how a situation makes *you* feel and the impact it's having on your work. This avoids sounding accusatory and centers the conversation on outcomes.
- **Avoid blaming language**: Statements that target others personally are rarely received well. Instead, focus on issues and processes rather than individuals.
- **Propose solutions thoughtfully**: Even if unsure, suggesting possible paths forward shows initiative. Phrasing like “One thing I was thinking about…” or “Could we try…” keeps the conversation collaborative and open-ended.
- **Frame feedback to enable support**: Managers are more able to help when you present challenges clearly and offer context. Productive expression of frustration builds trust and often leads to faster resolution.

By being candid *and* constructive, you increase the likelihood of being heard, supported, and ultimately driving the change you seek.

Write A Stellar Resume As A Software Engineer [Part 22] - Go Deeper: Follow Through

Download Alex's resume here: [Alexander Chiou Resume.docx](https://docs.google.com/document/d/1NnAx2jYkRTMCQwbdDPPqSj1Fwxkahda-/edit?usp=sharing&ouid=109380646850979301783&rtpof=true&sd=true)

If you have any questions about the content of this course or about your career overall, start a discussion in the Taro forum here: <https://www.jointaro.com/questions/create/>

Come to Taro events and join a resume review meetup: <https://www.jointaro.com/events/>

Join Alex for his Group Office Hours: <https://www.jointaro.com/p/alex-chiou/>

**UPDATE:** We have shut down Taro Networking as a feature. Sorry for the inconvenience 🙏

Nail Your Promotion As A Software Engineer [Part 3] - The Key To Understanding Promotion

We're told our entire lives that the key to success is to work hard. While this is admittedly true for most professions, it's very much not the case when it comes to software where you need to work *smart* in order to get anything done, especially for promotion. This lesson teaches you:

- The key insight behind understanding what promotion truly means, especially at top companies
- Why you can't get promoted by just working longer hours and writing more code, especially at very senior levels
- A framework to understand what separates incredibly senior (L6+) engineers from the more junior ones
- What it means to think multiplicatively instead of individually, including an in-depth example

Excited about developing better product intuition after watching this lesson? Check this out: ["How to develop product sense as an engineer?"](https://www.jointaro.com/question/w84sxyM805YOCokfvuQ8/how-to-develop-product-sense-as-an-engineer/)

Nail Your Promotion As A Software Engineer [Part 2] - You Can’t Job Hop To Success

A lot of software engineers give up way too easily when they're faced with substantial career resistance. You can't achieve that much genuine growth when you're constantly hopping around, and this reflects in both your level and compensation. This lesson teaches you:

- Why most engineers hit a wall when solely trying to job switch their way into higher levels, especially at senior and staff
- The defining trait of engineers who make it to incredibly senior engineering levels (Staff+)
- How to become a 10x engineer (i.e. Staff+ at a top company)
- Why it takes so long to truly settle into an organization and be able to demonstrate L6+ impact and behaviors

If you're interested in the 7 levels playlist, here it is: [Asking 7 Levels Of Engineers The Most Important Skill](https://www.jointaro.com/playlist/TnJFvWcvpUvFWLFjpY7X/) (here's the [combined YouTube video](https://www.youtube.com/watch?v=R1pg5kI0VI4))

Check out this discussion about the costs of being [perceived of being a "job hopper."](Perception of being a \"job hopper\"?)

[Masterclass] Should You Work At FAANG? - What Big Tech Is Like For Software Engineers

Working at FAANG isn't all sunshine and roses, which most software engineers don't realize. This masterclass extensively covers both the pros *and* cons of working at Big Tech, with the cons being angles that are rarely talked about online.

### Pros of Big Tech
- Compensation (obviously)
- Boosts your resume 10x, often automatically getting you phone screens
- Higher-quality and more well-rounded learning from being surrounded by talent
- In general, provides a solid foundation for your career across most crucial aspects

### Cons of Big Tech
- It's stressful - Between the sky-high expectations, PIP culture, and much more, most engineers find it difficult just to survive at Big Tech. The vast majority of SWEs at these companies have poor work-life balance
- Politics - There's so many cooks in the kitchen that it can be glacially slow to get anything done
- Growth wall at senior/staff - The senior promotion is notoriously difficult at FAANG, especially at Amazon and Google. You are often competing for scope against your teammates
- Unfulfilling work - Big Tech projects are usually very incremental, and you will own a tiny piece of a tiny piece of a tiny piece, especially if you're L3/L4 (junior/mid-level).

### Is Big Tech right for you?
- It depends! Work backwards from your career goals and use the information from this presentation to make an informed decision
- Big Tech generally pays higher dividends when you're earlier-in-career
- If you're a very experienced engineer who hasn't worked for Big Tech before, it can be dangerous. Work-life balances needs generally scale up with age, and it will be harder for you to adapt to the Big Tech style

Related resources:
- ["What's the difference between Big Tech and startups in terms of learning and growth?"](https://www.jointaro.com/question/KWXIrFIR1EIJsvdOdo7u/whats-the-difference-between-big-tech-and-startups-in-terms-of-learning-and-growth/)
- [How To Get FAANG Interviews](https://www.jointaro.com/lesson/pIMdopWoJFfbANnzo7U5/how-to-get-faang-interviews/)
- [[Masterclass] How To Choose A Good Company And Team As A Software Engineer](https://www.jointaro.com/lesson/0WEmTNZOMIh8xAdfO3JH/masterclass-how-to-choose-a-good-company-and-team-as-a-software-engineer/)
- [Presentation Slides](https://docs.google.com/presentation/d/1T5prt4AsEUxS1Yx5BvAIO4OYNFFGD5mCyv8g9UFzrTA/edit?usp=sharing)

This Is What Most Companies Get WRONG About Promotion

- 2 types of promotion:
  - **Strong companies:** Already functioning at the next level
  - **Weak companies:** Mastery of current level + long tenure
- In the best tech companies, each level is fundamentally different from the previous one. This is why promotion is lagging there: You need to be functioning at the next level consistently for 3-6 months before getting promotion.
- The goal is to avoid the Peter Principle: Getting promoted to higher and higher levels until you are completely incompetent. When levels are truly meaningful, it's really easy to be doing great at your current level and then be struggling to survive at the next one.

Not Getting Stuff Done? Find Someone To Call You Out

Why are accountability partners so helpful when it comes to productivity?

True or false: A good accountability partner is willing to shame you a bit sometimes.

How do good accountability partners help with excuses?

- Finding an accountability partner is one of the most powerful ways you can shore up your productivity.
  - You can understand your own potential when you see what your peers can do
  - They can offer help when you're feeling low or stuck
- Humans inherently don't like letting other people down: We're a social species. Just having someone who's expecting or even counting on you to make decent progress regularly makes you far more motivated to actually get stuff done out of fear of disappointing them.

Related resources:
- ["How do you network effectively within a company?"](https://link.jointaro.com/Hr1nr53D7sfQAEv3A)
- ["How can I better network with other software engineers in the Bay Area?"](https://link.jointaro.com/42JLsbppRMwAJAPUA)

Why Onboarding Matters

This video discusses the importance of onboarding and how it can significantly impact your reputation and career growth. 

If you imagine a "**Trust Meter**" where 0 means you have no trust and 100 means absolute trust, your default score as the new engineer will be around 50. Existing employees will think you are smart and have good intentions, but you need to work hard to increase the score and unlock larger-scoped projects. This hard work begins in onboarding.

The other reason the initial months in the company are important is because the tech industry is changing increasingly rapidly. When the average tenure at a company is &lt; 2 years, you need to figure out how to fully ramp up in a fraction of that time. Even within the same company, you will likely switch teams multiple times. Re-orgs are so common!

By approaching onboarding with a proactive plan and a sense of urgency, you can set yourself up for success and build strong relationships quickly.

Level Up Your Code Quality As A Software Engineer [Part 6] - Embrace The Pain

A defining characteristic of mediocre software engineers is that they run away from problems in their code and avoid confronting hard problems in general. This lesson will teach you:

- Why (and how) you should embrace the pain if you truly want to write better code as a software engineer
- The process to follow to go from writing bad code to good code
- What it means to actually learn system design
- How to level up your technical understanding with an in-depth example from Alex's past about how he truly mastered a deep Android concept and applied that mastery to learn iOS development almost instantly

How To Work With Your Manager To Get The Performance Review Rating You Want

Too many engineers are afraid of awkward conversations, so their plan is to just do good work and hope for the best. This rarely works.

Here are the points from the video:
- **Getting the rating you want is a team sport** - You need to be in-sync with others (particularly with your manager) on your desired outcome. You have to be transparent about what you want. Use your 1 on 1 to have those hard conversations with your manager on the delta between where you are now and where you want to be. It's painful to hear that you're falling behind, but it's much better to hear it 3 months before the performance review instead of 3 days before.
- **Don't assume that you're doing well** - Just because you're not receiving negative feedback doesn't mean that you're doing okay; the reality is that you could be doing as bad as trending towards PIP. Remember that managers are busy, and they can easily forget to give you critical feedback in a timely manner (or just not fully realize you're not doing well until they see peer feedback).

Related resources:
- [[Taro Top 10] Software Engineer To Engineering Manager (IC -> M Track)](https://www.jointaro.com/playlist/oz0mnJvHHgM8NfVF7rgp/)
- [[Masterclass] What Software Engineers Should Look For In Their Engineering Manager](https://www.jointaro.com/lesson/oeY7ncZhzJ5NO6dij5e7/masterclass-what-software-engineers-should-look-for-in-their-engineering-manager/)

Understanding The Differences Between Engineering Levels

True or false: Very senior engineers are at their levels because they act and operate in a fundamentally different way from their more junior peers.

How can you properly tell the more senior engineers from the others?

Which one of these is a core example of what a very senior (i.e. Staff or above) engineer would do?

Write A Stellar Resume As A Software Engineer [Part 1] - How This Course Works

It doesn't matter if you have mastered 500 LeetCode problems if your resume isn't even good enough to get you the interview to begin with. Writing a stellar resume is one of the absolute highest-leverage things you can do as an engineer yet so many mess it up, making basic mistakes. With this course, you will stop making those mistakes. Here are the core parts of the lesson:

- Your instructor [Alex Chiou](https://www.linkedin.com/in/alexander-chiou/) walks you through his extensive 10+ year Silicon Valley background with rapid career advancement, ending up as a high-performing tech lead making $750k at Robinhood. More importantly, he goes through how he reviewed (and rejected) 1,000+ resumes as he was extensively involved in the hiring loop of all of his prior companies.
- You'll understand why writing a stellar resume is actually quite easy, but the internet makes it hard due to misinformation
- We walk you through the course objectives. By the end of the course, you will understand:
  - 💡 Truly understand the **principles** behind a stellar resume
  - 🗑️ Avoid the common **traps** that make resumes suck
  - 💯 Get **maximum credit** by best framing your experience
  - 📊 Make the right resume based on your **level**
  - 🤔 Know what to do if your resume **isn’t enough**

Managing Up: Understanding Your Boss

Understand the preferred communication style of your boss:

- Preferences/pet peeves

- Strengths and weaknesses

- Work to earn trust

- Share your own style and best environment

Connect with [**Ethan on LinkedIn**](https://www.linkedin.com/in/ethanevansvp/)

Taro members get a discount to join [Ethan's Level Up community](https://levelupwithethanevans.substack.com/taro25)

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.