[Timeless Career Advice] Mid Year and End of Year Reviews

Amazon Metrics Map Example

In this lesson, we walk through **two core techniques—Metrics Mapping and Customer Experience Mapping**—that helped us systematically discover and define the input metrics that truly matter. These methods gave us a more granular, customer-focused way to understand and improve our business performance at Amazon.

### Key Takeaways:

- **We used Metrics Mapping to break down strategic goals**: Starting with broad objectives like lowering cost structure, we recursively drilled down to discover the specific drivers (e.g., shipping cost, pick cost, forecast accuracy) and converted them into measurable input metrics.
- **We cast a wide net during brainstorming**: In the early stages of metrics mapping, we didn’t worry about whether we could measure something yet or whether it was immediately useful. Our priority was to be comprehensive.
- **We built Customer Experience Maps to capture every user touchpoint**: From site entry to search, checkout, and delivery, we identified every customer interaction and defined metrics for speed, quality, and cost—measured both from the customer's and Amazon’s point of view.
- **We stayed grounded in the customer’s perspective**: Instead of focusing on internal outcomes like revenue per page view, we measured how intuitive, fast, and helpful each experience was for the customer, ensuring our metrics aligned with long-term value creation.
- **We operationalized customer obsession**: These techniques gave us a structured, measurable way to uphold our customer-obsessed culture. Other companies have found these frameworks to be transformative in how they assess and improve their own customer experience and operations.

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 11] - Identifying Fit

Some people simply aren't meant to get along, and you will run into a lot of these people across your career. This lesson teaches you:

- Why finding right fit connections is so important for networking, particularly with your efficiency
- How professional networking really isn't that different from making friends "in real life" (IRL)
- Solidarity angles you can leverage to find good fit connections

[Part 3] Software Engineer Onboarding: Understand Tactical Decisions

Learn the product to make good tactical decisions.

Within the first few weeks of your onboarding, you should have have fixed a few bugs and . Now it's time to slow down a bit and do some reflection on the decision-making process and priorities of the team.

