Code Review Is NOT For Catching Bugs

In this follow-up video, we dive deeper into the **true purpose of code review**, challenging the misconception that its main goal is to catch bugs. Instead, we emphasize how code review plays a central role in shaping team culture, accountability, and knowledge sharing.

### Key Takeaways:

- **We see code review as a cultural engine**: It’s a key mechanism for how our team communicates, transfers norms, and builds a shared understanding of quality and standards.
- **We’ve learned that code reviews aren’t about bug-hunting**: Studies—including from Microsoft Research—show that code reviews are not effective at finding bugs, even with multiple reviewers or approval layers.
- **We hold ourselves accountable for our code**: The responsibility for quality and testing lies with the author—not the reviewer. Code review isn’t a safety net for catching functionality issues.
- **We avoid over-reviewing**: Adding more layers of review slows us down without meaningfully reducing bugs. Instead, we focus on meaningful reviews that support learning and alignment.
- **We use code reviews for knowledge and culture transfer**: Through thoughtful feedback and shared context, we reinforce how we build, think, and collaborate—making code review a vital part of team growth.

[Masterclass] How To Navigate Your Performance Review In Tech

The slides provide a great high-level overview of the entire session for your notes, so here's our Top 5 thoughts that aren't entirely in the slides:

- Not deeply understanding your company's performance review cycle is job suicide, especially in the current age of layoffs and stack-rank (the latter being perennial).
- If you're truly working at a top company, you shouldn't be promoted to the next level unless you have been functioning there for at least 3-6 months. Companies that don't do this tend to promote due to raw experience and have many incompetent people at senior+ levels.
- Always have a plan for your performance review, even if your goal is just to be average and survive. Work with your manager at the beginning of every cycle to create a clear and living expectations document.
- Be very deliberate about the peers you want leaving feedback for you on your performance review. Assemble that cast at the beginning of the cycle and start building those deep 1 on 1 relationships once you have done that.
- When you are asked to leave constructive feedback for a peer, flip the question from *"What did they do poorly?"* to *"How can they expand their scope?"*. This will become easier as you reach an L5 (senior) level and more deeply understand what each engineering level means.

Related resources:

