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

20 Years Of Fighting Procrastination [Part 10] - The Simple Playbook For Sleep

Sleep is often underestimated, yet it’s one of the most powerful levers for improving productivity, health, and mental clarity. Here are the core points from the lesson:

- Sleep has greater long-term health impact than alcohol or smoking, and chronic deprivation leads to worse mood, lower energy, and reduced cognitive function
- Treating yourself as “a good sleeper” and following a consistent wind-down routine (e.g. reading, brushing teeth early, reflecting on the next day) can drastically improve sleep quality
- Physical activity, especially group-based with accountability, helps regulate sleep and creates natural productivity deadlines
- Even small efforts like 10–15 minutes of movement or consistent pre-bed rituals can create compounding benefits for both rest and output

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

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>

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

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

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

What's Often Overrated When Choosing Your Next Job

Here are the attributes we've generally seen software engineers prioritize too much when weighing career opportunities:
- **Product space** - This usually manifests as pursuing a tech trend (like VR or NFTs). Of course, if you're legitimately passionate about the space, go for it, but seriously ask yourself if you would be in this space if it wasn't regularly talked about.
- **Technical space** - Similar to product space, you can follow trends here. Choose a stack that you're legitimately passionate about, which also has the support network you need (very important for junior engineers). The risk with cutting-edge technology is that it often doesn't have a lot of mature teaching resources behind it (it's cutting edge for a reason).
- **Level/title** - Promotion is a decent and concrete career goal earlier on, but don't go to bad companies to maximize your title. At the end of the day, your level and title are just strings next to your name.
- **Compensation** - Money is genuinely important in almost all cases, but what a lot of people don't realize is that very high pay often comes with a catch (usually work-life balance). Try treating this as a lagging indicator - If you're genuinely growing fast as a software engineer, you will eventually
land an opportunity that is top-of-market (as you deserve).

This clip was taken from the following masterclass: [[Masterclass] How To Choose A Good Company And Team As A Software Engineer](https://www.jointaro.com/lesson/0WEmTNZOMIh8xAdfO3JH/masterclass-how-to-choose-a-good-company-and-team-as-a-software-engineer/)

Related resources:
- ["How should I think about levels when it comes to evaluating jobs and in my career overall?"](https://www.jointaro.com/question/siBFn9WmU204N6D0IRHZ/how-should-i-think-about-levels-when-it-comes-to-evaluating-jobs-and-in-my-career-overall/)
- ["I feel like senior engineers tend to focus on a specific area. How can I pick a specialization that's still relevant in 5-10 years?"](https://www.jointaro.com/question/xFEhcvfbJ2P0pYzZ4r6f/i-feel-like-senior-engineers-tend-to-focus-on-a-specific-area-how-can-i-pick-a-specialization-thats-still-relevant-in-5-10-years/)

Meta Manager Case Study: The Ultimate Guide To Navigating A PIP

This was an Engineering Manager at Meta who has put 20+ employees on PIPs throughout their career.

- PIPs come from a mismatch of a “square peg, round hole”

- PIPs should never be a surprise. PIPs get discussed with the skip manager and HR

- Designed to be achievable with effort

- Across 20+ PIPs, has never had anyone continue employment

- **Advice**: “Clarity is more important than agreement”

DSA Crash Course [Part 27] - Sum List Walkthrough

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

Code along and test your work in the following editor workspace: <https://structy.net/problems/sum-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/>

Asking Great Questions [Part 5] - Figure It Out Or Get Help?

As a software engineer, you need to figure out a lot of things on your own (that's why you get paid the big bucks). However, you don't want to go the extreme where you endlessly run yourself into a wall by not getting help. This lesson teaches you:

- When to figure it out on your own vs. get help
- The dynamic behind solving complex engineering problems
- How to identify if you're stuck
- When to ask for help earlier instead of later

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.

Tech Lead Blueprint 2/17 - Course Structure

Connect with Lalit on LinkedIn: <https://www.linkedin.com/in/lalitkundu/>

Write A Stellar Resume As A Software Engineer [Part 8] - Intro Summaries

It's common practice for engineers (and almost everyone else) to include a paragraph at the very top of their resume summarizing their overall experience and explaining why they're great. This lesson teaches you:

- Why those intro summaries actually hurt you, especially in tech
- What to do instead of having an intro summary

[Become A Go-To Person 12/18] Lead Projects To Become An Expert

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

This Is Why FAANG Engineers Make So Much Money - Tech Compensation Breakdown

Learn about the 4 components of compensation:

1. Base salary
2. Sign-on bonus
3. Performance bonus
4. Equity

The latter two are less understood, and they are key to understanding why compensation at tier 1 tech companies is so high.

And we also talk about how Mark Zuckerberg actually had a pretty big impact on increasing tech compensation as a whole!

[The Insider's Guide To Negotiating Your Tech Salary And Compensation](https://www.jointaro.com/course/the-insiders-guide-to-negotiating-your-tech-salary-and-compensation/)

DSA Crash Course [Part 28] - Linked List Find Approach

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

> Write a function, *linked_list_find*, that takes in the head of a linked list and a target value. The function should return a boolean indicating whether or not the linked list contains the target.

```
a = Node("a")
b = Node("b")
c = Node("c")
d = Node("d")
a.next = b
b.next = c
c.next = d

# a -> b -> c -> d
linked_list_find(a, "c") # True
```

```
a = Node("a")
b = Node("b")
c = Node("c")
d = Node("d")
a.next = b
b.next = c
c.next = d

# a -> b -> c -> d
linked_list_find(a, "d") # True
```

```
a = Node("a")
b = Node("b")
c = Node("c")
d = Node("d")
a.next = b
b.next = c
c.next = d

# a -> b -> c -> d
linked_list_find(a, "q") # False
```

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

Why Big Tech Compensation Is So High - RSUs

This video explains how **Restricted Stock Units (RSUs)** work as a major part of tech compensation, especially in large tech companies. It outlines key timing mechanisms, industry trends, and the outsized impact RSUs can have on total earnings.

- **RSUs are company shares granted over time**, typically as part of a four-year compensation package. For example, an employee may be awarded 4,000 shares and receive 1,000 per year.
- **Most companies enforce a one-year cliff**, meaning no shares are received until completing the first full year. However, some companies like Google and Facebook have moved toward shorter cliffs, such as three months.
- **After the cliff, vesting usually occurs quarterly or monthly**, gradually releasing shares to the employee. This incentivizes ongoing retention.
- **Graphics help illustrate vesting schedules**, showing an initial cliff followed by incremental monthly or quarterly share distributions over the remaining years.
- **RSUs can far exceed base salary in total value**, especially at the senior level. In some cases, RSUs make up 75% or more of an individual's total compensation in big tech.

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.