Have A Conversation About Conversation

In this lesson, we explore how to set up a healthy, effective relationship with an engineering manager by having a “meta” conversation early—one that focuses not on tasks, but on how we want to work together.

- We introduce the idea of a personal “README file,” where we proactively explain our background, working style, motivations, and concerns so our EM understands how to support us.
- We emphasize sharing what energizes us and what drains us, giving our manager the context they need to advocate for us and assign work that helps us thrive.
- We suggest regularly reflecting on what’s going well and what isn’t—using 1:1s not just for status updates, but for deeper calibration on collaboration.
- We call out the importance of explicitly discussing how we prefer to receive (and give) feedback, whether direct and verbal or written and reflective.
- We highlight that starting the relationship with these meta conversations sets the foundation for a smoother, more aligned partnership with our EM.

Embodying The Leader

If you want direct interview support from Alex and Uzair, take their live Maven course with discount code **TARO10**: <https://maven.com/alex-kliotzkin/acing-em-interviews>

In this lesson, we learn how to effectively showcase leadership qualities during engineering manager interviews by understanding the most commonly assessed leadership abilities. Interviewers are assigned specific attributes to evaluate, and crafting thoughtful, real-world stories that highlight these traits is essential.

- **We prepare stories around 9 common leadership abilities**, including growing talent, delivering under pressure, and influencing stakeholders, knowing these form the backbone of most behavioral interview questions.
- **We ensure each story highlights not just outcomes, but the judgment and systems we used**, especially in situations involving conflict, ambiguity, or strategic risk.
- **We practice showcasing our resilience and decision-making**, such as dealing with underperformers, making fast-paced calls under time pressure, or navigating conflict with senior stakeholders.
- **We recognize that good answers require emotional maturity**, thoughtful communication, and the ability to reflect on learnings—not perfection or bravado.
- **We strive to embody senior leadership through our communication style**, avoiding over-explaining, exaggeration, or emotional volatility, and focusing instead on clarity, calmness, and authenticity.

So What Do Engineering Managers Do?

If you want direct interview support from Alex and Uzair, take their live Maven course with discount code **TARO10**: <https://maven.com/alex-kliotzkin/acing-em-interviews>

An engineering manager’s role extends far beyond attending meetings or writing reports—it centers on one core responsibility: *Ensuring the team delivers*. This requires balancing accountability, leadership, and adaptability across multiple domains.

- **Facilitate Decision-Making and Own Processes:** EMs don’t always make every decision, but they must facilitate the decision-making process and ensure team adherence to defined practices like quality standards or definitions of done.
- **Own Delivery Outcomes:** Regardless of who does what on the team, the EM is ultimately responsible for all deliverables—both successes and failures.
- **Bridge Business and Engineering:** EMs connect the technical team with the broader business, helping engineers understand customer needs, product lifecycles, and why building the *right* thing is more important than just building it right.
- **Ensure Product Integrity and Fill Gaps:** Maintaining consistent product quality across releases is part of the EM's responsibility. They must also step into roles as needed—whether that’s scrum master, product owner, or project manager—to remove blockers and enable progress.
- **Represent the Team and Grow Talent:** EMs act as the external face of the team to stakeholders and leadership while also coaching and developing individual engineers to help them grow in their careers.

Motivation

If you want direct interview support from Alex and Uzair, take their live Maven course with discount code **TARO10**: <https://maven.com/alex-kliotzkin/acing-em-interviews>

In this video, I discuss the common challenges engineers face when preparing for engineering manager interviews, highlighting that the criteria for these roles differ significantly from those of individual contributor positions. Many engineers are unaware of these differences, which can lead to confusion and poor performance during the interview process. I emphasize the importance of understanding these unique expectations to improve your chances of success. I encourage viewers to reflect on their own experiences and consider how they can better prepare for these types of interviews.

Weekly Business Review

###### In this lesson, we introduce the **Weekly Business Review (WBR)** as Amazon’s core mechanism for consistently analyzing, improving, and controlling business performance. This structured, weekly ritual helped us align leadership around metrics, dive deep into customer experience, and create a culture of truth-seeking and operational rigor.

### Key Takeaways:

