Engineer Your Ideal Tech Career [Part 6] - What's Your Ideal Role Type?

In this video, we begin by debunking common career misconceptions that often plague individuals progressing through their career. We then cover the major role types you can aim for as a software engineer. These are only three options, and there are more nuanced ones to explore.

Specifically, we cover becoming a:

- High-Level Independent Contributor (IC)
- Tech Lead
- Engineering Manager

We'll also cover what it looks like to be at the pinnacle of your career in each of those roles.

Looking for mentorship from tech’s top engineers + personalized job hunt assistance and interview prep? [Formation.dev](http://Formation.dev) can provide you unlimited career coaching, technical mentorship, personalized practice, and mock interviews. Join us here: <https://formation.dev/partners/taro>

Worksheet: [Formation - Coding Your Career](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/courses%2Fslides%2FFormation%20Career%20Direction%20Worksheet.pdf?alt=media&token=f6344b78-529a-411e-a449-7a34a8d55fc8)

Master The Behavioral Interview [Part 20] - Write Stuff Down

Writing English is far more important than writing code, and this applies to mastering the behavioral interview as a software engineer as well. This lesson teaches you:

- How to create a powerful Q&A database to master the behavioral interview
- What you should be remembering from your written preparation vs. not

Write A Stellar Resume As A Software Engineer [Part 12] - Esoteric Terms

As a software engineer, it is absolutely critical for you to write a resume that is incredibly easy to understand, particularly for the recruiter (who, as a reminder, is a non-technical person). Unfortunately, it's very easy for engineers to get this wrong. This lesson teaches you:

- Why engineers often unintentionally make their resumes near impossible to understand
- What esoteric terms are and the categories they fall into
- How to get rid of esoteric terms from your resume with an in-depth example

Senior Staff Engineer (L7) Describes Most Important Skill - Kaushik Gopal

[Kaushik](https://www.linkedin.com/in/gopalkaushik/) is a Senior Staff Engineer at Instacart.

- **Most important skill**: identify, deliver, and measure the impact. At the Senior Staff level, it's not enough to execute on a technical vision, you also need to spend time identifying and measuring impact.
- **Advice**: talk to stakeholders across the company to identify problems and areas of impact. This includes non-eng functions like PM, design, customer support.

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:

- [SWE2 --&gt; Principal Eng in 4 years](https://www.jointaro.com/lesson/Lvf1TDKt1R4ZJSCr9BVv/rockstar-software-engineer-story-sw2-greater-principal-in-just-4-years/)
- Taro's top 10 to get promoted from [senior to staff engineer](https://www.jointaro.com/playlist/YD8LMCSlE71VUGUbNAWM/)
- [David Pan on what makes a great tech lead](https://www.jointaro.com/lesson/uHqZZ15SK19MatEvLSO6/what-makes-a-truly-great-tech-lead-a-vp-of-engineerings-perspective/)
- [Kaushik on LinkedIn](https://www.linkedin.com/in/gopalkaushik/)

Break Into Tech And Become A Software Engineer [Part 5] - Know Your Fundamentals & Frameworks

In this lesson, Brian highlights the balance between knowing your technical fundamentals and understanding modern frameworks to build effective software applications.

This lesson covers:

- The importance of having both foundational knowledge and framework expertise to speak the same technical language as co-workers, especially those with computer science degrees
- How understanding design patterns, software development lifecycles, and common best practices prevents you from reinventing the wheel and helps you navigate technical discussions
- Key resources like *Clean Code*, *You Don’t Know JavaScript*, and *The Phoenix Project* that deepen your knowledge of coding fundamentals and software development processes

If you need extra help breaking into tech, join Brian's exclusive, cohort-based bootcamp (just 10 students per batch). Use this special link for $800 off: <https://www.parsity.io/taro>

Connect with Brian on LinkedIn: <https://www.linkedin.com/in/brianjenney/>

DSA Crash Course [Part 43] - Tree Sum Approach

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

> Write a function, *tree_sum*, that takes in the root of a binary tree that contains number values. The function should return the total sum of all values in the tree.

```
a = Node(3)
b = Node(11)
c = Node(4)
d = Node(4)
e = Node(-2)
f = Node(1)
a.left = b
a.right = c
b.left = d
b.right = e
c.right = f

#       3
#    /    \
#   11     4
#  / \      \
# 4   -2     1

tree_sum(a) # -> 21
```

```
a = Node(1)
b = Node(6)
c = Node(0)
d = Node(3)
e = Node(-6)
f = Node(2)
g = Node(2)
h = Node(2)
a.left = b
a.right = c
b.left = d
b.right = e
c.right = f
e.left = g
f.right = h

#      1
#    /   \
#   6     0
#  / \     \
# 3   -6    2
#    /       \
#   2         2

tree_sum(a) # -> 10
```

```
tree_sum(None) # -> 0
```

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

Grow From Senior To Staff Engineer [Part 18] - Product Hybrid

As a software engineer, you generally want to evolve past the code. There is 1 group of staff engineers who take that to the extreme. This lesson teaches you:

- What the product hybrid staff engineer archetype is
- The exact expectations of a product hybrid staff engineer
- How software engineers are uniquely positioned to hybridize as product managers
- Why most tech companies don't support the product hybrid archetype
- How to become a product hybrid staff engineer

Learn to sharpen your product sense with these resources: [\[Taro Top 10\] Product Management For Engineers](https://www.jointaro.com/playlist/66TyB60SRRmdnm0jmf55/)

Grow From Mid-Level To Senior Engineer [Part 18] - Build A Strong Internal Network

If you have a meaningful bench of people who are willing to fight for your success, you will succeed as a software engineer. One of the simplest ways to understand seniority is that this bench grows larger and larger over time. This lesson teaches you:

- How an engineer's internal network at a company evolves as they grow from mid-level to senior, both in terms of breadth and depth
- How to expand your internal network
- The difference in peer feedback that mid-level engineers get compared to senior engineers, especially with XFN (cross-functional) partners

To dive deeper into earning trust quickly and building relationships: [\[Masterclass\] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

Master The DSA Interview [Part 29] - LeetCode Stockholm Syndrome

Even after passing the data structures and algorithms interview, a surprising amount of engineers maintain a toxic relationship with it. This lesson teaches you:

- What LeetCode Stockholm Syndrome looks like
- Why it doesn't make sense to continue studying data structures and algorithms after you have started the job
- The key towards true growth as a software engineer (hint: it's not LeetCode)
- A super simple way to understand data structures and algorithms studying and how it fits into your life

What Does A High Trust Team Mean For Code Review?

In this closing section, we focus on the importance of **building and operating within a high-trust engineering team**. Trust is not just a feel-good concept—it directly affects our productivity and velocity when shipping code.

- **We prioritize speed and trust in code review.** When we trust our teammates, we don’t block diffs unnecessarily. Instead, we approve with minor suggestions, knowing the author will follow through responsibly.
- **We use “accept with nits” to keep things moving.** For small, straightforward changes—like renaming variables—we leave a “nit” comment but still approve the diff to avoid introducing unnecessary delay.
- **We avoid slowing each other down over trivial issues.** Each extra cycle of “request changes” can delay code by 1–2 days. We conserve team momentum by trusting competent authors to resolve minor feedback themselves.
- **We treat time as our most precious resource.** Code review should add value without becoming a bottleneck. High-trust practices help us operate with both quality and speed.
- **We maintain expectations through communication.** Even when approving with nits, we clarify, *“Please address before landing,”* so everyone stays aligned on expectations without blocking forward motion.

PIP Stereotypes - The Ultimate Guide To Navigating A PIP

Given the secrecy and consequences of PIPs, you've probably a bunch of stereotypes about PIPs. This is a non-exhaustive list of beliefs that are simply not true:

- *"You must be incompetent or lazy"*
- *"Your manager or company must be horrible"*
- *"It’s impossible to keep your job on a PIP"*
- *"You'll no longer be employable"*

This thinking is reductive and will lead to more harm than good. A better way to think about a PIP is not to cast blame on one party or another. Instead, a PIP means **there was a mismatch in expectation between employee and employer**. 

The reality is that there are many potential reasons why you may receive a PIP, ranging from lack of support, poor management, lack of motivation, shifting company needs, etc.

Throughout the PIP process, one of the most difficult parts is that you’ll feel zero (or negative) support from key people around you. In order to find success at your job, and more broadly in your career, **you need to be an advocate for yourself**. Have the confidence that you are valuable. Too many engineers are their own worst critic, which exacerbates the negative spiral of performance.

[Timeless Career Advice] IC vs Manager

This video discusses how much the software industry pays in the US in terms of total compensation. 

In addition, we discuss the decision to be an individual contributor vs engineering manager.

Connect with Louie:

- SmallBets community: [**https://smallbets.com/?utm_source=taro**](https://smallbets.com/?utm_source=taro)
- Twitter: [**https://twitter.com/LBacaj**](https://twitter.com/LBacaj)
- LinkedIn: [**https://www.linkedin.com/in/louiebacaj/**](https://www.linkedin.com/in/louiebacaj/)
- Newsletter: [**https://newsletter.memesmotivations.com/**](https://newsletter.memesmotivations.com/)

Engineer Your Ideal Tech Career [Part 5] - Gathering Requirements And Preferences

As an introduction to this next section, you can expect to start defining what your long-term career and path may look like based on your preferences you defined in the last section.

For each dimension, pick one option only to make your goals as clear as possible. If one dimension doesn’t resonate with you, that’s okay! Skip it vs. making arbitrary goals.

The dimensions we’ll cover are:

- Role types
- Specializations
- Company stage
- Becoming a founder

Looking for mentorship from tech’s top engineers + personalized job hunt assistance and interview prep? [Formation.dev](http://Formation.dev) can provide you unlimited career coaching, technical mentorship, personalized practice, and mock interviews. Join us here: <https://formation.dev/partners/taro>

Worksheet: [Formation - Coding Your Career](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/courses%2Fslides%2FFormation%20Career%20Direction%20Worksheet.pdf?alt=media&token=f6344b78-529a-411e-a449-7a34a8d55fc8)

Asking Great Questions [Part 7] - Diversify Your Asks

It is tempting to stick with what you know. When it comes to asking questions, this means asking the same person again and again after they have helped you before. However, this isn't the way to go when it comes to your growth. This lesson teaches you:

- How repeatedly getting help from just 1 person can strain your relationship with them
- The tech industry-specific danger of only having 1 person to answer your questions
- The tactical survival benefit of diversifying the pool of people you ask questions to
- How getting help from a lot of people builds up a huge career asset with long-term social capital, which is crucial for more senior engineers

Nail Your Promotion As A Software Engineer [Part 25] - Timing: When To Amp Things Up?

Humans have terrible memory, and software engineers (+ engineering managers) are no exception. The annoying thing is that this greatly affects how you're judged in performance review. This lesson teaches you:

- The role recency bias plays in your promotion case
- How to spend your energy over time across the performance review cycle

How To Be An Effective Tech Lead [Part 6] - Be The Code Guardian

As a tech lead, you are ultimately responsible for all the code that is delivered. The tricky part is that you need to do this without simply writing all of it. This lesson teaches you:

- The role tech leads play when it comes to cleaning up the code and paying down tech debt
- A high-level, multiplicative lever tech leads should pull to enforce code quality
- The in-the-weeds tactic tech leads need to constantly use to keep code quality high

To get better at code reviews, particularly those outside of your immediate domain, read through this: ["How to give better code reviews without full business context?"](https://www.jointaro.com/question/vio35mw1SYWM8AYojB2w/how-to-give-better-code-reviews-without-full-business-context/)

Master The Behavioral Interview [Part 24] - Challenge Yourself, Do Great Work

Behavioral interviews are fundamentally an exercise in storytelling. This means that in order to pass these interviews as a software engineer, you need great stories to begin with. This lesson teaches you:

- The 2-step process to become absolutely incredible at behavioral interviews
- The most common mistake software engineers make with their mentality when it comes to growth
- How to get better at coding, even if you're unemployed

For more resources on becoming a better software engineer:

- [\[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\] Build Side Projects With 500k+ Users: Coming Up With An Idea](https://www.jointaro.com/course/build-side-projects-with-500k-users-coming-up-with-an-idea/)
- [\[Taro Top 10\] How To Create Scope As An Engineer](https://www.jointaro.com/playlist/EWIo3USNcsgXbCs5PS0h/)
- ["What are the Core skills a SDE should be consistently developing?"](https://www.jointaro.com/question/Hs8VJtUb6bfTPjUgbj96/what-are-the-core-skills-a-sde-should-be-consistently-developing/)

Ace Your Tech Interview As A Software Engineer [Part 19] - Take Home Assignments

Take home assignments are one of the most brutal screening mechanisms tech companies use to filter out software engineer job candidates. This lesson teaches you:

- Why take homes are horrible
- How to skip take homes as much as you can
- A framework you can use to figure out whether or not you should do a take home

If you have no other option but to do a take-home, follow these resources:

- ["How do I make software less overwhelming?"](https://www.jointaro.com/question/YseMPDw538jhyS1MWlTs/how-do-i-make-software-less-overwhelming/)
- ["How Long to Complete Take-Home Assignment II"](https://www.jointaro.com/question/7PfT1CWSY0Dd1jiLYTou/how-long-to-complete-take-home-assignment-ii/)
- [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

Understanding How To Empower Your Manager To Get The Rating You Want

- Come calibration time (i.e. when managers and very senior engineers come together to calculate your manager), your manager is going to have to defend you to get the rating they're proposing for you.
- This is another reason why it's so important to have a clear expectations plan. By setting the baseline, your manager has a concrete anchoring point to argue your case, in particular when you have gone above and beyond the baseline.

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.