DSA Crash Course [Part 41] - Breadth First Values Approach

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

> Write a function, *breadth_first_values*, that takes in the root of a binary tree. The function should return a list containing all values of the tree in breadth-first order.

```
a = Node('a')
b = Node('b')
c = Node('c')
d = Node('d')
e = Node('e')
f = Node('f')
a.left = b
a.right = c
b.left = d
b.right = e
c.right = f

#      a
#    /   \
#   b     c
#  / \     \
# d   e     f

breadth_first_values(a)
#    -> ['a', 'b', 'c', 'd', 'e', 'f']
```

```
a = Node('a')
b = Node('b')
c = Node('c')
d = Node('d')
e = Node('e')
f = Node('f')
g = Node('g')
h = Node('h')
a.left = b
a.right = c
b.left = d
b.right = e
c.right = f
e.left = g
f.right = h

#      a
#    /   \
#   b     c
#  / \     \
# d   e     f
#    /       \
#   g         h

breadth_first_values(a)
#   -> ['a', 'b', 'c', 'd', 'e', 'f', 'g', 'h']
```

```
a = Node('a')
#      a

breadth_first_values(a)
#    -> ['a']
```

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

Master The Behavioral Interview [Part 9] - The Interviewer Isn’t You

One of the biggest mistakes software engineers make during behavioral interviews is not having empathy. This lesson teaches you:

- A crucial way to understand the goal of a behavioral interview
- How a lack of empathy leads to immediate tactical failure in behavioral interviews
- How you can use empathy to take in a non-confusing way

A Huge Way Companies Reward You For Joining - Signing Bonus

This video explains the role of signing bonuses in tech compensation, particularly how they’re used by companies to stay competitive and how candidates should evaluate them carefully when reviewing offers.

- **Signing bonuses are one-time cash payments** intended to sweeten a job offer and help a company stand out among competing opportunities.
- **Unlike base salary and equity, signing bonuses are not banded**, meaning they can be more flexible and generous—sometimes reaching up to $175K–$200K for top-tier roles at big tech firms.
- **Because signing bonuses are tied to retention**, they’re typically prorated over time. If the full amount is paid upfront and the employee leaves early, a portion must usually be repaid.
- **Most signing bonuses are structured around a one-year commitment**, but some companies now split them over two years, spreading risk and encouraging longer retention.
- **It's important to read the fine print**, especially around repayment terms and payout schedules, since these details can affect real take-home compensation and decision-making.

Structuring Your Manager 1 on 1

If you are working in a strong, high-growth tech company, what is a good frequency to meet with your manager?

True or false: Managers are extremely busy, so it is best to have ad-hoc 1 on 1 meetings with them based on whenever they are able to find a sliver of free time.

Weekly one-on-ones with your manager are essential for staying aligned, especially in high-growth tech environments where priorities shift quickly.

- **Weekly cadence is ideal**: Aim to meet with your manager every week; bi-weekly is acceptable at most. Anything less frequent than that is considered a red flag for team communication and alignment.
- **30-minute standard**: A 30-minute weekly meeting strikes the right balance—long enough to discuss key topics, but short enough to stay focused and avoid bloat.
- **Avoid reactive scheduling**: Don’t wait until problems arise to schedule one-on-ones. Recurring meetings prevent misalignment and build a strong, consistent feedback loop.
- **Proactive relationship management**: Regular one-on-ones foster stronger relationships, clearer communication, and better support between you and your manager.

Grow From Mid-Level To Senior Engineer [Part 14] - Work Towards The Team Goal

Software engineers aren't paid to write code; they're paid to solve problems. However, this mindset often takes years for engineers to truly internalize, often at the senior level. This lesson teaches you:

- How mid-level engineers and senior engineers react different when given a project
- The questions every senior engineer needs to ask when given a project
- What needs to be done in order to understand the true impact of a project

Don’t Do THIS Kind of Code Review - Healthy vs Unhealthy Comment Example

