Maximize Your Equity And Benefits In Tech [Part 10] - Strategy (ESPP)

ESPPs can offer significant value, but deciding when to sell requires more nuance than it may seem at first glance. Here are the core points from the lesson:

- If there’s no holding period requirement, selling immediately after purchase can yield guaranteed gains, especially with discounts and lookback provisions
- Holding ESPP shares introduces market risk and complexity, and your decision should reflect whether you’d buy the stock outright if given the equivalent in cash
- A holding period aligned with qualified disposition rules may offer better tax treatment—but not always; in some cases, a disqualifying disposition results in lower overall tax
- When stock declines during the offering but rebounds before sale, the tax owed under a qualified disposition may be higher due to how ordinary income is calculated from the offering price rather than purchase price

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

Taro Book Club: Designing Data Intensive Applications - Chapter 8 (Distributed Systems)

Topic: Chapter 8 - The Trouble with Distributed Systems

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

Here's the agenda:

- We’ll break down and discuss the key concepts from Chapter 8.
- 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. *If you don't have the book or want more details on how this all works, check out the #taro-bookclub channel in the Taro Premium Slack as well!*

Get ready for another engaging and informative session!

What Does An Engineering Manager Actually Do?

In order to work together optimally with your engineering manager (EMs), you should have a great understanding of their perspective and incentives.

Here are the core points from the video:
- **Engineering managers shouldn't do technical work** - They need to influence the code of the team without writing it, reviewing it, or designing it. This is an extremely hard job.
- **So what specifically do EMs do?** - Ultimately the EM's goal is to make the team land impact, and this can manifest in many different ways (some of which engineers don't want to hear about). If you are a good performer, it's in the manager's best interest to foster your talent and grow you. If you aren't (i.e. you're dragging the team down), it's possible the manager believes firing you to be the best choice for the team. Outside of managing performance, there are tasks like removing non-technical blockers and making people work better together that EMs do to keep the impact engine going.

