Maximize Your Equity And Benefits In Tech [Part 21] - Bottom Line

There are a few essential things to keep in mind when managing retirement accounts. Here are the core points from the lesson:

- 401(k)s are effective for automating savings and deferring taxes, especially in high tax brackets, and it's important to capture the employer match and invest contributions
- Pre-tax vs. Roth decisions aren’t one-size-fits-all, but choosing wisely can reduce your lifetime tax bill with the help of smart withdrawal strategies
- Mega backdoor Roths allow large tax-free contributions if your plan supports them, while backdoor Roths offer smaller contributions with more complexity and caution required

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

Become An Engineer Influencer [Part 21] - Networking

Grow Fundamental Skills

We explain why growing fundamental, transferable skills is one of the most powerful ways to reduce layoff risk and strengthen long-term career resilience. Here are the core points from the lesson:

- There is far more to software engineering than coding, especially at scale, where communication, project management, leadership, and relationship-building determine whether work actually ships.
- Over-indexing on a specific technology, language, or product is risky, because teams, systems, and entire products can disappear, while transferable skills allow you to move across teams or companies.
- Engineers who can clearly design systems, think through edge cases, write thoughtful plans, and communicate tradeoffs create outsized impact compared to those who jump straight into code.
- So-called “soft skills” are actually the highest-leverage skills, because they compound across roles, companies, and industries, while technical tools and frameworks inevitably change.
- Focusing your time on high-leverage problems and influence, rather than low-level tooling details, is what drives career growth, adaptability, and durability during periods of layoffs.

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.

Round Structure ML Algorithm

In this section, we dive into what makes the **ML algorithm coding interview** distinct from traditional coding rounds. It’s a focused, high-pressure test of both our theoretical depth and practical coding ability.

- We’ll be asked to **implement ML algorithms from scratch**—no scikit-learn, no TensorFlow—just raw code.
- This round tests both our **understanding of the algorithm’s inner workings** and our ability to **code it cleanly and efficiently**.
- With only **45–60 minutes**, we’re expected to focus on **core logic and code structure**, not perfection or full library-level implementations.
- The scope is typically **limited to common algorithms** like linear regression, logistic regression, or k-means—so it's highly trainable.
- With preparation, we can excel by knowing the **key steps, math, and edge cases** behind each algorithm and practicing how to express them in code.

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

Before The Meeting

In this lesson, we dig into how to prepare for 1:1s so they’re consistently high-value and how thoughtful prep not only improves the conversation but also prevents cancellations and protects our time.

- We advise seeding the 1:1 agenda at least 24 hours in advance so our EM can “pre-compute”—arriving prepared instead of reacting on the spot to complex issues.
- We recommend prioritizing agenda items, putting critical topics first in case time runs short, and leaving lower-priority items for follow-up on Slack if needed.
- We highlight that surprising a manager with heavy topics during the meeting leads to wasted time and weaker guidance, whereas advance notice empowers them to think deeply and respond effectively.
- We explain that sending a thoughtful agenda also makes it harder for the manager to cancel or move the meeting, since it clearly shows we’ve invested effort and have meaningful topics ready.
- We reinforce that consistent preparation creates smoother, more productive discussions and helps us extract maximum value from the limited 30 minutes we have each week.

[Paper Reading] Netflix : Query Facet Mapping and its Applications in Streaming Services