- **We used the WBR to bridge strategy and detail**: Contrary to conventional advice, we didn’t choose between high-level strategy and operational detail—we embraced both. The WBR let senior leaders dive deep while still steering big-picture strategy.
- **We built the WBR around the customer journey**: Our report flowed from financials to marketing, browsing, shopping, fulfillment, and customer support. Each department leader owned and explained their metrics—not analysts—ensuring accountability and depth.
- **We started before everything was perfect**: We launched the WBR even before our metrics were fully refined. By including many metrics upfront, we learned over time which ones provided signal and which were noise.
- **We continuously refined our metrics**: In each WBR meeting, we didn’t just review results—we asked whether we were measuring the right things and how to improve clarity and relevance of our metrics.
- **We made it a disciplined habit**: Reports were automated and delivered every Monday by 7 a.m., enabling prep ahead of the all-company WBR. This rhythm created organizational focus, enabled early issue detection, and aligned everyone around the brutal facts of performance.

The WBR was not just a meeting—it was a **weekly dose of operational truth** that made Amazon more customer-obsessed, data-informed, and execution-focused.

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

The Do's and Don'ts For Good Metrics

Here's the exercise worksheet: [Metrics Template and Worksheet Combined (B2C + B2B)](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/courses%2Fslides%2FMetrics%20Template%20and%20Worksheet%20Combined%20$B2C%20%2B%20B2B$.xlsx?alt=media&token=3951bfd7-ef9e-4c81-9245-80043a4973d0)

In this wrap-up, we assign a powerful, hands-on homework exercise: to generate a **comprehensive set of input and output metrics** that can answer three foundational business questions. This process, built on the tools and frameworks we've covered, is the first real step in building a metrics-driven, customer-obsessed organization.

### Key Takeaways:

- **We focus on three key questions**:

  1. How did our business do last week?

  2. What was the customer experience like last week?

  3. Are we on track to hit our goals?

- **We use four core methods to identify input metrics**:

  1. **Metrics Mapping** – Drill down from business goals to uncover metric drivers.

  2. **Customer Experience Mapping** – Map and measure every customer interaction.

  3. **Customers** – Mine support data and engage with end users directly.

  4. **Defects** – Use root cause analysis (like CoEs) to find and track preventable errors.

- **We cast a wide net—hundreds of metrics is a good start**: This is not about picking the “best” metrics yet. We brainstorm 200–300 across all functions without concern for whether they’re inputs or outputs, or even if they can be measured immediately.

- **We avoid vague or compound metrics**: Good metrics are discrete, observable, and repeatable by different people or systems. Avoid averages where possible—percentiles and RMS error are often better indicators of variation and performance.

- **We assign priorities and assess data readiness**: After brainstorming, we tag each metric as Priority 1, 2, or 3 and indicate whether the data is currently available. This helps build a phased implementation plan for metrics collection and review.

This assignment launches the foundational work needed to operationalize a **weekly business review (WBR)**. It sets the stage for measurement, analysis, improvement, and control—ensuring our teams are focused on the right inputs to drive the right outcomes.

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

Building A Metrics Map

In this lesson, we explore **practical techniques** for identifying the input metrics that matter most. Through methods like **metrics mapping** and **customer experience mapping**, we gain a clearer, more quantitative view of what drives our business forward—especially from the customer’s perspective.

### Key Takeaways:

- **We prioritize input metrics and customer interactions**: Too often, businesses rely heavily on output metrics. We recommend looking deeper into input metrics—particularly those tied to customer behavior and experience.
- **Metrics Mapping helps us discover drivers of key metrics**: We start with a business goal or known metric, then recursively ask what drives it and how we can measure those drivers. This technique reveals a broad and useful set of input metrics.
- **The process is recursive and comprehensive**: We drill down from each metric or goal until we can’t go any further, building an extensive network of quantifiable drivers. Repeating metrics across branches is fine—what matters is completeness.
- **The end goal is a flat, exhaustive list of metrics**: While the mapping exercise may begin as a hierarchy, we ultimately compile all the discovered metrics into a single, non-hierarchical list for practical use and monitoring.
- **Finding input metrics is an ongoing process**: This isn’t a one-time task. We continuously revisit and expand our metric set as our business, goals, and customer needs evolve.

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

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

Master the Art of Receiving Quality Feedback (from an ex-Meta Staff Researcher)

In this time of uncertainty in the workplace and job market, what’s one skill you can develop that would **yield disproportionate rewards**?

It’s hard to pinpoint *the one* skill, but I believe the **ability to ask for, receive, and iterate on feedback** is incredibly important. Adaptability is what helps us not just survive, but thrive—and adaptability begins with how well we take in and work with feedback.