Related resources:
- [[Taro Top 10] Software Engineer To Engineering Manager (IC -> M Track)](https://www.jointaro.com/playlist/oz0mnJvHHgM8NfVF7rgp/)
- [[Masterclass] What Software Engineers Should Look For In Their Engineering Manager](https://www.jointaro.com/lesson/oeY7ncZhzJ5NO6dij5e7/masterclass-what-software-engineers-should-look-for-in-their-engineering-manager/)

SWE Internship Survival Guide [Part 18] - Plot Your Growth Trajectory

Wrapping up all the advice and strategies into something actionable can feel overwhelming—so this video offers a clear, week-by-week roadmap to help you stay on track throughout your internship. Here are the core points from the lesson:

- **Weeks 1–2**: Embrace your newbie status—ask lots of questions, explore the codebase, and focus on learning, even if it means breaking things (safely)
- **Weeks 3–4**: You should start contributing code more regularly, with fewer basic mistakes in PRs, and begin transitioning from onboarding tasks to your main project
- **Weeks 5–7**: You’re gaining confidence—PR feedback is more meaningful, your code is smoother, and a midpoint check-in should help confirm you’re on track
- **Weeks 7–10**: You’re hitting your stride—code velocity and quality are high, you’re asking sharper questions, and maybe even helping others on the team
- **Weeks 11–12**: Finalize your project, document it, reconnect with your network, and take a moment to enjoy the end of a hard-earned, productive summer

How Managers Hire Great Engineers [Part 20] - Tips For Interviewing

It's critical as a hiring manager to make sure that an engineer candidate is the right fit during the interview. From this lesson, you will:

- Learn to avoid hypothetical questions in favor of inquiries about concrete experiences to gain accurate insights into a candidate's actual work behavior
- Understand the importance of building rapport and appearing friendly throughout the interview process, as candidates are also evaluating their fit with the team
- Discover the value of maintaining a curious mindset, encouraging thorough exploration of a candidate's responses, especially when initial impressions may suggest a red flag

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

Become An Engineer Influencer [Part 5] - Top-Funnel Channels

Stability

Even amid recent waves of layoffs, Big Tech companies continue to offer more job stability than most others in the tech industry. This stability is driven by several structural advantages, not just current economic conditions.

- **Layoffs in Big Tech are more reactive, less  routine**: Unlike smaller companies or traditional enterprises that cut staff regularly every 1–2 years, Big Tech companies like Google and Facebook went over a decade without mass layoffs. Their recent cuts were responses to extreme macroeconomic shifts, not standard operating procedure.
- **Higher baseline of job security**: Statistically, it’s harder to lose a job at a Big Tech company, especially when compared to \~80–90% of other tech firms. That said, consistent performance is expected to maintain that security.
- **Stability comes from product-market fit**: These companies have already achieved PMF with multiple products—Google, Meta, Airbnb, etc.—which ensures reliable revenue and customer demand. This reduces existential risk compared to early-stage startups.
- **Strong financials provide a cushion**: Many Big Tech firms operate some of the most profitable business models in history, particularly in digital ads and cloud infrastructure. Their massive cash reserves and consistent profit margins further insulate them from financial instability.
- **Comparison with startups is stark**: Companies still seeking product-market fit or surviving on runway from funding rounds face constant pressure to cut costs, making layoffs more common and less predictable.

What Should I Do In The First 10 Minutes?

In this lesson we talk about how to strategically approach the first 10 minutes of an AI-assisted coding interview to set yourself up for success.

- **Resist the urge to dive in immediately** — instead of jumping straight into coding or prompting the AI, start by restating the problem in your own words and doing a strategic skim of the codebase to understand existing functionality and function signatures.
- **Uncover hidden requirements** — as you explore the code, actively look for things like bot user filtering, non-active event handling, or data normalization that may not have been spelled out in the prompt, and clarify these with your interviewer.
- **Turn requirements into tests early** — unlike traditional interviews, convert each discovered requirement into an executable test case upfront (using AI to help generate them if needed), since verifying AI-generated code is a core part of the assessment.

Amazon Behavioral Interview [Part 27] - Recovering From A Bad Decision (Answer)

This video segment describes a situation where the interviewee made a mistake in their role at American Express.

- **Identified the Mistake:** The interviewee implemented a new incentive system for customer care professionals that rewarded them for saving high-value customers while neglecting lower-value customers. This led to:

  - **Cherry-picking of customers:** Customer care professionals prioritized high-value customers, leading to long wait times for lower-value customers.
  - **Negative customer experience:** Long wait times resulted in poor customer satisfaction and potentially damaged brand reputation.
  - **Missed revenue opportunities:** Neglecting lower-value customers, particularly early-tenure customers, resulted in missed opportunities for future revenue growth.

- **Learned from the Mistake:** The interviewee learned the importance of:

  - **Considering all stakeholders:** Involving customer care professionals in the decision-making process.
  - **Thinking long-term:** Considering the long-term value of customers, not just their immediate spending.
  - **Gathering diverse perspectives:** Seeking input from former team members to identify potential pitfalls.

- **Implemented Corrective Actions:**

  - Revised the incentive system to account for customer lifetime value.
  - Implemented measures to improve call center response times and reduce wait times.
  - Developed a system to identify and address cases of long wait times for customers.

This example demonstrates the interviewee's: 

- ***Self-awareness:*** *Acknowledging and taking responsibility for their mistake.* 
- **Problem-solving skills:** Identifying the root cause of the issue and implementing corrective actions. 
- ***Learning agility:*** *Learning from the mistake and applying those learnings to future projects.* 
- **Focus on customer experience:** Prioritizing customer satisfaction and long-term customer relationships. 
- **Continuous improvement:** Continuously refining processes and seeking ways to improve performance.

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

Ship & Grow 500k+ User Side Projects [Part 18] - GitHub

95%+ of software engineers aren't getting nearly enough value from GitHub, which is a shame as they're already using it. This lesson teaches you:

- Why it's so easy to stand out on GitHub
- How GitHub is becoming more and more powerful as a traffic-driving mechanism
- How to quickly make an awesome README to greatly improve your repo's attractiveness
- What a terrible GitHub README looks like, explained with a fun example
- What great GitHub READMEs look like, explained with 2 examples
- The ingredients you should have for a compelling GitHub README

Here are the repos shared in the lesson:

- <https://github.com/tsenart/vegeta>
- <https://github.com/afollestad/material-dialogs>

Influence vs. Manipulation

In this lesson, we discuss how **effective influence requires preparation, emotional intelligence, and an understanding of the other person’s motivations**. Like planning the opening moves in a chess game, difficult conversations can benefit from thinking ahead about what you want to ask, when to ask it, and how the other person is likely to respond. But influence is not simply about technique—the same interpersonal skills can be used collaboratively or manipulatively, making it equally important to understand the motives of the people you’re dealing with.

- **Prepare your opening moves and choose your timing:** Think through how you’ll introduce an important request and choose a moment when the other person is receptive, while looking for common ground as the conversation develops.
- **Emotional control makes influence more effective:** Anger and criticism can undermine your message even when your underlying point is correct. Staying calm and understanding how the other person feels can significantly improve difficult conversations.
- **Understand the motives behind interpersonal skill:** Influence, politics, and manipulation can rely on similar skills—the difference often lies in how they’re used. Learn to recognize whether someone’s interests align with yours, negotiate when cooperation is possible, and protect yourself when working with people you don’t fully trust.

Original podcast link:[ https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s](https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s)

Become An Engineer Influencer [Part 10] - Story-Telling

You'll Learn Proper Engineering Skills

Working at Big Tech companies offers a unique opportunity to develop strong engineering foundations by being immersed in mature processes, robust tools, and a culture of high standards.

- **Access to top-tier engineers and tooling**: Employees are surrounded by highly skilled engineers and comprehensive internal tools that streamline development. Many of these tools address needs engineers didn’t even know they had until using them.
- **High-quality code review culture**: Rigorous code reviews from experienced peers serve as a fast-track for learning. Early feedback can be intense but leads to rapid growth in code quality, scalability awareness, and best practices.
- **Exposure to mature engineering systems**: Engineers learn the full lifecycle of software deployment with components like dogfooding, alpha/beta testing, stage rollouts, A/B testing, monitoring, and alerting, many of which are often missing or underdeveloped in smaller companies.
- **Longevity drives technical evolution**: Companies like Meta and Google have evolved with the industry, migrating through major tech stack changes over decades. This adaptability teaches engineers how to future-proof their systems and processes.
- **Cultural emphasis on continuous learning**: The engineering culture encourages innovation, resilience, and cross-pollination of ideas, making it ideal for those looking to grow as adaptable and forward-thinking software engineers.

Taking Things Further

In Part 4 of the course, we focus on how to **embed "thinking in deltas" as a daily leadership habit**. This final module emphasizes how to continuously spot and create positive, sustainable change as a manager—not just react to problems.

- **We build the habit by journaling our daily deltas**, capturing the tangible changes we influence, however small.
- **We use the journal to reframe how we think**, making it easier over time to spot opportunities for impact in individuals, teams, and systems.
- **We improve our mental well-being as managers** by recognizing our contributions and wins in a role where feedback loops are long and ambiguous.
- **We measure our success not just by outputs, but by meaningful changes we've catalyzed**—deltas we can point to as outcomes of our leadership.

Creating a daily "delta journal" isn’t just about reflection—it’s how we grow our impact and resilience as leaders.

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)

Maximize Your Equity And Benefits In Tech [Part 17] - 401(k) And IRA Basics

Understanding retirement accounts is essential for long-term financial planning. Here’s the core points from the lesson:

- 401(k)s allow automated payroll contributions (up to $23,500 in 2025 for those under 50), often include employer matching, and offer pre-tax or Roth contribution options
- Contributions reduce taxable income but are still subject to payroll taxes like Social Security and Medicare
- IRAs (individual retirement arrangements) are similar to 401(k)s but are personally managed, have lower contribution limits, and don’t include employer matching
- IRA contributions may be tax-deductible or Roth-eligible depending on your income, unlike 401(k)s which have no income-based restrictions for pre-tax contributions

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

Expert Secrets of Successful Big Tech Interviews

**Event description**

Join this special NEW session where I interview "Mr. X" –– a former Amazon Bar Raiser and current Head of Talent Acquisition at a top tech company that must remain nameless ;)

