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

Asking Great Questions [Part 17] - Target Domain Experts

A big part of getting great answers quickly is to ask the right people, especially with technical questions as different engineers specialize in different things. This lesson teaches you:

- Why targeting makes it more likely for your question to be answered
- What it looks like when you target domain experts in your question, explained with an in-depth example
- How to find domain experts to tag in your questions

Break Into Tech And Become A Software Engineer [Part 13] - Establishing Your Brand Online

In this lesson, Brian discusses the importance of focusing on valuable content when writing online, rather than chasing likes or negative engagement.

This lesson covers:

- Avoiding negative or clickbait content that might gain attention but harms your professional reputation, such as romanticizing rejection or posting rage bait
- The value of sharing interesting challenges, technical problems, and personal experiences with solutions, which fosters meaningful conversations and builds credibility
- Posting about specific technologies, problems you’ve solved, and snippets of code to engage with professionals and attract potential career opportunities

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

How to Crack System Design Interviews - Part 9: Effective Communication

This video details the scoring criteria for system design interviews, focusing on scalability, reliability, and communication. We learn how to demonstrate strong technical skills and cultural fit:

- **Identify and mitigate bottlenecks:** We should proactively identify scalability and performance bottlenecks in our design and propose effective mitigation strategies.

- **Address potential failures:** We must analyze potential points of failure, including those in external systems, and explain how we would handle them.

- **Communicate clearly and effectively:** We need to present our solution in a structured and organized manner, using appropriate terminology and incorporating feedback constructively.

- **Demonstrate cultural fit:** We should align our design choices and communication style with the company's values and priorities, showcasing our understanding of their engineering culture.

- **Maintain professionalism:** We must conduct ourselves professionally throughout the interview, avoiding inappropriate jokes or comments and demonstrating openness to feedback.

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

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

Talent Density

Working at a Big Tech company means joining an environment that systematically attracts top-tier talent due to its high compensation and prestige. This creates a unique ecosystem where growth, learning, and problem-solving are significantly accelerated.

- **Talent Follows Compensation**: Competitive pay naturally draws in highly skilled engineers. While exceptions exist, the vast majority of engineers in Big Tech are above-average in both technical skills and motivation.
- **Noticeable Culture Shift**: Engineers often report that, compared to previous jobs, colleagues in Big Tech care more about code quality, engineering rigor, and continuous learning.
- **High Learning Potential**: Being surrounded by experienced and skilled engineers ensures a constant opportunity to learn. Teams often include individuals who are more experienced, creating a strong environment for mentorship and knowledge transfer.
- **Collective Wisdom and Problem Solving**: The scale and maturity of these organizations mean that most technical challenges have been encountered, and solved, before. Success often comes from leveraging internal networks to find engineers who’ve already navigated similar problems.
- **Standing on Shoulders of Giants**: Engineers thrive by observing and applying best practices from tech leads and staff engineers, accelerating their own effectiveness and impact through this ecosystem of shared expertise.

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

Asking Great Questions [Part 20] - Make Fulfillment Easy

In order to get what you want, you need to know *exactly* what you want. This can be harder than many engineers realize. This lesson teaches you:

- The importance of reducing fulfillment friction, presented through the perspective of the person fulfilling the favor
- What it means to make fulfillment of your favor easy, shown with an in-depth example covering a common engineering ask
- How the spectrum behind fulfillment friction reduction is actually incredibly deep, especially if you're creative
- Ideas to make fulfillment easier with examples covering 3 more very commonly asked for favors

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

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

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

Come Up With 500k+ User Project Ideas [Part 16] - Bias Towards Action

Talk is cheap. Action is expensive. Engineers often fall into a habit of thinking about what to do instead of actually doing anything. This lesson teaches you:

- How engineers struggle internally with their side projects, leading to nothing getting built
- Why you should just quickly build a side project idea after you have done some basic validation
- Why running a survey is one of the worst ways to validate a side project idea
- How most engineers struggle with user research (UXR)
- What book you should read if you really, really, really want to do UXR

Here's the UXR book Alex mentioned (it's one of the few books he's actually read): <https://www.momtestbook.com/>

How To Build A Fulfilling Career Path For Your Engineers

We’ve all been there – you want to be there for your team, but you end up pushing back 1:1 meetings because there’s a lot on your plate. Or your team member wants to practice a particular framework but you don’t have any upcoming work that would let them do that. Or you’re heading into a career development conversation and trying to figure out how to share some tough feedback.

At the same time, a regular piece of feedback from individual contributors is that they’d like their managers to provide more support for their career development..

So what’s an engineering manager to do? How can we help our teams build fulfilling careers while juggling their asks with all the other work on our plate? And how do we balance their development areas with completing the work that needs to be done? Doing this well will not only help our team’s satisfaction and morale, but also support our own progress in our organization – but it’s easier said than done.

This talk provides concrete tips to help you do better in supporting your team on their career development journey. We’ll talk about strategies to:

- The bedrock for a fulfilling career (awareness)
- Make time for 1:1s – even when things get busy!
- Focus 1:1’s on growth & development (not work)
- Balance between improving weaknesses versus cultivating strengths

This is a talk Rahul gave at the [Tech Leaders Chat](https://www.meetup.com/tech-leader-chats/events/293719388/) hosted by [Multitudes](https://www.multitudes.co/).

Tech Lead Blueprint 13/17 - Team Culture

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

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

Break Into Tech And Become A Software Engineer [Part 15] - Fostering Online Relationships

In this lesson, Brian shares his strategy for using comments and direct messages to build meaningful online connections and network effectively.

This lesson covers:

- Starting with genuine, thoughtful comments on posts to build rapport and avoid disingenuous engagement, which helps foster real conversations
- How to follow up comments by sliding into DMs, offering value first rather than asking for a favor, and creating opportunities for connection without being awkward
- The importance of short, 15-minute coffee chats to learn from others while keeping the conversation low-pressure and focused on mutual interests

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

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

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

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.