Amazon Behavioral Interview [Part 7] - Overcoming An Unanticipated Obstacle (Answer)

This video segment focuses on an interviewee's experience overcoming a significant obstacle in achieving a key goal.

- **The Obstacle:** The interviewee encountered an issue with their company's customer satisfaction (CSAT) measurement system. They discovered that the current process, where Escalation Account Managers (EAMs) were responsible for sending out CSAT surveys, introduced significant bias. Some EAMs were selectively sending out surveys only to customers they expected to give high scores, artificially inflating the overall CSAT score.
- **Overcoming Challenges:**
  - **Resistance to Change:** The interviewee faced resistance from some EAMs who were hesitant to relinquish control of the survey process.
  - **Technical Limitations:** Implementing an automated survey system presented significant technical challenges, requiring collaboration with the tooling and automation team.
- **Impact and Mitigation:** The initial implementation of a more accurate CSAT measurement system resulted in a temporary dip in the overall score. However, the interviewee proactively communicated this potential drop to leadership and addressed concerns.
- **Long-Term Results:** Over time, as the team addressed underlying issues and improved customer service, the CSAT score gradually increased, eventually exceeding the previous level.

This example demonstrates the interviewee's ability to identify and address a critical issue, overcome resistance to change, and ultimately achieve a positive outcome despite encountering significant obstacles.

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

SWE Internship Survival Guide [Part 5] - Act With Urgency

Top interns succeed by treating every week as high-leverage and avoiding the common traps that waste time. Here are the core points from this lesson:

- Adopt a mindset of urgency—internships are short, so prioritize work that drives progress on your main project and skip distractions like excessive social events or irrelevant tasks
- Use a structured timeline: ramp up quickly in the first 3 weeks, execute intensely for 6, and aim to wrap and demo your project by week 10
- Aggressively seek help when blocked and bias toward action—don’t wait for replies when a quick conversation can resolve things faster
- Avoid rabbit holes into infrastructure or tooling curiosity; stay focused on work that directly impacts your deliverables and evaluation

DSA Crash Course [Part 82] - Summing Squares Walkthrough

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

Code along and test your work in the following editor workspace: <https://structy.net/problems/summing-squares?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/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

Become An Engineer Influencer [Part 2] - Michael's Backstory

Michael saw the transformative power of influence after he left his job at Netflix. This video reveals the new opportunities enabled by cultivating an audience. Michael talks about which platforms he grew on, among Medium, LinkedIn, Twitter, a newsletter, and more.

Connect with Michael:

