Make Sure To Set This Up With Your Manager To Ace Your Performance Review

- Work with your manager to figure out which peers you should request feedback from at the end of the cycle: They may already have a bunch of peers in mind!
- Once you figure out these key peers, talk with them upfront about your goals, especially if they're ambitious and you're gunning for promotion. Work with them early to build this relationship, especially if they're more senior.

Grow From Mid-Level To Senior Engineer [Part 19] - Onboarding

Onboarding is one of the most important processes for any healthy engineering team. Helping the newbies is both critical and rewarding. This lesson teaches you:

- How a senior engineer levels up the team more when helping with onboarding compared to a mid-level engineer
- Different ways to achieve multiplicative impact with onboarding instead of singular, even when you are the one onboarding!

Grow From Mid-Level To Senior Engineer [Part 22] - Instagram Ads Survey Cleanup Workstream

See something, say something: You'll be surprised at how much opportunity you can find by championing this mentality, including to senior levels. This lesson goes through:

- The weird organizational dynamic that led to a bunch of senior scope existing "for free" but easy to ignore as a junior or mid-level engineer
- The simple but powerful trick Alex used to turn several smaller issues into a senior-level project
- How Alex continued to deepen the impact of this survey cleanup workstream by digging deeper and doing the right thing
- The learnings from this case study that you can apply to your day-to-day to find senior scope

DSA Crash Course [Part 52] - Graph Warm Up Lecture

In this lecture, Alvin reviews how to implement a basic depth-first and breadth-first traversal on a graph.

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/>

Senior Engineer (L5) Describes Most Important Skill - Richard Chen

Richard is a Senior Engineer (E5) at Meta.

- **Most important skill**: correct project selection. This requires balancing outcomes, priorities, and risks.
- **Advice**: bring people along with you. Careers are built over the long-term, so it's important to treat partners and work colleagues well.

Here's the full playlist asking engineers what the most important skill is for their level: [Asking 7 Levels Of Engineers The Most Important Skill](https://www.jointaro.com/playlist/J9Io5lDGaYUpI8vGrUyI/)