In this segment, we explore a crucial cultural principle in code review: **“You are not your code.”** The way we give feedback deeply influences team trust, learning, and psychological safety. Our goal isn’t to be “right”—it’s to help each other grow and to build a healthy, collaborative engineering culture.

### Key Takeaways:

- **We critique code, not people**: Everyone—from interns to staff engineers—writes imperfect code. We give feedback without attacking the author, always assuming good intent and shared goals.
- **We use empathy-driven language**: Ending comments with a question mark (“Have you considered…?”) or using tentative language (“This might miss an edge case…”) keeps feedback constructive and opens the door to discussion, not defensiveness.
- **We avoid destructive comments**: Terse feedback like “Did you even test this?” not only fails to help—it can demoralize authors and harm team culture. Being “right” is meaningless if it alienates collaborators.
- **We model humility, especially as senior engineers**: Seniority should amplify empathy, not authority. Even if we're confident, we acknowledge the possibility we're wrong and focus on dialogue, not dominance.
- **We prioritize helpfulness over harshness**: Great reviewers point to specific issues, offer reasoning, and invite collaboration. They focus on moving the work forward—not “winning” a debate.

By reviewing with empathy, humility, and clarity, we turn every code review into an opportunity to strengthen our team and elevate everyone’s craft.

Write A Stellar Resume As A Software Engineer [Part 7] - It's Too Long

Having a resume that's too long is one of the easiest ways software engineers get their resume (and their job candidacy) immediately thrown out. This lesson teaches you:

- The optimal length for a resume
- Why shorter is better when it comes to resumes (and why very long resumes make 0 sense)
- How to convert your years of experience to a resume length
- Tactics to trim down your resume and make it more concise

Master The DSA Interview [Part 22] - The #1 Tool For DSA Prep

As a mainstay of the software engineering industry for 15+ years, data structures and algorithms have more than their fair share of online resources to help you learn it. This lesson teaches you:

- The #1, time-tested resource to learn data structures and algorithms
- The trap many engineers fall into when learning data structures and algorithms when it comes to tool selection
- How to organically expand LeetCode into the rest of your learning tree
- What to do when you get a FAANG interview

If you're interested in NeetCode, you get a discount on it with your Taro Premium membership. Redeem it here by using code TARO at checkout: <https://neetcode.io/pro?utm_source=taro>

Common Scenarios For Setting Up 1 on 1s

What is the main condition to look out for that could prompt you to set up new 1 on 1 meetings?

Which of the following scenarios is something you probably should set up some new 1 on 1 meetings for?

1 on 1s are meetings for the 2 people involved to connect and build a longer-term relationship. Here are 3 common scenarios where it makes a ton of sense to set up a 1 on 1:

1. **Incoming new hires**: Help the new person on the team feel welcome and get them onboarded
2. **You being the new hire**: When you're new, 1:1s help you build up valuable context and relationships from talking to existing teammates. Use your "new"-ness to setup meetings with anyone who might be relevant to your job [as described here](https://www.jointaro.com/lesson/xwldhYelyOFLjogs7RVA/onboarding-gives-you-special-powers-make-sure-to-use-them/)
3. **Working with a new team**: If you have a long-term relationship with a partner from another team, it could be worthwhile to setup a recurring one on one with them

Amazon Behavioral Interview [Part 2] - Tell Me About Yourself (Answer)

This video provides a glimpse into the speaker's diverse career journey.

- **Career Trajectory:** The speaker has a varied background, spanning finance, baseball analytics, marketing at American Express, and roles at tech giants like Google, Facebook, and Salesforce.
- **Focus on Customer:** The speaker emphasizes their consistent focus on the customer throughout their career, influenced by their time at customer-centric companies like Amazon and American Express.
- **Entrepreneurial Ventures:** The speaker founded Kadima, a business focused on helping underrepresented talent break into top tech companies, highlighting their passion for supporting others.
- **Return to Tech:** After exploring entrepreneurship, the speaker is seeking a return to the tech industry, driven by the need for greater stability and financial security for their family.
- **Amazon Opportunity:** The speaker expresses excitement about a potential opportunity at Amazon, recognizing the company's customer-centric approach and rigorous standards, aligning with their own values and career goals.

