Taro Book Club: Designing Data Intensive Applications - Chapter 5 (Replication)

Topic: Chapter 5 - Replication

Session led by: [Rohit Katyal](https://www.linkedin.com/in/rohitkatyal/)

In this #taro-bookclub discussion, we'll be talking about Chapter 5 of [**"Designing Data-Intensive Applications"**](https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321) by Martin Kleppmann.

Here's the agenda:

- Let’s get to know each other with some quick introductions.
- We’ll break down and discuss the key concepts from Chapter 5.
- There will also be time for any questions and answers you might have.

Please send your questions ahead of time to [**Rohit Katyal**](https://www.linkedin.com/in/rohitkatyal/) in the [**Taro Premium**](https://www.jointaro.com/membership/) Slack, so that they can be included in the discussion.

Get ready for another engaging and informative session!

Lack of Control

Engineers at Big Tech often experience a deep lack of control over their work, compensation, and long-term impact. Here are the core points from the lesson:

- Politics and top-down decision making mean engineers can invest heavily in projects only to have leadership reject ideas or directions with no recourse
- Compensation elements like company multipliers are tied to overall corporate performance, which individual engineers have virtually no influence over
- Constant reorgs, shifting org charts, and manager reshuffling create instability and make teams feel like they’re moving for reasons that aren’t always merit-based
- Big Tech frequently kills projects, even promising or widely used ones, because they don’t meet multibillion-dollar expectations, leaving engineers demoralized and powerless over product fate

Ship & Grow 500k+ User Side Projects [Part 16] - Word Of Mouth

The most organic source of traffic is happy users simply telling their network how awesome your product is. This lesson teaches you:

- The main metric to understand when it comes to your word of mouth
- 2 product mechanisms you can add to juice up your word of mouth
- How to make an effective sharing flow, explained with an in-depth example
- How to make a compelling referral flow, shown with famous examples

Airbnb blog post about how they sharply refined their sharing flow (an oldie but a goodie): <https://medium.com/airbnb-engineering/growth-at-scale-getting-to-product-sharing-fit-ccb4b501ecf>

How Should I Practice For These Interviews?

In this lesson we talk about how AI is making previously time-prohibitive advanced data structures and algorithms newly relevant in coding interviews, and what that means for how you should prepare.

- **AI unlocks harder concepts by handling the boilerplate** — complex structures like tries, heaps, and LRU caches were rarely testable in a 45–60 minute interview because implementation alone could eat up 15–20 minutes; with AI generating that scaffolding in seconds, interviewers can now reasonably include them, making them worth studying once you've solidified the fundamentals.
- **What you actually need to demonstrate has shifted** — since AI handles much of the implementation, your value lies in recognizing when a given data structure is the right tool, clearly articulating *why* it helps (e.g. "a trie eliminates the factor of M by checking all patterns simultaneously through shared prefix traversal"), and writing precise prompts that reflect that understanding.
- **Master the basics first, and don't over-rotate on this** — the vast majority of interviews (roughly 95%) will not require these advanced concepts, so treat this as the final 5–10% polish layer, not the foundation; verification of AI output remains just as critical here as everywhere else in the interview.

Amazon Behavioral Interview [Part 19] - Taking An Unpopular Stance (Answer)

This video segment describes a situation where the interviewee took an unpopular stance in a meeting with leadership.

- **Identified the Conflict:** The interviewee disagreed with the company's decision to significantly shift resources from the US to India for customer support, primarily driven by cost-cutting measures.
- **Presented an Alternative Solution:** Despite the potential for backlash, the interviewee proposed an alternative solution:
  - While acknowledging the cost-effectiveness of hiring in India, they suggested leveraging the "Year Up" program to hire underrepresented talent in the US, aligning with the company's diversity and inclusion goals.
- **Faced Opposition:** The interviewee faced strong opposition from the CFO, who was primarily focused on cost-cutting measures and reacted negatively to the alternative proposal.
- **Continued to Advocate:** Despite the initial setback and lack of immediate recognition, the interviewee continued to advocate for the inclusion of the "Year Up" program.
- **Achieved Partial Success:** While the initial proposal was largely dismissed, the company eventually implemented a limited version of the "Year Up" program, demonstrating the long-term impact of the interviewee's advocacy.

This example highlights the interviewee's: ***Proactive Approach:*** *They identified a potential solution that aligned with company values.* **Courage and Persistence:** They were willing to express their dissenting opinion despite potential negative consequences. ***Focus on Long-Term Impact:*** *They demonstrated a commitment to long-term goals, such as diversity and inclusion, even when faced with immediate pressures.* **Ability to Learn and Adapt:** They acknowledged the limitations of their initial approach and demonstrated a willingness to adapt and find alternative solutions.

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

Taro Book Club: Designing Data Intensive Applications - Chapter 6 (Partitioning)

Topic: Chapter 6 - Replication

Session led by: [Bhavana Gannu](https://www.linkedin.com/in/bhavanagannu/) and [Suraj Singh](https://www.linkedin.com/in/suraj-singh-495b192b/)

In this #taro-bookclub discussion, we talked about Chapter 6 of [**"Designing Data-Intensive Applications"**](https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321) by Martin Kleppmann.

Ethical Concerns

Working at Big Tech can expose engineers to ethical dilemmas and reputational challenges, especially as these companies grow in size and societal influence. Here are the core points from the lesson:

- **Ethical baggage and public scrutiny** - Every large tech company accumulates controversy over time, from privacy scandals to monopolistic behavior. Employees often face external judgment and may feel conflicted about the company’s broader impact, such as gentrification and social displacement caused by high salaries and rapid expansion.
- **Disconnect between purpose and individual contribution** - Engineers may feel demoralized realizing their role (e.g., being engineer #80,532 at Google) probably won't meaningfully contribute to making the world a better place - especially for those motivated by social impact or purpose-driven work.
- **Reputation can shift dramatically** - Facebook was once viewed positively (e.g., in the late 2000s), but public perception reversed dramatically after scandals like Cambridge Analytica. Engineers went from proudly wearing company swag to avoiding brand affiliation in public. Similar sentiment shifts can hit any big company, even well-intentioned ones.
- **Moral complexity of innovation and market power** - As companies grow in influence and value, their innovations may disrupt other industries, leading to job loss or social backlash. While sometimes justified in capitalist terms, the ethical line becomes murkier when dominance is maintained through questionable means.

Feature Engineering

In this part of the course, we focus on **feature engineering**, a critical area where interviewers differentiate between average and exceptional ML candidates. This is our opportunity to show not just technical skill, but creativity and judgment.

- **Mediocre feature engineering** relies on basic, mechanical steps—like one-hot encoding categoricals or normalizing numericals—without much customization.
- **Stellar candidates go further**, creating new features from raw data (e.g., extracting time-of-day from timestamps, or combining variables into meaningful interactions).
- We show thoughtfulness by **dropping irrelevant features**, checking for **multicollinearity**, and aligning features closely with the problem's objectives.
- We demonstrate versatility by handling **complex data types**—such as transforming freeform text, working with embeddings, or aggregating time series effectively.
- Ultimately, we recognize that **feature engineering can matter more than the model itself**, and our job is to shape the data so that the model can truly learn from it.

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

Amazon Behavioral Interview [Part 31] - Missing A Commitment (Answer)

This video segment describes a situation where the interviewee failed to meet a commitment during their time at Google.

- **The Commitment:** The interviewee committed to flawless execution of a major advertising campaign during the Super Bowl, ensuring all ads ran smoothly across all platforms.

- **The Obstacle:** Despite thorough planning and preparation, a critical ad failed to run on Mac computers due to a software bug.

- **The Impact:** This failure resulted in significant disruption, including:

  - **Lost revenue:** The ad in question was a high-value advertisement.
  - **Damaged reputation:** The incident could have negatively impacted Google's reputation with advertisers.
  - **Increased stress:** The interviewee experienced significant stress due to the unexpected issue and the pressure to resolve it quickly.

- **Corrective Actions:**

  - **Root Cause Analysis:** The team conducted a post-mortem analysis to identify the root causes of the failure, including inadequate testing on all devices and insufficient escalation procedures for technical issues.
  - **Process Improvements:**
    - Implemented a more comprehensive testing process to ensure compatibility across all devices and browsers.
    - Established a clear escalation path for technical issues, including multiple levels of support and on-call engineers.
  - **Improved Communication:** Enhanced communication protocols to ensure timely identification and resolution of technical issues.

- **Key Learnings:**

  - The importance of thorough planning and rigorous testing.
  - The need for robust contingency plans to address unexpected challenges.
  - The importance of effective communication and collaboration within and across teams.
  - The value of learning from mistakes and using them to improve future performance.

This example demonstrates the interviewee's ability to: *Acknowledge and take responsibility for their mistakes.* Conduct a thorough root cause analysis to identify areas for improvement. *Implement corrective actions to prevent similar issues from occurring in the future.* Demonstrate resilience and the ability to learn from challenging situations.

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

Become An Engineer Influencer [Part 8] - Bottom-Funnel Channels

Build Up Relationships

We highlight why building strong relationships and social capital is essential for career resilience, especially during layoffs. Here are the core points from the lesson:

- Relationships are a form of social capital, and having people who know you, like you, and will advocate for you can directly influence whether you survive layoffs or get new opportunities.
- Engineers often underinvest in relationship-building by staying heads-down, but proactively connecting with managers, skips, and peers across teams is increasingly important in today’s economy.
- Building relationships doesn’t require forced networking—it can happen naturally through code reviews, coffee chats, offsites, and one-on-ones if you are intentional about seeking opportunities.
- No matter how senior or skilled you are, everyone is expendable, so you should never rely on company loyalty alone and should continuously invest in relationships that outlast any single job.

Amazon Behavioral Interview [Part 25] - Working Outside Of Your Domain (Answer)

This video segment describes a situation where the interviewee took on a project outside their core responsibilities to improve employee engagement at Google.

- **Identified a Problem:** The interviewee noticed that employee engagement scores were low, particularly regarding the perception of fair and transparent promotions.
- **Took Initiative:** The interviewee proactively identified this issue and proposed a solution: creating an anonymous feedback system to gather data on employee perceptions of promotion fairness.
- **Implemented a Solution:** The interviewee worked with HR to develop and implement the "Perfolution" system, which collected anonymous feedback from employees on promotion decisions.
- **Achieved Positive Results:** The system successfully gathered valuable data, which was then used to identify areas for improvement in promotion processes. This resulted in a significant improvement in employee engagement scores related to promotion fairness.
- **Demonstrated Initiative and Collaboration:** This example demonstrates the interviewee's initiative, problem-solving skills, and ability to collaborate effectively with other teams (HR) to achieve a positive impact.

This example effectively demonstrates the interviewee's: 

- ***Proactive approach:*** *Identifying a critical issue and taking the initiative to address it.* 
- **Problem-solving skills:** Developing and implementing a creative solution to gather data and identify areas for improvement. 
- ***Collaboration and teamwork:*** *Effectively collaborating with HR to implement the solution and address the identified issues.* 
- **Focus on employee engagement:** Demonstrating a commitment to improving employee satisfaction and well-being. 
- **Ability to drive positive change:** Successfully implementing the solution and achieving a significant improvement in employee engagement scores.

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

How Managers Hire Great Engineers [Part 19] - Speed

Great engineers don't stay on the market for a long time. From this lesson, you will:

- Understand that reducing the time from initial contact to offer acceptance can significantly improve your chances of closing a candidate
- Learn that a faster process can position your company advantageously against competitors who may have longer hiring cycles
- Discover how streamlining your recruitment process to make decisions quicker can prevent candidates from pursuing or waiting for other offers

Connect with John Egan on LinkedIn: <https://www.linkedin.com/in/jwegan/>

How To Crack Any Interview

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>

To ace any Engineering Manager (EM) interview, we need to go beyond memorized answers and demonstrate a deep, tailored understanding of the role, the company, and the people interviewing us. This final video recap ties together the core strategies we've learned throughout the course.

- **Deeply Understand the Role and the Interviewer**

  - We should thoroughly research the company's culture, the team’s business priorities, and even the interviewer’s background if possible.
  - This helps us anticipate questions and articulate the team’s pain points—making us stand out as someone who already thinks like an insider.

- **Focus on the Intent Behind the Questions**

  - Every question has an underlying purpose. We must listen for the *question behind the question* to understand what trait or leadership ability is being evaluated.
  - Once we’ve identified this, we lead our response with our **engineering management systems** and **leadership philosophies** to show intentionality and maturity.

- **Build and Customize Our Story Bank**

  - We should prepare core EM stories that demonstrate a range of leadership abilities and adverse situations.
  - The goal isn’t perfection but authenticity—sharing how we made decisions, what we learned, and how we’ve grown as a result.

- **Showcase Growth Through Adversity**

  - Most interview questions center around difficult moments. We should use these opportunities to demonstrate emotional maturity, resilience, and our ability to evolve—crucial traits for a leader.

- **Be Convincing and Confident**

  - At the end of the day, we’re not just answering questions—we’re telling a story about why we’re the best fit. We need to sell our value clearly and confidently, grounded in real experience and reflection.

Maximize Your Equity And Benefits In Tech [Part 23] - Conclusion

Congratulations on making it to the end of this course! Here are core points from the lesson:

- Know the details of your equity, 401k, and ESPP plans, and set calendar reminders for things like stock option expirations, enrollment windows, and rollover opportunities
- Automate what you can only after understanding your holdings—review RSU tax withholdings, grant docs, and whether you’re using pre-tax vs. Roth intentionally
- Explore advanced options like mega backdoor Roths if your 401k allows them, and ensure you're not missing out on your employer match or other benefits
- Review your health plan and associated perks like HSAs, FSAs, and wellness stipends, and use reminders to avoid letting free money go to waste

If you want to get additional support from Andy:

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

Amazon Behavioral Interview [Part 30] - Building Trust With Stakeholders (Evaluation)

This video segment discusses the quality of an interview conducted by a person named Alan.

- **The Interviewer's Approach:**

  - **Unclear Questioning:** Alan initially asked a general question about building trust, which is not a typical behavioral interview question.
  - **Unnecessary Detour:** This initial question led to a lengthy discussion that was not directly relevant to assessing the interviewee's skills or experiences.
  - **Awkward Transition:** Alan then abruptly shifted to a more relevant question about a time the interviewee failed to meet a commitment, but the transition felt awkward and disjointed.

- **Concerns about Interview Quality:**

  - **Lack of Clear Focus:** The interviewer's approach seemed unstructured and lacked a clear focus on assessing the interviewee's skills and experiences.
  - **Potential for Bias:** The interviewer's personal style and communication approach could potentially bias the interview outcome, particularly for interviewees who are less experienced or less comfortable with unexpected questioning.
  - **Limited Quality Control:** The video highlights a concern about the lack of quality control for interviewer performance and the potential impact on interview outcomes.

- **Recommendations:**

  - **Focus on Clear and Relevant Questions:** Interviewers should focus on asking clear, concise, and relevant behavioral questions that directly assess the candidate's skills and experiences.
  - **Maintain a Structured Approach:** A structured interview approach helps ensure that all candidates are evaluated fairly and consistently.
  - **Improve Interviewer Training:** Investing in interviewer training programs can help to improve the quality of interviews and ensure that all interviewers are equipped with the necessary skills and knowledge to conduct effective and unbiased interviews.

This analysis highlights the importance of conducting high-quality interviews to ensure fair and accurate assessments of candidate qualifications.

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

The Story Behind Component Script

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, reflects on one of the most ambitious—and ultimately unsuccessful—projects of his career: **ComponentScript**, a cross-platform UI framework designed to unify iOS and Android development. Although the framework was technically sophisticated and solved many engineering challenges, it failed to gain widespread adoption. Adam shares the key lessons he learned about product strategy, developer adoption, and why technical excellence alone is not enough to ensure success.

- **Technical Success Doesn't Guarantee Product Success:** ComponentScript delivered strong technical capabilities—including type safety, seamless integration with native frameworks, and bidirectional interoperability—but these strengths were not enough to drive widespread adoption.
- **Know Your Users and Focus Your Strategy:** One of the project's biggest shortcomings was failing to identify a clear target audience. By trying to appeal to both native mobile engineers and JavaScript developers, the framework ultimately resonated with neither. Adam also learned the importance of concentrating efforts on winning over a single committed team before attempting broad adoption.
- **Embrace Failure as a Learning Opportunity:** Adam openly documented ComponentScript's failure through a detailed postmortem, using the experience to share hard-earned lessons with the engineering community. His reflection highlights the value of transparency, continuous learning, and recognizing that successful engineering requires balancing technical excellence with usability, adoption, and organizational alignment.

Original podcast link: [**https://www.youtube.com/watch?v=YA_OYJF3Mmw**](https://www.youtube.com/watch?v=YA_OYJF3Mmw)

Your Rating Should Never Be A Surprise

In this lesson, we explain why your performance rating should *never* be a negative surprise and how maintaining transparent, ongoing conversations with your EM prevents career-derailing outcomes.

- We emphasize that if you expect “meets” and end up on a PIP, something has gone catastrophically wrong—and it’s almost always preventable through proactive communication.
- We recommend regularly asking for a *hypothetical rating* (“If you had to rate me today, what would it be?”) while explicitly acknowledging it’s not a guarantee—this makes managers comfortable giving candid signals.
- We highlight that good managers are usually 80–90% accurate with these hypothetical ratings, giving you strong insight into where you truly stand.
- We note that engineers who avoid this conversation out of discomfort effectively “walk themselves off a cliff” by choosing to stay in the dark.
- We reinforce that building trust through vulnerability, consistency, and strong 1:1 habits unlocks your manager’s willingness to give honest performance signals—ensuring you’re never blindsided.

How Managers Hire Great Engineers [Part 16] - Follow Up

If at first you don't succeed, try try again. From this lesson, you will:

- Learn the impact of follow-up emails, which can significantly enhance response rates when sent in addition to an initial email
- Discover tools like Mixmax and features within ATS systems like Ashby that can automate the follow-up process and track email openings
- Understand the strategy of escalating outreach, involving higher levels of management, to engage high-value candidates effectively

Connect with John Egan on LinkedIn: <https://www.linkedin.com/in/jwegan/>

Be Deliberate With Team Selection

We explain how team selection within a company can influence both career growth and layoff risk, while stressing the importance of balance and personal fit.

- Team choice is one of the remaining factors within your control, and teams that are important to leadership or closely tied to core revenue are generally less likely to be cut.
- Importance is relative to executive priorities, not just revenue, so understanding what leadership truly cares about is key, especially at companies with strong founder influence.
- Choosing a high-priority team is usually good career advice anyway, since those teams tend to have more scope, visibility, and growth opportunities.
- You should not sacrifice genuine interest or passion just to chase perceived safety, because lack of engagement hurts performance and long-term career growth.
- This guidance is clearer at companies with product-market fit, while earlier-stage startups carry more inherent uncertainty, making stability harder to assess regardless of team choice.

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.