Helpful links:
- Taro's top 10 to get promoted from [entry-level to mid-level engineer](https://www.jointaro.com/playlist/iBKHYpkjd0BRWWLKQG2j/)
- Taro's top 10 to get promoted from [mid-level to senior engineer](https://www.jointaro.com/playlist/AUMiBTvYUv0gcOzuu26V/)
- Taro's top 10 to get promoted from [senior to staff engineer](https://www.jointaro.com/playlist/YD8LMCSlE71VUGUbNAWM/)
- [Richard on LinkedIn](https://www.linkedin.com/in/r-x-c/)

Asking Great Questions [Part 6] - Be Clueless In Public

The best software engineers are those who embrace their lack of knowledge. This lesson teaches you:

- Why it's better to ask your question in a broader audience
- The difference levels of visibility when asking a question with higher being better
- A huge, often unknown benefit that comes with asking questions in public which allows even junior engineers to become leaders
- Why you should always try to create a record of your question and its answer(s)

The Incredibly Rare Benefit Top Tech Companies Offer - Equity Refreshers

This video segment explains **refresher equity grants**, a powerful and rare form of compensation offered mainly by top-tier tech companies like Facebook and Google. These grants serve as both a performance incentive and a retention strategy.

- **Refresher grants are annual RSU awards**, given in addition to the initial offer. Their size is determined by an employee's level and most recent performance review.
- **Compensation structure is formulaic** at big tech companies, including the calculation of refresher amounts, which often outpace inflation even in challenging economic climates.
- **Grants stack over time**, meaning employees may have multiple overlapping equity packages (original + yearly refreshers), significantly increasing total stock-based compensation over the years.
- **Year four marks a peak**, where compensation from the initial grant and up to three refreshers overlap—this is why many employees leave after their fourth year, as compensation often drops after the original grant fully vests.
- **Refresher grants are a major retention tool**, helping extend average tenure at top companies from around two years closer to four.

[Become A Go-To Person 9/18] The Formula For Expertise

A course by [Jordan Cutler](https://www.linkedin.com/in/jordancutler1/), Senior Software Engineer at Pinterest and Author of the [High Growth Engineer Newsletter](https://read.highgrowthengineer.com/)

Write A Stellar Resume As A Software Engineer [Part 19] - When You Don't Have Enough

A 1-page resume is the golden standard, and engineers usually mess up by going above that 1 page. However, what happens if you're incredibly junior and you're the opposite, having less than 1 page? This lesson teaches you:

- How to stretch your Education section on your resume
- What to do with your resume's project section when you're just a student
- Other simple tricks to make your resume longer and fill up that 1 page

Handling a PIP: The Ultimate Guide To Navigating A PIP

There are two options after a PIP: either the employee will remove all the doubts about the performance concern, or the employee will be terminated.

Your job as an employee is to judge your manager’s intentions. Your manager is the most important person in the PIP, and more generally, in your career. Many managers view the PIP as a formality before termination, and they’ve already given up on you. In that case, **you need to leave.** You don’t win any bonus points by "proving them wrong."

If the manager is responsive to your questions, provides constant feedback, and has a reasonable PIP plan, you may have a chance to succeed.

However, in the vast majority of cases, our recommendation is that you **must start looking for a** **new job.**

The biggest reason a PIP is not worth fighting is because **you want to work for people who believe in you**. This is critical for career success: you need someone who is unfailingly supportive of you, whether that's a friend, mentor, or manager. A PIP does not feel like support. In fact, it feels like the opposite. Your manager felt your performance was weak enough that they literally spent hours documenting how you fell behind, and then informed you in a legal manner.

The joke is that PIP should stand for “Paid Interview Period”, and that is honestly our recommendation for many tech workers who receive a PIP.

Here is the **PIP Evaluation Framework** in order to make the best decision once you’ve received the PIP. If 1+ of the following are true, you should **not** plan to have a long-term future at your current company.

- Your manager is uncommunicative or closed off
- The time horizon for the assigned work on the PIP is unrealistic (e.g. 1 week for a launch)
- The goalposts for the projects keep shifting
- The PIP work and your “normal duties” result in an unmanageable workload
- Your team is unsupportive

Come Up With 500k+ User Project Ideas [Part 7] - The Alex Formula

Repeated excellence is the key to any very successful tech career. Alex has accomplished this time and time again with around a dozen side projects that have 10,000+ users, and he's here now to spill the beans. This lesson teaches you:

- The exact playbook Alex uses to repeatedly build successful apps with several thousand users
- The "Honer vs. Innovator" philosophy when it comes to understanding engineer types
- Why you should (probably) stop trying to be Steve Jobs and go hard down the innovator route
- How honers are often incredibly underrated and can still achieve stellar career outcomes
- The ideal place to be on the honer &lt;-&gt; innovator spectrum when it comes to side projects

20 Years Of Fighting Procrastination [Part 15] - Conclusion

Congratulations on making it to the end of the course! While watching great content like this feels good - It doesn't actually mean anything unless you put the learnings into practice. With that being said, here's some ideas for "homework" for you:

- Start sleeping consistently every day, even on weekends
- If you have a task or project that will take at least 1 week, decompose it into at least 3 different sub-tasks
- Set up a meeting with yourself on a regular basis to reflect on your productivity
- Go through your calendar, audit all the meetings, and kill as many as you can

If you want to learn how Rahul's cofounder Alex made $750,000 per year at Robinhood working \~35 hour weeks, you can go to the next level and take his much deeper and more concrete productivity course here: [Maximize Your Productivity As A Software Engineer](https://www.jointaro.com/course/maximize-your-productivity-as-a-software-engineer/)

Master The Behavioral Interview [Part 21] - Record Yourself

Behavioral interviews are inherently difficult as they're very open-ended and there's no such thing as a 100% "right" answer. Luckily for you, behavioral interview questions are incredibly easy to simulate. This lesson teaches you:

- How to properly record yourself for behavioral interviews
- What kinds of questions you should be asking yourself in behavioral interview recordings
- Creative ways to make behavioral interview recordings more realistic
- How to analyze the quality of your behavioral interview response recordings

Master The DSA Interview [Part 18] - Fishing

Many engineers think that they got rejected due to the interviewer being bad or "out to get them". While low-quality interviewers do exist (and there are a lot of them), it is often the engineer's fault by being a weak candidate. This lesson teaches you:

- Why there is often a discrepancy between what engineers believe is the cause of their data structures and algorithms interview rejection and what reality actually is
- What fishing is and how it forces interviewers into a very awkward situation that makes them seem icy to the candidate
- How to not do fishing during an interview so you can have a real chance of passing (and make the interviewer more likely to help you)
- Why asking the interviewer for a raw hint is a recipe for failure

Become An Engineer Influencer [Part 3] - Strategy #1: Catering to Your Strength

Master The DSA Interview [Part 17] - How To Pass FAANG DSA Rounds

Why is it so hard to break into FAANG? Well, it's because FAANG tends to push engineers far harder on data structures and interviews problems. This lesson teaches you:

- The score spectrum FAANG interviewers use to grade candidate
- What it means to get a "Yes" vote on a data structures and algorithms round
- What it means to get a "Strong Yes" vote on a data structures and algorithms round (very important when the market is bad)
- What a strong passing data structures and algorithms interview performance looks like, explained with an in-depth example

Master The DSA Interview [Part 10] - Run-Time Analysis

After clarifying the problem and coming up with a detailed, granular plan, coding up the solution should have been trivial. Now it's time for big O. This lesson teaches you:

- How to actually learn run-time analysis instead of memorizing the big O of every individual problem
- The structure of a strong run-time analysis for a data structures and algorithms problem
- Exactly what a quality run-time analysis looks like, explained with an in-depth example

How To Be An Effective Tech Lead [Part 17] - Go Deeper: Follow Through

Congratulations on making it to the final lesson of the course! This lesson teaches you:

- The key takeaways of being an effective tech lead
- Technical items you can take on to start being a better tech lead
- Leadership items you can take on to start being a better tech lead

For further support, start career discussions in the Taro forum to get top-tier advice: <https://www.jointaro.com/questions/create/>

You can also go deeper with our related courses:

- [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- [\[Course\] System Design Masterclass: Shipping Real Features To Production](https://www.jointaro.com/course/frontend-system-design-masterclass-building-playlists/)
- [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)
- [\[Course\] Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)

How To Be An Effective Tech Lead [Part 5] - Think High-Level, Plan Long-Term

As a software engineer, it's way too easy to get lost in the weeds, fixating on details that ultimately don't matter. As a tech lead, you need to avoid rabbit holes like the plague. This lesson teaches you:

- The overall mindset tech leads must have when planning through and executing a project
- What it actually means to see the forest, not just the trees, with a detailed example from Jocelin's past
- How to own the overarching goal behind a project or workstream
- How to thoroughly think through dependencies

Do This To Get Maximum Value From Your Manager 1 on 1s

The manager 1 on 1 meeting is arguably the most sacred and high-leverage time you have in your career. Make sure you don't waste it by stumbling in with 0 preparation.

Here are the core points from the video:
- **Come in with a plan** - In your running meeting notes doc, write down the agenda beforehand with discussion points ordered by priority. Not only does this make your meeting more effective, it improves the perception of you from your manager's eyes as it shows that you're being more respectful of their time and you're more serious about your own growth and productivity.
- **Alert your manager of the plan 24+ hours beforehand** - This allows them to "pre-compute" the best responses to your meeting topics, so they don't get caught like a deer in the headlights with the trickier ones. It also makes it harder for your manager to cancel, especially when you have deeper, more important topics on the agenda.

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/)

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.