Led by [Dharin Shah](https://www.linkedin.com/in/dharinshah/)

For a Taro Premium discount from Dharin, use his referral link here: <https://www.jointaro.com/r/dharins694/>

This deep-dive goes through how Netflix built their internal query to facet mapping layer to have better understand intent of the query. For example - matching 'anim' to 'Demon Slayer' as higher rank than perhaps 'animal planet'. In this session we dive into the white paper released by Netflix around their implementation.

Link to Paper: [**https://dl.acm.org/doi/pdf/10.1145/3477495.3536330**](https://dl.acm.org/doi/pdf/10.1145/3477495.3536330)

Become An Engineer Influencer [Part 23] - Coaching

Mock Interviews Are Non-Negotiable

To wrap up our preparation strategy, we dive into how to *structure* our prep effectively—because randomly studying “a bit of everything” doesn’t work.

- **Mock interviews are non-negotiable**: They’re the fastest way to sharpen your skills, build confidence, and improve how you communicate under pressure.
- **Avoid practicing in real interviews**: We should use mocks to make mistakes and learn, not high-stakes opportunities.
- **Find partners in your network or online**: Leverage communities or platforms like ADP List to schedule mock sessions with others.
- **Record your mocks**: Watching ourselves afterward reveals blind spots we may not notice in the moment—this step alone can lead to major improvements.

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

Senior Managers Adam Admires

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, reflects on the engineers he most admires throughout his career and the qualities that set them apart. Rather than attributing success to a single skill, Adam highlights how exceptional engineers excel in different ways—from writing code and debugging complex systems to communicating ideas, launching new initiatives, and aligning teams. He emphasizes that there is no single blueprint for becoming a high-impact Individual Contributor.

- **Exceptional Engineers Have Different Superpowers:** Adam highlights colleagues who excel in distinct areas, including high-volume coding, deep debugging, launching ambitious projects, technical communication, and organizational alignment. There is no single path to becoming an outstanding engineer.
- **Leverage Your Strengths While Appreciating Others':** Adam recognizes that his own strengths lie in hands-on engineering, while others surpass him in areas such as cross-team leadership, strategic communication, and stakeholder management. Great engineering organizations thrive because individuals bring complementary skills.
- **Learn from Role Models, Not Copies:** Rather than trying to emulate one person completely, Adam encourages engineers to study the specific qualities they admire in others—whether it's technical depth, problem-solving, writing, or leadership—and incorporate those strengths into their own unique career path.

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

Thoughts On Management

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, explains why he chose to remain on the **Individual Contributor (IC)** career path instead of transitioning into engineering management. He discusses how understanding his strengths, interests, and motivations helped shape his career, why deep technical expertise can be more valuable than constantly switching domains, and how long-term specialization enabled him to become a trusted expert within Meta's mobile engineering organization.

- **Know What Motivates You:** Adam chose to remain an Individual Contributor because his greatest passion is writing code and solving technical problems. He recognized that management requires a different skill set—such as organizational leadership, direction setting, and people management—that did not align with his strengths or interests.
- **Build Deep Expertise Over Constant Change:** Rather than frequently changing teams or technologies, Adam stayed within mobile engineering, allowing him to develop deep institutional knowledge and become an expert in the architecture, tooling, and infrastructure that powered Meta's iOS ecosystem.
- **Career Paths Should Match Your Strengths:** Adam emphasizes that there is no universally "correct" career path. While some engineers thrive by exploring new domains such as AI or AR/VR, others create greater impact by mastering a specific area. The key is aligning your career choices with the type of work you genuinely enjoy and excel at.

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

Become An Engineer Influencer [Part 15] - Headline/Preview Testing

How To Handle a Failed Project

In this lesson, **Adam Ernst**, Software Engineer at **Meta**, reflects on the difficult decision to end **ComponentScript** after realizing it was not achieving the impact it was designed for. He discusses how performance reviews provided honest feedback, why responsibly shutting down a project can strengthen rather than damage your reputation, and the importance of recognizing when persistence becomes counterproductive. Adam offers valuable advice for engineers navigating ambitious projects that may not succeed.

- **Performance Reviews Should Inform, Not Define You:** Receiving a "Meets Most" performance rating helped Adam recognize that ComponentScript was no longer delivering the expected impact. Rather than viewing the feedback as a failure, he used it as a signal to reassess the project's direction.
- **End Projects Responsibly:** Instead of abandoning ComponentScript, Adam personally helped teams migrate to alternative solutions, removed the framework entirely from the codebase, and documented the lessons learned. Taking ownership of the cleanup earned trust and demonstrated strong engineering leadership.
- **Listen to Early Warning Signs:** Looking back, Adam realized he had sensed for nearly a year that the project was losing momentum. His instinct was to write more code in hopes of turning things around, but he later learned that recognizing when to pivot—or stop altogether—is just as important as technical execution.

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

Be Vulnerable

In this lesson, we highlight the importance of vulnerability in building a strong, supportive relationship with an engineering manager—because they can only help us if they understand what we’re going through.

- We stress that EMs can’t read minds; if we’re struggling, whether with a teammate, a project, or something personal, we should tell them so they can protect our well-being at work.
- We explain that good managers act like part-time therapists, and sharing when things are rough allows them to adjust workload, mediate conflicts, or at least offer support.
- We note that vulnerability builds trust, just like in friendships outside of work, and that trust significantly improves how effectively we collaborate.
- We clarify that we shouldn’t overshare, but we also shouldn’t hide everything—sharing selectively helps EMs understand who we are and how to help.
- We reinforce that showing vulnerability increases the “trust meter,” strengthens the partnership, and ultimately unlocks more powerful support from our EM.

Model Training

In this segment, we cover **model training**, a phase where many candidates fall into autopilot. To stand out, we need to show thoughtfulness, adaptability, and a clear connection between our choices and the problem at hand.

- **Mediocre performance** involves picking a default model (e.g., logistic regression or random forest), using out-of-the-box settings with no tuning or justification.
- **Strong candidates** choose models deliberately, explaining how their selection fits the **data characteristics, business goals, or system constraints**.
- We improve performance through **hyperparameter tuning**, using techniques like grid search or informed manual adjustments based on EDA insights.
- When appropriate, we apply **ensemble methods** (e.g., boosting, bagging, stacking) to push performance further.
- Most importantly, we demonstrate that our modeling choices are **intentional and grounded in context**, not just rote or random experimentation.

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

Maximize Your Equity And Benefits In Tech [Part 14] - Stock Option Special Tax Considerations

When working at an early-stage startup, certain tax strategies can unlock major financial advantages—if you plan ahead. Here are the core points from the lesson:

- Qualified Small Business Stock (QSBS) can allow up to $10 million or 10x your basis in tax-free capital gains if you meet specific conditions, like holding actual shares for five years and your company having under $50M in assets at grant
- Early exercise and filing an 83(b) election can start the QSBS clock early and lock in low tax values, but they come with financial commitment and risk if you leave before fully vesting
- The 83(b) election must be filed within 30 days of exercising options and doesn't accelerate the two-year holding clock required for qualified ISOs
- Only $100K worth of ISOs can vest annually for favorable tax treatment—going above that limit risks converting some to NSOs with different tax implications

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

Amazon Behavioral Interview [Part 20] - Taking An Unpopular Stance (Evaluation)

This video segment provides feedback on an individual's response to a behavioral interview question about a time when they took an unpopular stance.

- **Identified Shortcomings:** The feedback highlights that the interviewee's response, while demonstrating a willingness to disagree with leadership, may not be perceived favorably in an Amazon interview setting.
- **Amazon's "Backbone" Culture:** The feedback emphasizes the importance of the "backbone" principle at Amazon, which values individuals who not only express their opinions but also actively contribute to the success of the chosen course of action, even if it differs from their initial recommendation.
- **Alternative Approach:** The feedback suggests that a more effective response would have focused on how the interviewee, despite the initial disagreement, actively contributed to the success of the chosen strategy. This could include:
  - Emphasizing their commitment to implementing the decision effectively.
  - Describing how they provided valuable input and insights to improve the chosen approach.
  - Highlighting their contributions to mitigating potential challenges and ensuring the successful execution of the strategy.
- **Importance of Demonstrating Commitment:** The feedback emphasizes that Amazon values individuals who are not only willing to express their opinions but also demonstrate a strong commitment to the success of the team and the organization, regardless of whether their initial recommendations are adopted.

This analysis provides valuable insights into the expectations and values of Amazon's interview process, particularly regarding the "backbone" principle and the importance of demonstrating commitment and a collaborative approach.

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

Finding Scope To Grow

We walk through how to evaluate whether a team offers real *scope for growth*—one of the most important factors for long-term career progression.

Here are the core points from the lesson:

- We suggest assessing a team’s track record of major launches: frequent, meaningful wins signal room for impactful work, while long dry spells often indicate a team that is either too new (unstable) or too mature (no hard problems left to solve).
- We point out that very mature orgs like core Facebook Feed may be so optimized that it’s nearly impossible to produce meaningful results, making promotions extremely difficult; meanwhile, very new orgs offer big scope but come with chaos and uncertainty.
- We recommend examining the level distribution on the team: a healthy mix of engineers more senior *and* more junior than you enables both mentorship (learning) and leadership (scope creation), whereas being the most junior or most senior can severely limit growth.
- We advise deeply evaluating the engineering manager’s track record—whether they have successfully grown people from junior → mid-level → senior → staff—because a strong EM accelerates your development, while a newly minted or unproven EM introduces career risk.

Project Presentation

Some companies include a **project presentation round** in their ML interview process, where we’re expected to walk interviewers through a real project from start to finish. This is a powerful opportunity to showcase our end-to-end technical skills, communication ability, and strategic thinking.

- **Use visuals** to anchor the conversation—simple diagrams in Excalidraw or Google Docs help explain architecture clearly and keep interviewers engaged.
- **Explain concepts like you’re teaching a junior engineer**, avoiding jargon and offering quick context before diving into complex ideas (e.g., why negative sampling is needed).
- **Stay composed during interruptions**, as these are often tests of our communication clarity rather than signs of concern.
- **Show real trade-off thinking**—don’t just name-drop methods; explain *why* one approach was selected over others based on constraints like latency or scalability.

This round is about more than technical depth—it’s about demonstrating that we can **lead projects, make informed decisions, and communicate them with confidence and clarity**.

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

How Do I Talk Without Sounding Chaotic?

In this lesson we talk about how to communicate effectively during an AI-assisted coding interview without sounding scattered, frantic, or going completely silent.

- **Avoid the two extremes** — narrating every single keystroke comes across as junior, while going silent for several minutes leaves the interviewer in the dark; the goal is to sound controlled and intentional somewhere in between.
- **Choose the communication model that fits your thinking style** — Model A is light, continuous commentary as you work ("I'm pulling the date out of each event to populate the per-day set"), while Model B is stating your high-level intent upfront, working silently for 60–90 seconds, then summarizing what you did before repeating the cycle.
- **Practice talking while you work before the interview** — like touch typing, verbalizing your thought process while solving a problem is a skill that needs to be rehearsed, not figured out on the spot; a few mock sessions with a friend or mentor can make a significant difference.

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.