Together, we'll take you beyond the basic tips you already know and unveil **specific, winning strategies** that actually separate you from other candidates in competitive interviews.

If you have the job skills and a solid work history (but interviewing continues to be where you "fall down" in the job search) this event will be an absolute game-changer.

**After This Masterclass, You Will:**

- **Eliminate Blind Spots**

  - **You’re making mistakes every time you interview, that you don’t see, that cost you job offers. Get ready to hear what they are.**

- **Own Your Story**

  - **The winning candidates aren’t necessarily the most skilled––they have the best stories. Soon, YOU will be that candidate.**

- **Read Minds (Literally)**

  - **Hiring managers speak in code. What they say is often totally different from what they’re thinking. Now you’ll know the difference.**

If you need additional support with your job search, you can get coaching from Alan and Kadima Careers. Join with a discount here: [**https://signup.kadimacareers.com/mQBsDvu**](https://signup.kadimacareers.com/mQBsDvu)

Politics

As companies scale, politics become inevitable - Big Tech companies are no exception. While these environments offer great compensation and talent density, navigating organizational complexity and interpersonal dynamics becomes a critical part of engineering success.

- **Politics Are Inevitable in Large Orgs**: As tech companies grow, layers of leadership and cross-functional dependencies make decision-making complex. Engineers must often align with numerous stakeholders, especially when aiming for senior or staff roles.
- **Shipping Requires Consensus-Building**: Even seemingly minor changes can require significant internal negotiation. One example cited involved a six-month project to enlarge a button being blocked just before launch due to last-minute leadership disagreement.
- **People Over Code**: The technical work is often less challenging than influencing and winning over colleagues who may disagree or have competing priorities.
- **Burnout from Frustrated Efforts**: Senior engineers can burn out after investing months into initiatives that get shut down due to misaligned incentives or lack of political foresight.
- **Success Requires “Playing the Game”**: Engineers who are averse to navigating internal politics may struggle, especially in high-visibility roles. Building relationships proactively is often essential for seeing projects through.

Startup Employee To Startup Founder: What I Wish I Knew

From 2013 to 2023, Tongbo Huang worked as an engineer or manager at three high-growth companies: Pinterest, Chekr, and Amplitude.

After 10 years working in startups of various sizes, Tongo decided to start his own: [**Sidr Tax**](https://www.sidr.io/). In the past year, Sidr Tax has surpassed 6 figures of revenue and is growing rapidly.

In this talk, Tongbo will share:

- How he thought about taking funding (he previously went through Y Combinator) and why he decided to bootstrap for Sidr.
- How he ended up working on a tax startup and how Shopify is fueling his growth.
- The problem with founders today looking for "exciting" ideas.

Connect with Tongbo here: [**https://www.linkedin.com/in/tongbohuang/**](https://www.linkedin.com/in/tongbohuang/)

\[Taro Top 10\] Entrepreneurship And Tech Startups: <https://www.jointaro.com/playlist/ArtlSzF17v7cad1K6TJG/>

Become An Engineer Influencer [Part 14] - Tips on Writing

Just A Cog In The Machine

Although Big Tech offers compensation and prestige, the sheer scale of these organizations can lead engineers to feel like small cogs in an enormous machine. The work often becomes highly specialized and incremental, making it harder to find personal fulfillment or a sense of ownership.

- **Incremental Work Dominates**: Many engineers are tasked with refining already hyper-optimized features, such as tweaking a single call-to-action button on an ad format. This kind of work can feel repetitive and lacking in creative fulfillment.
- **Limited Ownership**: As teams grow larger, individual engineers may end up owning only a sliver of a product component—sometimes just one platform’s implementation of a single UI element.
- **Slower Innovation in Mature Products**: Legacy systems and products that have been around for over a decade (like Gmail) may offer fewer opportunities for impactful changes, making it harder to grow scope or gain recognition.
- **High Competition for Scope**: Even when surrounded by brilliant engineers, opportunities for meaningful ownership can be scarce. This leads to competition over small improvements and sometimes a struggle to stand out.
- **Pockets of Growth Still Exist**: Certain high-growth teams such as those working on newer initiatives like AI or experimental products can still offer dynamic, zero-to-one opportunities. Success often depends on finding and joining these pockets within the broader organization.

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.