When you learn to process feedback effectively, **you develop a kind of likability and professional superpower** that organizations and leaders find hard to ignore.

We hear feedback all the time, so what exactly are we trying to get better at? Most of the feedback we receive is vague and hard to act on. Think about examples like “improve your communication” or “increase your coding speed”—where do you even start? The **key is in asking for feedback** proactively, clarifying and chunking it down into something actionable, working on it, and then circling back to check if you’ve understood and implemented it well.

In this talk, we’ll learn how to do exactly that—a process I call “**exhausting the feedback process**,” a phrase I often use in my coaching practice. We’ll also explore how to handle feedback that’s just plain off the mark (spoiler: it’s rarely useful to say that outright to the person giving it).

Yogi on LinkedIn: <https://www.linkedin.com/in/yogi1/>

Gilad’s Take On Management

In this video, we explore the core responsibility of managers and define what great management truly entails. The speaker provides a clear, actionable definition of management and unpacks each part of it to guide us toward becoming more impactful leaders.

- We learn that **the essence of management is to create a positive and sustainable change in the organization’s performance**, a definition we are encouraged to internalize and apply.
- We embrace the idea that management is a **creative, proactive discipline**, not just a reactive one—our actions should be intentional and forward-looking.
- We are reminded that our impact must be **positive** and **lasting**, focusing on growing people and systems that perform well even in our absence.
- We are taught to focus on **creating deltas**, meaning our value lies in the improvement we drive, not in maintaining the status quo.
- We expand our view beyond just our teams, recognizing that **great managers influence the broader organization**, constantly looking for opportunities to elevate overall performance.

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)

Foundational Ideas

In this key section of the course, we dive into the essential machine learning concepts that consistently appear across all types of ML interviews. This foundation prepares us to explain not just the “what,” but the “why” behind our choices—something interviewers value highly.

- We review core **ML paradigms** like supervised, unsupervised, and reinforcement learning, along with real-world examples to explain their use cases clearly.
- We explore **machine learning tasks** such as classification and regression, and when to apply specific evaluation metrics like precision, recall, or RMSE.
- We gain a deep understanding of **model performance** concepts—bias/variance trade-off, underfitting/overfitting—and how to recognize and address them.
- We cover **validation strategies**, data leakage prevention, and the right use of metrics beyond just accuracy, such as AUC-ROC and F1 score.
- We enhance our skills in **feature engineering**, **optimization algorithms** (like SGD and Adam), **model selection reasoning**, and **dimensionality reduction** techniques like PCA and UMAP.
- We also touch on **LLM fundamentals**—such as Transformers and encoder-decoder architectures—to stay current with emerging trends.
- Most importantly, we practice explaining all of this in a way that connects to real-world problems and highlights our decision-making skills.

If you want to learn even more from Yayun:

- Book 1 on 1 career guidance with her here: <https://calendly.com/your-friend-yayun/1on1>
- Follow her on LinkedIn: <https://www.linkedin.com/in/yayunjin/>

Course Roadmap

In this part of the course, we’re given a roadmap that outlines the full journey of preparing for machine learning interviews. Each section is designed to build our skills systematically and strategically, based on real-world experience and mentorship insights.

- We start with **essential ML concepts**, learning how to clearly explain high-frequency topics that appear in nearly every interview.
- We then move into **practical ML coding and modeling**, covering notebooks, EDA, model selection, feature engineering, and evaluation techniques.
- **Coding foundations** are reinforced to help us succeed in general algorithm rounds, with a focus on what companies expect from ML candidates.
- We’ll tackle **ML algorithm coding**, where we may be asked to implement algorithms like decision trees or k-means from scratch.
- **ML system design** is emphasized for senior-level roles, with frameworks and examples for building scalable systems.
- Finally, we prepare for **project deep dives and behavioral interviews**, learning how to share impactful stories, followed by crafting a personalized **study plan** that fits our timeline and goals.

If you want to learn even more from Yayun:

- Book 1 on 1 career guidance with her here: <https://calendly.com/your-friend-yayun/1on1>
- Follow her on LinkedIn: <https://www.linkedin.com/in/yayunjin/>

Let them carry it. You’ve done your part.

You’ve seen the pieces.\
Now we pull them together.

This final act is about how ownership moves—how everything you’ve practiced shows up when things get messy, unclear, or just plain stuck.

It’s less about new ideas, more about recognizing the patterns, and deciding what to do when they land on your desk.

