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

Nail Your Promotion As A Software Engineer [Part 14] - Observe Other Engineers

Don't know what you need to do as a software engineer to get promoted? Observe engineers who are better than you! However, this is a surprisingly difficult skill to develop. This lesson teaches you:

- Which engineers you should observe and how to find them
- What you should be looking for when observing other engineers
- What "silent hero" work is and how very senior engineers do a lot of it
- The concrete avenues you should look at when trying to figure out why a higher-level engineer is superior to you
- Why getting jealous of engineers above you is a colossal waste of time, even if you are truly better than them

Nail Your Promotion As A Software Engineer [Part 12] - Talk To Your Manager

In order to get promoted, you almost certainly need your engineering manager on your side. However, this is much said than done, and many engineers mess this up. This lesson teaches you:

- The importance of being deliberate about promotion
- Why your engineering manager is so important to your promotion case
- The fundamental principal to remember when it comes to asking for promotion
- What to do and what *not* to do when having that promotion conversation with your manager
- How to react gracefully and effectively if your manager doesn't believe you are ready to start really thinking about promotion

15 SWE Years In 1.5 Hours [Part 5] - Succeeding In School

Most software engineers start off their journey in tech by getting a university degree. However, most students don't leverage their time in school optimally. This lesson teaches you:

- The most valuable asset you get from school (hint: it's not good grades)
- Why school isn't very effective at teaching you how to do software engineering in the real world
- What you should do instead to enhance your technical skills instead of purely focusing on getting good grades

Nail Your Promotion As A Software Engineer [Part 8] - Avoid Level Overload

Not all teams are created equal when it comes to promotion opportunity, far from it in fact. Don't sleep on this crucial angle when it comes to planning out your promotion plan as a software engineer. This lesson teaches you:

- The 2 types of level overload to avoid and which one is worse
- How to a team that has a healthy mix of levels vs. one that doesn't
- Why level overload is bad, particularly when there's a lot of engineers at the same level you are

Why Great Engineering Managers Are Like Captain America

There is far more to software engineering than shipping code. A truly effective engineering manager needs to step up with these issues to protect the team.

Here are the core points from the video:
- **A good engineering manager is a shield** - In particular, engineering managers should handle non-technical issues like politics and organizational thrash, abstracting that pain away from their engineers so they have the clarity to execute.
- **Alex's Manager Shielding Story** - When Alex joined his team at Robinhood, the product roadmap wasn't very clear. There definitely wasn't enough well scoped out work for the team to work on. To shield the team from this product direction thrash, he created a high-impact infrastructure project for the team to work on, giving them the scope necessary to not get destroyed in performance review from doing nothing.

If you're interested in how Alex led that Robinhood infrastructure project despite being new to the company, watch his case study about it here: [[Case Study] Becoming A Tech Lead Again In Just 1 Month After Joining Robinhood From Meta](https://www.jointaro.com/lesson/X8vpfJooDpsX915ouC00/case-study-becoming-a-tech-lead-again-in-just-1-month-after-joining-robinhood-from-meta/)

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/) - The full video this clip was taken from
- [How Do Effective Engineering Leaders Help Their Teams Achieve More?](https://www.jointaro.com/lesson/xGJDCG7VL4hcZaq5XL92/how-do-effective-engineering-leaders-help-their-teams-achieve-more/)
- ["How possible is it to spot red flags about toxic culture during the interview?"](https://www.jointaro.com/question/1JwmhC3Nh9Ku0fkDL1bq/how-possible-is-it-to-spot-red-flags-about-toxic-culture-during-the-interview/)

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

Get The Rating You Deserve [Part 15] - Use Synchronous Time Wisely

**In this section, we explored strategies for optimizing our synchronous time and effectively communicating our work and desires.**

To make the most of our time and build strong professional relationships, we should:

- **Prioritize synchronous time:** Focus on activities that require real-time collaboration and cannot be effectively accomplished asynchronously.
- **Minimize unnecessary meetings:** Reduce the number of meetings and their duration to maximize productivity.
- **Communicate proactively:** Share updates and seek feedback regularly, both synchronously and asynchronously.
- **Build strong relationships:** Cultivate positive relationships with colleagues and managers through open and honest communication.
- **Be mindful of our communication style:** Adapt our communication style to different audiences and situations to ensure effective message delivery.

By implementing these strategies, we can improve our efficiency, effectiveness, and overall job satisfaction.

If you want to get personalized support from Yogi, you can reach out to him at [coaching@yogisharma.com](mailto:coaching@yogisharma.com) or schedule an introductory call to dive into your situation at <https://tinyurl.com/meetyogi>.

Become An Open Source Master [Part 8] - Find Companies Active In Open Source

The video discusses where to find open source projects to contribute to.

- The GitHub Octaverse Report and websites like <https://gitstar-ranking.com/> provide lists and rankings of companies and projects active in open source.
- Many large tech companies, like Microsoft and Google, have active open source ecosystems.
- The GitHub trending pages can help you discover new and interesting projects that are gaining popularity.
- Don't limit yourself to one type of project or technology; contributing to a variety of projects will broaden your skills and experience.

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

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

Clear Communication For SWEs [Part 3] - Core Elements Of Communication

In this video, I delve into the core elements of effective communication - empathy, purpose, and responsibility. Understanding and mastering these elements are crucial for successful team interactions and project outcomes. I emphasize the importance of tailoring messages to the audience, defining clear purposes, and ensuring mutual understanding. Viewers are encouraged to adopt a mindset shift towards intentional and thoughtful communication.

Connect with me on LinkedIn: <https://www.linkedin.com/in/ryan-wiens/>

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

Make Your Promotion Case Easy - Keep A Brag Journal

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

Nail Your Promotion As A Software Engineer [Part 23] - Sell Yourself, Claim Your Wins

So many software engineers don't realize that perception and reality are 2 very different things that often drift apart. The painful truth is that perception is far more important than reality. This lesson teaches you:

- How software engineers can do amazing work but their teammates actually think they're mediocre
- Why you need to put in the work to get full credit for your work, especially for promotion
- Why you shouldn't only wait for huge launches to communicate progress
- Which mediums to use when it comes to sharing progress updates
- The many benefits of high-quality project updates

For more concrete tactics on writing a top-notch project update, check this out: ["How to get more visibility on work?"](https://www.jointaro.com/question/XA0X51AypDLCeVeleJv4/how-to-get-more-visibility-on-work/)

Growth And Promotion 4/6: Beyond The Basics

Topics covered:

- 🔄 Stop asking and start suggesting solutions to help move toward your goals.
- 💼 Offer to take on tasks that align with your desired career path, such as stepping into product management roles.
- 🤝 Build trust by offering solutions rather than waiting for your boss to assign tasks.
- 🚀 As you grow in your role, learn to anticipate problems and solve them without needing direct permission.
- ✨ Becoming proactive and solving issues without being asked makes you valuable and trusted by your manager.
- ❌ Avoid bad habits like nagging for promotions or stepping on others to advance your career.
- ⚖️ Balance ambition with responsibility—don’t rush through promotions or switch roles too quickly. 🏃‍♂️ Chasing hot trends without focus can hinder your long-term career growth.
- 💡 Don’t compare yourself to others—focus on your own performance and growth.
- 📋 Be mindful of bad managers who may exploit you, but understand their motivations and manage relationships carefully.

Starting at Amazon as a Senior Manager, then Director, then Vice President, Ethan has decades of experience at top tech companies. This career growth course is developed from his own knowledge and input from his extensive network of fellow coaches and executives.

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

This Is Why You Should NOT Work For Big Tech

Working at FAANG is great for many reasons, but the Big Tech life isn't for everybody. For many engineers, it doesn't really make complete sense to go there.

Here are the core scenarios where Big Tech might not be the best for you:
- **You have strong WLB needs** - Work-life balance generally becomes more important as you get older, and Big Tech is generally pretty bad at giving you that.
- **You don't like stress** - There's nothing wrong with wanting to chill and avoiding pressure. However, Big Tech is usually not a good place to do this.
- **You want to hyper-maximize your career growth** - Big Tech is often a consistent path that takes your career to a very good place. However, if you want to go to an astounding place (e.g. become a VP of Engineering by the time you're 30), startups are far superior. Startups have much higher risk but also much higher rewards.
- **You just want to code** - Engineers at Big Tech almost always need to become incredibly well-rounded, especially at senior and staff. If you don't want to play politics and spend mountains of time running meetings and writing planning docs, Big Tech is likely not the place for you.

Related resources:
- ["How to have FAANG level of career growth in startup?"](https://www.jointaro.com/question/VQgUHZPwbzqxjutaDU3W/how-to-have-faang-level-of-career-growth-in-startup/)
- ["When does it make sense to leave big tech?"](https://www.jointaro.com/question/v6GBLlfXb1ugNobkEm7w/when-does-it-make-sense-to-leave-big-tech/)

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

Nail Your Promotion As A Software Engineer [Part 16] - Impact

Impact is a word that's constantly tossed around the software engineer community, especially at Meta. But what exactly does it mean? This lesson teaches you:

- The definition of impact and how it varies between bigger and smaller tech companies
- The 2 core industry terms you should know when it comes to impact
- How junior and mid-level engineers are rewarded when it comes to project impact (spoiler: they usually aren't)

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)

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.