- [\[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/)
- [\[Masterclass\] How To Get Promoted Faster In Tech](https://www.jointaro.com/lesson/W730BOdrfAIXAEVd8HUf/masterclass-how-to-get-promoted-faster-in-tech/)
- [\[Masterclass\] How To Have Impactful 1:1 Meetings](https://www.jointaro.com/lesson/FEK6JZqW2Jg3rdN9yeGn/masterclass-how-to-have-impactful-1-on-1-meetings/)
- [Presentation Slides](https://docs.google.com/presentation/d/142PsWRJ-fmdP42CrFpR0VD64L1qFP-6nPTmjk5g1DKM/edit?usp=sharing)

How To Earn Respect Fast - Senior Engineer Onboarding Story

Even if you're onboarding, you can earn respect amongst your team. In fact, you should feel empowered to earn this respect despite being new, especially if you're a senior software engineer.

Here are the core points from the video:
- **Help junior engineers** - This is one of the most effective ways to earn respect on a team as a more experienced engineer. The junior engineers may be more fluent in the code than you are, but if you're a senior+ engineer, there is a reason you have this level: You have certain fundamentals and instincts that are applicable everywhere that junior engineers don't really have.
- **Show your depth** - You won't win with velocity and output when you're new. However, you can win with depth and quality as that's largely a function of your effort and time. If you're a more experienced engineer, think about how you can go deeper into something than everyone else on the team.
- **Alex's senior engineer onboarding story** - Here's how a senior Android engineer quickly made a splash after joining Alex's team back at Instagram.
  - They saw a junior engineer struggling with a very complex text layout bug with the Instagram Android app.
  - They volunteered to help with this bug, even though they didn't have to.
  - After many failed debugging attempts, *they slowly extracted the relevant code line by line into an entirely separate Android app to identify the breaking line*. This was a brilliant tactic that nobody else on the team even remotely considered.
  - This combination of goodwill and extreme software engineering depth earned them a mountain of respect pretty much immediately.

This clip is from our masterclass on how to succeed at a new team or company as a software engineer. [Click here to watch the full thing.](https://link.jointaro.com/9sJzfDeH3JdWzZRg9)

Related resources:
- ["How can I quickly gain respect among my team as a senior engineer?"](https://link.jointaro.com/i9j4dtohx2bXc2Sq8)
- ["How do you network effectively within a company?"](https://link.jointaro.com/Hr1nr53D7sfQAEv3A)

How Alex Got Into Meta With 0 Prior LeetCode Experience

Write A Stellar Resume As A Software Engineer [Part 2] - Why You NEED A Killer Resume

As a software engineer, there are a million different things you can do. Choosing the right things to work on from engineer to engineer, but the good news is that having a great resume is one of those right things for every engineer. This lesson teaches you:

- Why optimizing your resume is one of the highest return on investments you can possibly do
- Understanding the overall job search funnel and how a good resume fits within it

Top System Design Interview Mistakes [Part 7] - Document As You Go

In system design interviews, it's essential to use multiple forms of communication—verbal, written, and visual. A common mistake is relying only on verbal communication, which can lead to confusion and missed opportunities to iterate on your design.

- Not writing anything down makes it difficult to follow your logic, especially when discussing complex systems. Without written or visual references, both you and the interviewer may struggle to keep track of the design.
- Documenting as you go—whether through diagrams, lists, or notes—makes it easier to iterate on and debug your design. It also frees up your mental resources to focus on solving new problems instead of remembering all the details.
- Finally, well-documented designs provide a useful reference for interviewers when they review your performance after the interview.

If you need extra help with your system design interview, [Formation.dev](https://formation.dev/partners/taro) can provide you hands-on, personalized support. Join us here: <https://formation.dev/partners/taro>

20 Years Of Fighting Procrastination [Part 5] - Debug Your Productivity

Procrastination thrives when you confuse learning with progress. Here are the core points from the lesson:

- Jumpstarting productivity means producing *before* you feel ready — even a rough draft unlocks momentum
- Replace the one-way flow of tutorials with a feedback loop: code → learn → refine
- Writing personal notes or process logs boosts clarity and reduces future ramp-up time
- Systematize repeatable work into reusable components to move faster with each project
- Build a library of “done before” artifacts you can copy, tweak, and ship again and again

Top System Design Interview Mistakes [Part 9] - Don't Draw Random Boxes

In this video, we discuss a common mistake in technical interviews: drawing random boxes without considering the bigger picture. Here are the key points we cover:

- Candidates often create isolated components without thinking about how they connect
- We provide an example contrasting a disorganized approach with a more thoughtful one
- Our recommended approach: Trace through data flows and user perspectives
- The goal is to think like an engineer: Identify the right problems before proposing solutions
- **Our main advice:** Don't just draw random boxes, trace data flow to uncover key system challenges

If you need extra help with your system design interview, [Formation.dev](https://formation.dev/partners/taro) can provide you hands-on, personalized support. Join us here: <https://formation.dev/partners/taro>

Top System Design Interview Mistakes [Part 10] - Don't Speak Only in Hypotheticals

In this video, we discuss a common mistake in technical interviews - Talking only in hypotheticals instead of applying knowledge to practical scenarios. Here are the key points we cover:

- Many candidates discuss system design concepts theoretically without considering real-world applications
- We provide an example contrasting a hypothetical approach with a more practical one
- The goal is to show real-world engineering skills, not just theoretical knowledge
- **Our main advice:** Avoid "it depends" answers and make assertive decisions with proper justification

If you need extra help with your system design interview, [Formation.dev](https://formation.dev/partners/taro) can provide you hands-on, personalized support. Join us here: <https://formation.dev/partners/taro>

Nail Your Promotion As A Software Engineer [Part 15] - It's Not Just About Impact

*"I'm not getting promoted because my manager isn't giving me the proper projects"* is one of the classic excuses of software engineers who want to get promoted but are definitely not functioning at the next level. This lesson teaches you:

- Why impact has devolved into a near meaningless buzzword
- The right mentality to have when it comes to picking projects and thinking about impact
- The 6 axes that determine how much you get rewarded for working on a project (only 1 of them is impact)

To learn more about identifying the best projects and prioritizing properly, go through this discussion: ["How to figure out what the most important projects are?"](https://www.jointaro.com/question/CgCPA60bDDHoOteN7Lmb/how-to-figure-out-what-the-most-important-projects-are/)

Avoid This Performance Review Death Trap - Creating An Expectations Plan

- Work with your manager at the beginning of your performance review cycle to create a plan. Do this no matter what: Even if your goal isn't too ambitious and you just want to get an average rating.
- The plan should outline expectations for you very clearly, ideally as a checklist:
  - What does it mean to hit your baseline expectation and not be in danger of a performance improvement plan (PIP)?
  - What does it mean to knock it out of the park?
- Things will change, especially in high-performance tech companies. This document will change over time, and you and your manager should be 100% aware of this and adapt.

Grow From Mid-Level To Senior Engineer [Part 9] - Code Quality

Mid-level engineers are usually very solid at coding, but what most don't realize is how high the ceiling truly is when it comes to code quality. This lesson teaches you:

- The difference in code quality between junior, mid-level, and senior engineers
- What a senior engineer level pull request looks like

Become a code quality master by taking our course here: [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

How To Be An Effective Tech Lead [Part 4] - Go Deep, Not Broad

In order to become a tech lead, you need to have incredibly effective technical skills. So what does that mean?

- What it takes for your technical skills to be respected as an engineer
- Why depth is more important than breadth
- What it means to have true technical depth, shown with an in-depth example

To sharpen your technical depth, take our code quality course: [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

The Common Misconception With Help

When you're new, there's an overwhelming amount of information to absorb. You should plan to ask many, many questions, which means it's important to have the right framing of that interaction.

Obligatory Confucious quote:

> The man who asks a question is a fool for a minute, the man who does not ask is a fool for life

Myth #1:

- **Myth**: Asking for help is a sign of weakness ❌
- **Reality**: You’re expected to ask questions to gain knowledge and foster interaction ✅

Myth #2: 

- **Myth**: Everyone knows so much more than me, I’ll waste their time ❌
- **Reality**: Each person’s knowledge is incomplete ✅

Instead of thinking that building expertise in something is difficult or impossible, realize that **you can become more knowledgeable than anyone** as long as you narrow the scope appropriately. (e.g. "In one afternoon, I can go understand more about the flags to configure **git log** compared to anyone on my team of 10 people.")

[Case Study] How To Land 18 FAANG+ Offers With Steven Zhang (Airtable, USDR, Tableau)

While on the job hunt in 2019, Steven Zhang received 18 offers (out of 22 onsites), including from companies such as Airbnb, Apple, Facebook, Palantir Technologies, Pinterest, Stripe, Uber.

In the process, he became an expert in software engineering interviews and job searching. Steven shared his thought process and methodology:

- When you have many interviews, **operationalize it, and treat it like a multi-week/month project**. Some days will feel like a slog, but that's ok and part of the process. (Steven used Airtable to coordinate all his conversations.)
- **Doing an interview prep course is completely worth it for DSA**. It may cost a few thousand dollars, but being able to land the ideal job is definitely worth it (and likely worth tens of thousands of $$). Steven used InterviewKickstart (his referral: https://bit.ly/swe-tips-ik).
- **For behavioral interviews**, Steven recommends:
  - Writing all questions you received in a Google doc
  - Recording yourself doing mock interviews with a friend and then listening to it.
- **Steven received offers at various levels through the bands**, from L3 (junior) to L5 (senior). Your level has huge implications for your compensation.
- Negotiation tips:
  - Negotiation should not be adversarial- think of it as doing price discovery
  - If you ask nicely, no one will rescind your offer for asking for more money.
  - Negotiation/post team matching is a way to get signal on the company itself

Relevant resources:

- [\[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 Alex Got Into Meta With 0 Prior LeetCode Experience](https://www.jointaro.com/lesson/ZYiTbN21FsqFxFdpwt5a/how-alex-got-into-meta-with-0-prior-leetcode-experience/)
- Steven's [viral Medium article about this experience](https://medium.com/@stevenzhang/how-i-landed-18-faang-software-engineer-offers-after-not-interviewing-for-5-years-fc0dfc957a5d).
- Connect with [Steven on LinkedIn](https://www.linkedin.com/in/stevenqzhang/)

Maximize Your Equity And Benefits In Tech [Part 1] - Introduction

Hi, I’m Andy​​! 👋 In this course we’re going to cover the most common forms of equity compensation and benefits in tech, break them down, and provide strategies and thought frameworks for helping you maximize them.

- [Connect with Andy on LinkedIn](https://www.linkedin.com/in/andymoranio)
- [Leave feedback and/or sign up for Andy’s newsletter](https://subscribepage.io/taroequitycourse)
- [Schedule a consultation](http://adastrafp.com/contact-us/)

Maximize Your Productivity As A Software Engineer [Part 6] - Social Pressure > Work Pressure

Too many software engineers focus on finding something cool to work on instead of finding cool people to work with. This lesson teaches you:

- Why a supportive team is far more valuable and effective when it comes to making you productivity compared to working on something shiny like genAI
- Tactics you can use to apply social pressure to yourself and enforce productivity

Learn how to find a good team here: [\[Taro Top 10\] How To Find A Good Engineering Team And Company](https://www.jointaro.com/playlist/FWqTGeZYrXFohCOU38sR/)

DSA Crash Course [Part 12] - Pair Sum Approach

In this lesson, Alvin explores the strategy to solving the following interview problem:

> Write a function, *pair_sum*, that takes in a list and a target sum as arguments. The function should return a tuple containing a pair of indices whose elements sum to the given target. The indices returned must be unique.
>
> Be sure to return the indices, not the elements themselves.
>
> There is guaranteed to be one such pair that sums to the target.

```
pair_sum([3, 2, 5, 4, 1], 8) # -> (0, 2)
```

```
pair_sum([4, 7, 9, 2, 5, 1], 5) # -> (0, 5)
```

```
pair_sum([4, 7, 9, 2, 5, 1], 3) # -> (3, 5)
```

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: <https://www.linkedin.com/in/alvin-zablan-b73a92117/>

A Huge, Often Unused Way Your Manager Can Help With Promotion

- Your manager is critical to your promotion. More specifically, if your manager is not supportive of your promotion case, it is near impossible for you to get promoted.
- You need to create a plan with your manager as soon as the performance review cycle starts to set expectations on what you need in order to be a good candidate for promotion. It should be modal and detail the following:
  - What it means to meet expectations
  - What it means to exceed expectations
  - What it means to totally crush expectations
- Regularly work with your manager to get feedback and understand your progress for this plan

PIP In Big Tech -- Amazon, Meta, Google

In this section, we cover the path for employees to enter a PIP for three Big Tech companies — Amazon, Meta, and Google.

At **Amazon**, the poor performance rating is called **Needs Improvement (NI)**. Poor performers are put on a Focus, which is a development plan to get back on track. Think of it like a warning. If the focus does not do well, the employee is put on a Pivot, at which point the options are to leave the company or accept a PIP. Learn more here: <https://www.jointaro.com/topic/amazon/performance-review/>

At **Meta**, the poor performance rating is called **Meets Some (MS)** or **Meets All (MA)** Expectations. If the HRBP (Human Resources Business Partner) is part of your review meeting, a PIP is likely. One unique policy of Meta is something called "up or out." This requires engineers to get promoted every few years until hitting Senior Engineer \[E5\]. Learn more at <https://www.jointaro.com/topic/meta/performance-review/>

At **Google**, the poor performance rating is called **Not Enough Impact (NI)** or **Moderate Impact (MI).** A "Support check-in" indicates poor performance and candidate for a PIP. Google is generally more laid-back when it comes to performance compared to other companies. Learn more here: <https://www.jointaro.com/topic/google/performance-review/>

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.