**Workbook:** [Creator’s Orientation](https://drive.google.com/file/d/1sysZuPhlrLZbU5stxlJBqg3LAcGTy_S7/view?usp=sharing)

**Want to go deeper?**

- Explore more tools and courses at [**Taha’s Method**](https://www.tahasmethod.com/) — from interview prep to leadership development.

- Follow me on [**LinkedIn**](https://www.linkedin.com/in/tahahussain/) and subscribe to my weekly newsletter, [**The Conscious Leader**](https://tahahussain.substack.com/), for more lessons like these.

- Get 30% off [**Top Tech Leader**](https://bit.ly/tarotopleader) with code **ILOVETARO** (exclusive for Taro members).

What sounds like help can feel like control.

At some point, support starts to sound like hovering.\
And it’s hard to see when you’ve crossed that line.

This section takes a closer look at that moment—when helping quietly turns into handling.\
It’s more common than you think. Especially when you care.

**Want to go deeper?**

- Explore more tools and courses at [**Taha’s Method**](https://www.tahasmethod.com/) — from interview prep to leadership development.

- Follow me on [**LinkedIn**](https://www.linkedin.com/in/tahahussain/) and subscribe to my weekly newsletter, [**The Conscious Leader**](https://tahahussain.substack.com/), for more lessons like these.

- Get 30% off [**Top Tech Leader**](https://bit.ly/tarotopleader) with code **ILOVETARO** (exclusive for Taro members).

Maximize Your Equity And Benefits In Tech [Part 3] - Foundational Tax Concepts

Understanding how taxes work is key to making smart decisions about equity compensation—here are the core points from the lesson:

- Gross income is reduced by payroll taxes and deductions to determine adjusted gross income (AGI) and taxable income, which drives your federal tax liability
- Long-term capital gains (assets held over a year) receive lower federal tax rates than ordinary income, often saving high earners significant amounts
- State tax treatment varies—most states don’t offer preferential rates for long-term gains, and some, like Massachusetts, penalize short-term gains more heavily
- Investment losses can offset gains and up to $3,000 of ordinary income per year, but “wash sale” rules can disallow losses if you repurchase too soon
- The Alternative Minimum Tax (AMT) may kick in if you're using lots of deductions or exercising incentive stock options, so it’s important to model this in advance

Next steps with Andy:

- [Connect with Andy on LinkedIn](https://www.linkedin.com/in/andymoranio)
- [Leave feedback and/or sign up for Andy’s newsletter](https://subscribepage.io/taroequitycourse)
- [Schedule a consultation](http://adastrafp.com/contact-us/)

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

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

SWE Internship Survival Guide [Part 11] - Code Velocity

Your success as a software engineering intern hinges on one key metric: your ability to ship code consistently. Here are the core points from the lesson:

- Code velocity is the primary way interns are evaluated, so focus your time on writing and shipping impactful code
- Every company has a different pace, but you should ask your manager for benchmarks and observe full-time engineers to calibrate your own output
- Structure your day around long blocks of uninterrupted coding time, and avoid distractions like intern socials or long-term architecture meetings
- Make small, frequent code changes instead of large ones to make code review easier, allow quicker course correction, and prevent painful merge conflicts
- Communicate your approach with your team so they understand your intent to seek faster feedback through smaller pull requests

SWE Internship Survival Guide [Part 4] - How Internships Work At Top Companies

Top-tier internships at companies like Meta or Google are structured, high-impact opportunities that can transform you into a confident, job-ready new grad. Here are the core points from this lesson:

- Legitimate internships at top companies have clear structure—interns are given managers, mentors, well-scoped projects, and timelines
- Interns are treated like junior engineers, often contributing to real production work and collaborating closely with full-time teammates
- Larger companies offer more formal evaluation processes for return offers, which helps reduce ambiguity and stress compared to smaller, less organized internships
- You’ll likely focus on one or two substantial projects to avoid context switching and to enable deeper, more meaningful contributions
- Adopt a collaborative mindset with fellow interns—success isn’t zero-sum, and sharing knowledge will help everyone grow and build stronger networks

Ship & Grow 500k+ User Side Projects [Part 6] - Least Clicks Design

You don't need to be a product design to build great software with a smooth user interface. This lesson teaches you:

- Why *every* engineer needs to care about UX, not just front-end engineers (web/mobile)
- The core philosophy you need to remember when crafting user interfaces
- The difference between a good product and a bad product when it comes to least clicks design
- What it looks like to truly champion least clicks design, explained with an in-depth example

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.