- [How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/how-to-build-deep-relationships-quickly-in-tech-12172022/)
- [The Crucial First Step To Building Relationships That Everyone Misses](https://www.jointaro.com/lesson/YPniDFNQqoHEpYHC9JEq/the-crucial-first-step-to-building-relationships-that-everyone-misses/)

This is part 3 of a 4 part series from Daniel about how to **most efficiently** and **most effectively** onboard into a new team or company. What should you spend your time doing in the first few months of joining, and how should that change based on your level? 

This masterclass covers this topic from the perspective of Daniel Tomko, a 20 year Big Tech veteran. Daniel spent 11 years at Microsoft and 8 years at Meta in various senior IC and management positions. 

- [Go to part 4 of the masterclass here](https://www.jointaro.com/lesson/JFvfEoKshdPWuiCuy3GY/part-4-software-engineer-onboarding-understand-strategic-decisions/)
- [Go back to part 1 of the masterclass here](https://www.jointaro.com/lesson/IYZRmwp33E3TBeFQFr9c/part-1-software-engineer-onboarding-embrace-your-lack-of-knowledge/)

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

SWE Internship Survival Guide [Part 14] - Debugging

Debugging is a vital yet often underestimated skill for software engineers, especially interns who are frequently tasked with bug fixes or need to debug their own code. Here are the core points from the lesson:

- Interns often start with low-priority bugs or tackle backlog issues, making debugging a key part of ramping up and delivering impact
- Effective debugging requires identifying the relevant code, using logs or dashboards, and writing down your hypotheses to stay focused
- Reframing debugging as evidence gathering for a potential question helps you avoid tunnel vision and often leads to discovering the root issue
- Common mistakes include poor organization, incorrect environment setup, and focusing on irrelevant details—clarifying these with teammates is encouraged

Go through the debugging masterclass here: [\[Masterclass\] How To Become A Debugging Master And Fix Issues Faster](https://www.jointaro.com/lesson/ioR6WzamAIUTpySLAr7o/masterclass-how-to-become-a-debugging-master-and-fix-issues-faster/)

Build Deep Relationships Quickly In Tech [Part 13] - Lead With Kindness

Many engineers get impatient when it comes to networking, frustrated that it takes so long to get someone to provide meaningful value to them. It doesn't need to be this way. This lesson teaches you:

- A very simple way to understand networking and how to convert it into something that provides concrete benefits
- Why leading with kindness is the most powerful mindset you can have to build trust *fast*
- How leading with kindness really isn't that difficult, especially if you're smart and on the lookout for disproportionate activities
- What it means to lead with kindness, explained with an in-depth example that is very relevant to Taro

Ship & Grow 500k+ User Side Projects [Part 5] - Make It 5x Better With 0 Effort

It can be tempting to make some money on your side projects given how much time you're putting in. However, this is almost never worth it. This lesson teaches you:

- Why the ROI on adding paywalls and ads to your product is pretty bad, especially when considering the true purpose of your side project
- Why payments are way more complex than you think
- The many downsides of adding ads to your product
- A little bonus you can do on top of making your product free and ad-free

Clear Communication For SWEs [Part 10] - Rephrasing For Clarity

In this video, I delve into the art of rephrasing for clarity, emphasizing its significance in reaching a wider audience and maintaining engagement. Techniques like simplifying language, breaking down complex ideas, using synonyms, and restating key points are explored with practical examples. Viewers are encouraged to apply these strategies to enhance message comprehension and audience connection.

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

Tech Lead Blueprint 13/17 - Team Culture

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

Easy Tactics You Can Apply Today To Increase Your Focus

Which of these are valid tactics to minimize the distraction from your phone?

True or false: As an engineer, it is important for you to attend every possible meeting so you can know everything that is going on, therefore empowering your productivity.

As a software engineer, why is it crucial to reject meetings when possible?

Maximize your focus and productivity as a software engineer by minimizing any distractions.

Get The Rating You Deserve [Part 10] - Clarity On Deliverables

**In this video, we discussed the importance of clarity in defining and achieving our work goals.**

To ensure we're consistently making progress and maximizing our impact, we should:

- **Continuously seek clarity:** Regularly revisit and refine our goals and deliverables, especially in dynamic work environments.
- **Balance long-term and short-term priorities:** Prioritize tasks that align with long-term objectives while also addressing urgent issues.
- **Take ownership of our work:** Proactively seek clarity from our managers and take initiative in defining our own expectations and deliverables.
- **Utilize effective time management techniques:** Allocate specific time for focused work and unexpected tasks to maintain productivity and avoid feeling overwhelmed.

By following these guidelines, we can increase our effectiveness, reduce stress, and achieve greater success in our professional endeavors.

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

The First Thing You Need To Do To Set Yourself Up For Promotion

Which of the following is the foundation for your promotion plan?

Why is understanding your strengths so important towards your tech career growth?

Ace The ML System Design Interview [Part 10] - Final Thoughts

Congrats on making it all the way to the end of this course! We've now covered the key elements to help you succeed in your machine learning system design interviews. Remember, having a structured approach is essential. Here are the core points from this lesson:

- Use a system to guide you through the interview, helping to avoid common pitfalls and ensuring key aspects of the problem are addressed
- Treat time estimates for each stage as a guide, but prioritize the core sections: big-picture system design, data, and modeling
- Communicate your approach to the interviewer at the beginning of the interview to set clear expectations
- Demonstrate structure and a systematic approach to impress interviewers and showcase engineering capabilities

If you like what Ilya has to say, subscribe to his YouTube for more high-quality ML/AI career guidance: [MLEpath - YouTube](https://go.mlepath.com/taro-youtube-mlepath)

If you want hands-on support from Ilya to crack the FAANG ML interview, join his coaching program: [MLEpath - Coaching Program](https://go.mlepath.com/taro-march-25)

Get The Rating You Deserve [Part 11] - Add Incredible Value

**In this section, we explored the concept of adding incredible value to our work.**

To truly make a significant impact, we should:

- **Go the extra mile:** Strive for excellence and push beyond the minimum requirements.
- **Prioritize finishing tasks:** Complete projects thoroughly, including documentation and testing.
- **Seek continuous feedback:** Actively solicit input from colleagues and managers to improve our work.
- **Balance work and rest:** Maintain a sustainable pace by incorporating regular breaks and time off.
- **Focus on long-term impact:** Adopt a long-term perspective and prioritize tasks that contribute to strategic goals.

By consistently striving to add incredible value, we can become indispensable assets to our teams and organizations.

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

Asking Great Questions [Part 25] - How You Should Evolve

It's important to make sure that you're always getting better - As long as you're improving, you will eventually become a rockstar engineer. So how does that work when it comes to judging your question asking ability? This lesson teaches you:

- What seniority does not mean when it comes to asking questions
- What seniority actually means when it comes to asking questions
- A simple framework you can use to evaluate the level your questions are at, split by junior/mid-level/senior+

Become A Debugging Master [Part 10] - Document Your Process

If you want to debug faster and avoid getting stuck, one of the best habits you can build is writing everything down. Here are the core points from the lesson:

- Document your hypotheses, tests, and findings continuously during debugging to create clarity, reduce mistakes, and avoid repeating the same experiments
- Writing things down makes it easier for teammates to jump in, share context quickly, and collaborate effectively when tackling complex bugs
- Even when debugging alone, written notes help you stay organized, maintain momentum, and prevent morale-killing mistakes like redoing work you already tried
- Good documentation habits (like clear pull requests and linking to issues) allow future debuggers to “time travel” and understand why code was written a certain way
- Strong debugging cultures start with individuals — write as you debug today, and your future self (and team) will thank you

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

[Become A Go-To Person 16/18] Recap

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

Ship & Grow 500k+ User Side Projects [Part 7] - KISS

Engineers naturally gravitate towards complexity, and it shows in how they communicate and design things. This is a problem when it comes to side projects. This lesson teaches you:

- The beautiful, often under-appreciated value of simplicity
- Assumptions you shouldn't make about the end-user
- What it means to KISS (Keep It Simple, Stupid), explained with an in-depth example

The 4 Paths To Manager Growth. Choose One.

[**Ethan Evans**](https://www.linkedin.com/in/ethanevansvp/) is a retired Amazon VP who now teaches managers how to break into executive levels.

He shares how to get promoted as a front-line manager (M1). The pre-requisite is that you must do good work. This means motivating your team, delivering results, and organizing them effectively. M1s are focused inward and downward, with most of their time and attention on their team. M2s (managers of managers) focus on the bigger picture, considering how their team fits into the larger organization and collaborating for overall success.

**Four main ways to grow:**

- **Organic growth:** Your team and the company naturally expand, increasing your responsibility.
- **Filling holes:** Someone above you leaves, and you're chosen due to your performance.
- **Reorganizations:** Teams get shuffled, and you absorb parts of others' responsibilities.
- **Lead a new initiative:** Successfully launching a new project demonstrates leadership and initiative, potentially leading to promotion.

When times were good (i.e. metrics were strong and the company was doing well), there was more capacity for people to get promoted. For example, the gold, silver, and bronze medalist (3 people) may have gotten promoted, but in a stagnant company, only the gold medalist would get the promo.

Although you can't control when people leave or if there will be a re-org, what you can do is **focus on being the top performer:** Consistently deliver excellent results, demonstrate strong leadership, and be ready to take on additional responsibilities.

Relevant follow-ups:

- [Would you recommend SDEs try a rotation as an SDM?](https://www.jointaro.com/question/BRNUnPJ0y2BttQhPNmCu/would-you-recommend-sdes-try-a-rotation-as-an-sdm/?playlistId=oz0mnJvHHgM8NfVF7rgp)
- [\[Taro Top 10\] Software Engineer To Engineering Manager (IC -&gt; M Track)](https://www.jointaro.com/playlist/oz0mnJvHHgM8NfVF7rgp/)

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.