Learn more about Alan's job search program, Kadima Careers, using this [discount link](https://signup.kadimacareers.com/mQBsDvu).

Master The Behavioral Interview [Part 18] - How To Get The Level You Want

If you don't play your cards right, it is easy to get down-leveled, which means getting a level lower than what you were at before. This is very common in bad markets and for engineers breaking into FAANG. It's also common if you don't give an amazing behavioral interview performance. This lesson teaches you:

- The overall strategy to not get down-leveled
- Tips you should follow to maximize your level

To better understand the expectations at each level, go through this: [\[Taro Top 10\] Understanding Engineering Levels](https://www.jointaro.com/playlist/e9rjATPbSyvRPsukXiHn/)

For resources on becoming a better engineer:

- [\[Course\] Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)
- ["What are software engineering fundamentals?"](https://www.jointaro.com/question/3VNPK7wol76s89EkgFeW/what-are-software-engineering-fundamentals/)

Master The DSA Interview [Part 15] - Edge Cases

Too many engineers only care about the happy flow, but it is the easy thing to do. This lesson teaches you:

- Why handling edge cases is so important as an engineer, especially at FAANG
- The mindset you need to have to tease out edge cases systematically
- Common edge case scenarios for data structures and algorithms problems
- What a great edge case analysis looks like, explained with an in-depth example

Take the code quality course here: [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 Crack System Design Interviews - Part 10: Preparation Resources

This video outlines resources and strategies to prepare for system design interviews. We can improve our performance by:

- **Building a strong vocabulary:** Familiarizing ourselves with key technologies and concepts (e.g., Amazon S3, Apache Kafka) helps us communicate ideas effectively and demonstrate practical understanding.

- **Developing theoretical knowledge:** We can gain a solid theoretical foundation through courses like Interview Ready, which covers high-level and low-level design concepts, design trade-offs, and other essential topics.

- **Gaining practical experience:** Mock interviews provide invaluable practice and build confidence for the real interview. Consider using free platforms or seeking discounts if available.

- **Utilizing online assessment tools:** If time is limited, leverage automated online judges to assess and reinforce understanding of system design components and their placement.

- **Prioritizing human interaction:** While online tools are helpful, prioritize mock interviews with experienced individuals for the most effective preparation and feedback.

A few tools mentioned: 

- Mock Interviews: [joinTaro.com/perks](https://www.jointaro.com/perks/)
- [Automated Design Judge](https://interviewready.io/question-list/system-design-judge/?_aff=JOINTARO)
- [General Resources for SD](https://interviewready.io/resources)

[Gaurav Sen](https://www.linkedin.com/in/gkcs/) has conducted 1000s of system design interviews while working at Uber and building his [YouTube channel](https://www.youtube.com/@gkcs) to 500K+ subscribers. His platform [InterviewReady](https://interviewready.io/?_aff=JOINTARO) combines video explainers, live Zoom classes, and an automated System Design Judge.

Taking Amazing Meeting Notes

For any meeting, what should you make sure for it?

True or false: As long as you write down most of what was said in a meeting, you have taken a good set of meeting notes.

What can you do when someone else in a meeting says something really insightful?

Your meeting is winding down, and you have a good set of notes of what was said during the meeting. What should you do next?

Meetings can easily become unproductive unless there is a clear sense of ownership and structure. This segment emphasizes taking initiative and being proactive with note-taking and follow-up.

- **Take initiative to capture takeaways**: Especially when meeting with a manager, take responsibility for writing down notes and summarizing key points. Don’t assume they’ll do it—they likely have too much on their plate.
- **Communicate your intent**: Let the other person know that you’re taking notes because their input is valuable. This builds mutual respect and sets the tone for accountability.
- **Clarify ownership of action items**: Don’t leave to-dos ambiguous. Specify who will do what—whether it’s you, your manager, or another teammate.
- **Create space for note-taking**: Pause briefly during the conversation when something important is said. Say things like “Let me write that down” to signal that you’re capturing key information.
- **Follow up consistently**: Revisit the notes in future meetings and check progress. This keeps everyone aligned and ensures that good ideas don’t get lost.
- **Adapt for walking meetings**: For more casual one-on-ones (like walking meetings), carve out 10 minutes afterward to document and share what was discussed. This keeps the informal meeting just as productive as a formal one.

Level Up Your Code Quality As A Software Engineer [Part 22] - Too Many Comments

Comments is a coding technique everyone learns particularly early, which makes sense as newbies need the extra hand-holding. However, there's a weird phenomenon where code comments go from a good thing to a bad thing very rapidly in your career. This lesson will teach you:

- Why comments are so prolific across code
- How comments end up hurting rather than helping, especially at scale and with large codebases
- What you should do instead of adding a bunch of code comments
- The fundamental mentality around writing good, clean, readable code, which Alex breaks down with a concrete refactoring example

DSA Crash Course [Part 33] - Reverse List Walkthrough

In this lesson, Alvin walks through the python implementation for the *reverse_list* problem.

Code along and test your work in the following editor workspace: <https://structy.net/problems/reverse-list?language=py>

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

Clear Communication For SWEs [Part 2] - What Is Clear Communication?

In this video, I delve into the essence of clear communication in software engineering, emphasizing its critical role in project success. I discuss the definition of clear communication, common barriers, and strategies to overcome them. Effective communication ensures team alignment, enhances productivity, and reduces errors. Viewers are encouraged to adapt their communication style for diverse audiences and regularly summarize key points for clarity.

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

Grow From Senior To Staff Engineer [Part 6] - You Need Tenure

Software engineers like to give up when their team isn't going perfectly, often interviewing with another company entirely to jump ship. While this can work earlier in your career, it almost always stops as you're approaching staff. This lesson teaches you:

- Why job hopping to a staff uplevel at a top company is almost impossible
- Why you need to be in the same team for 2+ years in order to have a real case for staff
- The ingredients to develop the presence and impact of a staff engineer

Master The Behavioral Interview [Part 14] - Junior Engineer

Every software engineer starts off as a junior engineer. Junior engineers can't really do anything, but they still need to do pass interviews. This lesson teaches you:

- The expectations from a junior engineer overall and how that reflects in behavioral interviews
- The kinds of stories junior engineers tell in behavioral interviews

Managing ADHD as an Engineer

Attention-deficit/hyperactivity disorder (ADHD) is marked by an ongoing pattern of inattention and/or hyperactivity-impulsivity that interferes with functioning or development.

Handling ADHD as an engineer is hard. Juggling job demands, with everyday ADHD struggles, can feel overwhelming. But, you're not alone.

This collaboration between Shimmer and Taro explores the intersection of ADHD and Engineering. You'll see a live conversation between a Shimmer ADHD coach and their engineer client. Alex (coach) and Ashley (student) share how ADHD shows up in the engineering field, along with science-backed strategies to overcome common challenges. 

Some of the common presentations of ADHD: 
- Emotional regulation
- Procrastination
- Establishing routines

Ways to find and keep motivation: 
- Find your drive
- Break it down
- Create accountability
- Utilize external motivation

Energy and time management: 
- Know when your energy fluctuates
- Determine the level of cognitive effort for a task
- Use the minimum amount of cognitive effort necessary

Understand the front-end and back-end of procrastination: 
- **Front-end**: conditions must be perfect to get started, lack of direction/motivation, underestimating time needed
- **Back-end**: perfectionism, loss of novelty, fear of feedback, waiting for the final push

Get Shimmer through Taro Perks for a discount: [joinTaro.com/perks](https://www.jointaro.com/perks/)

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.