- LinkedIn: <https://www.linkedin.com/in/michael-lin-tech/>
- Twitter: [https://x.com/\_michaellin](https://x.com/%5C_michaellin)
- Newsletter: <https://www.michaellinwrites.com/>

Asking Great Questions [Part 19] - Give Them An Out

Most engineering favors don't get fulfilled. If you're cognizant of that and incorporate it into your question, you can counterintuitively *increase* your chances of getting the favor. This lesson teaches you:

- Why making it easy for your favor to be turned down increases your standing with the person you're asking for a favor from
- What it means to give the helper an out with your question, explained with an in-depth example

Come Up With 500k+ User Project Ideas [Part 17] - Just Keep Building

Failure is a part of life and software side projects are no exception. This lesson teaches you:

- The builder mindset you absolutely must have to succeed with side projects
- Why a failed side project really isn't that bad, especially if you're following the advice from this course
- How Alex made several stupid side projects destined for failure so you don't make the same mistakes he did

Asking Great Questions [Part 24] - Give More Than You Take

The counterpart to asking a question is answering a question, but it's not exactly right to call them opposites as they actually go hand-in-hand! This lesson teaches you:

- How engineers fail to attract and even repel the best engineers to help them
- What you should do to make altruistic, high-performing engineers (i.e. the people you really want answering your questions) want to help you
- Why answering others' questions is one of the best ways to get great people to answer your own questions
- A very tactical self-serving benefit to answering questions and teaching others

[Timeless Career Advice] Empathy as an Engineer

Become An Open Source Master [Part 20] - Share What You Learn

Share what you learn as you go on your open-source journey. We can add comments to the code, write wiki pages or articles, or even file issues in the codebase to better understand. When we're ready to start contributing, we should pick a task, dive into the code, and start experimenting with it by adding print statements or breakpoints. This will help us get familiar with the code and the build process so that we can be more effective when making meaningful contributions.

Video reference: [10 Things I Learned from the jQuery Source](https://www.youtube.com/watch?v=i_qE1iAmjFg)

[How to learn a new codebase fast](https://www.jointaro.com/lesson/DX27hiXPJ4G7Czk2mwLL/how-to-learn-a-new-codebase-fast/).

Connect with James:

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

Improve

In the Improve phase, we focus on **deploying resources and initiatives** that shift our input metrics in the right direction, knowing that this in turn drives our desired output results. Improvement at Amazon has always been a cycle of innovation, experimentation, and rigorous measurement.

### Key Takeaways:

- **We prioritize inputs to drive results**: We align our teams, projects, and resources around improving leading indicators—our input metrics—which ultimately influence lagging outputs like sales and customer retention.
- **Click to Deliver Time became a key input metric**: We tracked every step of the fulfillment process and launched targeted initiatives to speed up delivery, knowing it directly impacted customer satisfaction and engagement.
- **We scaled operations through iterative improvements**: Over two decades, we grew our global delivery infrastructure—fulfillment centers, delivery stations, air cargo, and driver networks—through thousands of iterative changes, many of which were experiments that included both successes and failures.
- **We formalized improvement with the Working Backwards PR/FAQ process**: This mechanism ensures we innovate from customer needs, forcing teams to start with a press release and FAQ to define how a proposed improvement solves real problems.
- **Improvement and analysis form a feedback loop**: Every improvement is followed by measurement and analysis. This iterative cycle lets us reinforce what works and eliminate what doesn’t, ensuring continuous refinement of our systems.

To dive deeper into Input Metrics Mastery and learn more from Bill and Colin, follow these links:

- Take the full course at their website: <https://workingbackwards.com/>
- Buy the book: <https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595>
- Bill's LinkedIn: <https://www.linkedin.com/in/bill-carr/>
- Colin's LinkedIn: <https://www.linkedin.com/in/colinbryar/>

Build Deep Relationships Quickly In Tech [Part 8] - In-Person Is King

Remote and flexible work are amazing, but they do come with massive downsides, especially when it comes to networking. This lesson teaches you:

- The fatal flaw with remote work, particularly with accruing social capital
- Why humans aren't intrinsically wired to work remotely (quite the opposite)
- What gets lost in translation during remote work and video calls
- What types of engineer should prioritize in-person work

Motivated IC Auto-Didact

In this segment of the course, we begin translating theory into practice by applying the essence of management—creating positive and sustainable change—to real-life situations. We're guided through four exercises that challenge us to think creatively and proactively like effective managers.

- We approach each scenario by recalling that our role as managers is to **generate positive, lasting improvement** in our organization’s performance.
- We recognize that the scenarios are vague on purpose, so we must **draw from our own experiences** to interpret and respond thoughtfully.
- In the first exercise, we examine how to support a **highly motivated, self-learning individual contributor**, and consider what impact we can create to further enable their growth and contribution.
- We are encouraged to identify the **Delta**—the change we can influence or initiate—and write down our strategy for each case, reinforcing our understanding through reflection and application.

If you want to learn more from Gilad, he shares free leadership advice daily on [LinkedIn](https://www.linkedin.com/in/giladnaor/?utm_source=taro&utm_medium=course&utm_campaign=cta) and weekly on the[ δeltas newsletter](https://posts.managementdeltas.com/?utm_source=taro&utm_medium=course&utm_campaign=cta)

How Managers Hire Great Engineers [Part 2] - John's Success With Recruiting

If you want to hire great engineers, you're in great hands by taking this course. From this lesson, you will:

- Learn about [John's](https://www.linkedin.com/in/jwegan/) journey from an engineer to managing an organization of around 100 engineers
- Understand the challenges and strategies involved in doubling an engineering team year after year
- Discover how [John](https://www.linkedin.com/in/jwegan/) personally contributed to hiring dozens of engineers and conducted over 300 interviews
- Gain insights into shaping engineering processes and promoting the company’s brand through recruiting events and meetups

Connect with John Egan on LinkedIn: [**https://www.linkedin.com/in/jwegan/**](https://www.linkedin.com/in/jwegan/)

The Most EVIL Way To End An Interview (And How Not To Do It)

Here are the core points from the video:
- It is **never** okay to end an interview early because the candidate wasn't good enough. This is immensely disrespectful, especially for an onsite interview where the candidate carved out an entire day to do it (likely taking PTO if they are currently working).
- As an interviewer, you are also representing your company. If you do this, you are hurting your company's reputation as people talk - That candidate is very likely to tell others that your company is a horrible place to interview at.
- When this scenario happens, *the proper thing to do is to switch gears and go entirely into maximizing candidate experience* (as your goal isn't collecting signal anymore). This involves:
  - Giving them hints aggressively to help them complete the problem
  - Pair programming with them and trying to teach them - Use your interview to make the candidate a better software engineer!
  - Allocating more time for them to ask questions about the company - Try to get them excited! If you do this properly, they'll want to interview with your company again at a later time. People change - They may come back in a few years and be an absolutely incredible engineer you 100% want to hire.

Related resources:
- [Full session on being an amazing interviewer](https://link.jointaro.com/NhjenQ5vERKwRPdb9) - This is where this clip was cut out from.
- [Full 1 hour+ Masterclass On Acing Your Big Tech DSA Interview](https://link.jointaro.com/VfSeuUFiXNtKa5if7)
- [Full 1.3 hour Masterclass On Acing Your Big Tech System Design Interview](https://link.jointaro.com/Tmqs62Lw7WV4qDw59)
- [How Alex Got Into Meta With 0 Prior Leetcode Experience](https://link.jointaro.com/vaNH1hjRUhmF8ibSA)

SWE Internship Survival Guide [Part 16] - Diversify Your Mentors

As you approach the end of your internship, one of the most important factors in getting a return offer is how you’re evaluated during your performance review. This lesson focuses on how to set yourself up for success by building strong relationships across your team. Here are the core points from the lesson:

- Don’t rely solely on your assigned intern mentor—build relationships with multiple teammates to avoid single points of failure
- You’ll receive 360 feedback at the end of your internship, so proactively engage with others who can speak positively about your work
- Identify 2–3 potential advocates by week two and keep them updated through code reviews, one-on-ones, or casual check-ins

Learn how to build relationships here: [\[Masterclass\] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

Tech Lead Blueprint 10/17 - Commit To Project Success

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

Break Into Tech And Become A Software Engineer [Part 17] - The Chicken vs. The Egg

In this lesson, Brian addresses the challenge of gaining experience as a software developer when transitioning careers, offering practical solutions beyond traditional routes.

This lesson covers:

- The limitations of open source projects, highlighting their high barriers to entry and explaining why they may not be the best route for everyone
- Freelancing as a more straightforward option for gaining experience, which can lead to valuable work and opportunities
- Turning a side project into a legitimate business, providing either career validation or even a pathway to financial independence without needing a traditional job

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

Break Into Tech And Become A Software Engineer [Part 19] - Selling Yourself As A Developer

In this lesson, Brian explains how to effectively market yourself as a software developer by positioning your skills and experience clearly to potential employers.

This lesson covers:

- Presenting yourself as a software developer, ensuring your resume and LinkedIn profile immediately reflect your skills and experiences in the field
- Avoiding terms like "junior" or "aspiring" developer and instead using strong language that showcases confidence, such as "architected," "led," and "deployed"
- Framing your achievements with a formula that highlights the technology used, the features created, and the outcomes achieved, demonstrating the value you bring to a team

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

15 SWE Years In 1.5 Hours [Part 20] - Conclusion

Congratulations on making it to the end of the course! The goal of this course was to capture Rahul's biggest, broadest, higher-level learnings across a multitude of core software engineering subjects. While this is indeed valuable, it's impossible to master a massive topic like all of data structures and algorithms in just 5 minutes

To go deeper into these subjects, we recommend following our learning path here: [Become A Better Engineer](https://www.jointaro.com/learning-paths/become-a-better-engineer/)

[Become A Go-To Person 13/18] Answer Questions 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/)

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.