Real Stock Options Example - Kosei (Acquired By Pinterest)

This final segment offers a real-world walkthrough of a startup stock option offer and breaks down the critical information employees need to assess the *true* value of such equity. It highlights how confusing option grants can be without proper context and the financial implications of exercising options.

- **Real Offer Letter Example:** The speaker received an offer of 62,000 options at a $0.14 strike price, totaling $8,750 to exercise. However, the true value of this offer depends entirely on factors not included in the letter, like company valuation and total shares outstanding.
- **Vesting and Exercising Mechanics:** Vesting followed the standard schedule—1-year cliff with monthly vesting afterward. Post-termination, many startups only give a 90-day window to exercise, which can be financially burdensome.
- **Liquidity and Risk Considerations:** Employees may lose out if they can't afford to exercise before leaving a startup. As a response, some companies began extending the exercise window up to 10 years, reducing financial pressure on departing employees.
- **Tax Strategy Tip:** Exercising early (if financially feasible) starts the clock on long-term capital gains, which can save 10–12% in taxes versus short-term treatment if exercised and sold after a liquidity event.
- **Most Common Mistake:** Employees often overvalue large share numbers without understanding what fraction of the company those shares represent. To assess an offer, it’s essential to ask:
  - *What percentage of the company do these shares represent?*

  - *What is the current fair market value versus the strike price?*

Without those answers, it's impossible to accurately evaluate the worth of a stock option grant.

Tips On Navigating RSUs

This video highlights the complexity of **RSUs (Restricted Stock Units)** in tech compensation, emphasizing how RSUs introduce elements of personal investing into salary evaluation. Understanding how stock fluctuations affect total pay and managing risk becomes crucial.

- **Evaluating RSUs is similar to investing**, since compensation becomes tied to the company's stock performance. Joining when stock prices are low can lead to significantly higher gains if the stock appreciates.
- **Choosing a company means essentially “buying” into its future**, since RSUs form a large part of total compensation. A rising stock price increases income; a falling one diminishes it.
- **There is no universal rule for managing RSUs**, as financial goals and risk tolerance vary by individual. Compensation strategies should reflect personal financial context.
- **Some employees choose to sell RSUs immediately upon vesting**, aiming to diversify rather than concentrate risk. This reduces financial dependency on a single company’s performance.
- **Investing RSU proceeds into diversified assets like S&P 500 index funds** is a common approach for those seeking more stability and reduced exposure to employer stock.

The Power Of Big Tech: Meta Interns Can Get $100k+ Signing Bonuses

Compensation is not talked about enough, leading to huge differences in awareness and feedback for different groups of people. This is a snippet from the full masterclass session about [Understanding And Optimizing Your Pay In Tech](https://www.jointaro.com/lesson/gk408yBIV2fa5RjVR213/masterclass-understanding-and-optimizing-your-pay-in-tech/).

Some companies offer massive signing bonuses for interns that convert over to full-time. In the early 2010s, Facebook (not Meta) paid return interns a $75,000 signing bonus. For top interns (or those who negotiated), they received a $125,000 signing bonus.

For a new grad engineer who might be 21 or 22 years old, **this is a huge amount of money**. It can be difficult to turn that down. But the more important consideration is the overall total compensation (TC) calculation. Total compensation should be computed over a 4 year window since companies typically give out equity grants over 4 years.

For Rahul's full compensation breakdown of the 5 offers he received as a new grad, watch this video: [5 Offers w/ FAANG Companies As A New Grad: Details + Lessons](https://www.jointaro.com/lesson/4MBOiqWEMbCTCcLPjisz/5-offers-w-faang-companies-as-a-new-grad-details-lessons/)

Why Engineers Can't Ignore Politics

In this lesson, [Ryan Peterman](https://www.linkedin.com/in/ryanlpeterman/) discusses the realities of senior leadership and management in the tech industry through the perspective of [**Ethan Evans**](https://www.linkedin.com/in/ethanevansvp/), a former Amazon VP. Building on a previous conversation known for its unusual transparency, this lesson sets the stage for a candid look at what happens behind the scenes at the highest levels of technology companies—including organizational decisions, reorgs, and management practices that engineers and managers rarely get to see.

- **A transparent look at senior tech leadership:** Gain insight into what happens behind the scenes at the VP and executive levels of major technology companies.
- **Lessons from both successes and mistakes:** Explore leadership experiences with an emphasis on openly examining decisions, including things the speaker would approach differently in hindsight.
- **Understanding how organizations really operate:** Set the foundation for a deeper discussion of reorgs, management decisions, and other internal dynamics that affect both engineers and managers.

Original podcast link: <https://www.youtube.com/watch?v=6WaeGfLnRvc&t=24s>

Becoming Senior Staff IC7 at Microsoft

In this lesson, Philip reflects on his rapid career progression at Microsoft and the factors he believes contributed most to his growth as an engineer. He discusses the value of working alongside exceptionally talented colleagues and mentors, deliberately accumulating experience early in your career, and the role that hard work can play in accelerating professional development.

- **Career growth is a combination of luck, talent, and hard work.** While some factors are outside your control, putting yourself in strong environments and learning from exceptional people can accelerate your development.
- **More experience can compress the learning curve.** Taking on a high volume of meaningful work early in your career can expose you to situations and problems that might otherwise take years to encounter.
- **Hard work has diminishing returns—and real trade-offs.** Longer hours may increase total output and experience, but each additional hour can become less productive, and career acceleration can come at the expense of health, relationships, and balance.

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

How It Started with CosmicSoft

In this lesson, **Adam Ernst**, a software engineer at **Meta**, shares the remarkable story of how his journey into software development began long before his professional career. He reflects on founding **CosmicSoft**, a software company he started while still in middle school, where he built and sold an online testing application for teachers. Adam explains how beginner-friendly programming tools enabled him to create real software, how he sold his products online before modern payment platforms like Stripe existed, and the entrepreneurial lessons he learned from launching a business at such a young age.

- **A Passion for Programming Began Early:** Adam Ernst discovered his love for software development in middle school, using the programming language **Real Basic** to build an online testing application inspired by his mother's work as a teacher.
- **Launching CosmicSoft:** Adam successfully sold his software to customers around the world using early e-commerce tools, accepting both online credit card payments and mailed checks—an impressive entrepreneurial achievement for a middle school student.
- **Foundations of a Software Career:** Adam's experience highlights how curiosity, accessible development tools, and a willingness to solve real problems laid the foundation for the engineering career that eventually led him to Meta.

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

Putting It All In Perspective

This bonus session wraps up the *Essence of Management* course by reflecting on the symbolism behind the **Management Deltas** logo and what it teaches us about effective leadership. The logo—featuring a lowercase delta—serves as a metaphor for the kind of impact we aim to create as managers.

- **We focus on small changes**—daily and weekly deltas—that compound over time into meaningful, lasting transformation for our team, our impact, and our careers.
- **We recognize the multidimensional nature of management**, much like the mathematical partial derivative (∂), where influence happens across many axes—people, processes, priorities, and culture.
- **We look for deltas in every direction**, and one of our responsibilities is to map these dimensions so we can lead more intentionally and with greater clarity.
- **We embrace the idea that leadership is not one-size-fits-all**—it's a creative, ongoing practice of identifying leverage points and applying thoughtful, sustainable change.

This session reminds us that our job isn’t to be perfect—it’s to continuously look for small, deliberate ways to move our teams and organizations forward.

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)

Course Introduction

In this opening session, Gilad Noor introduces the Essence of Management course, outlining what we’ll learn, how it’s structured, and what to expect. The focus is on practical, actionable lessons that help us become better managers.

- We’ll explore one core management lesson across **four modules**, combining theory with hands-on exercises to build real-world skills.
- The course begins with a look at the **individual contributor role** to set the foundation, then shifts to the core question: *What is a manager’s job—really?*
- Later modules help us **practice and apply** what we learn, and then explore how to take our management capabilities even further.
- Gilad brings his experience as an engineering manager at Meta, Amazon, and a clean tech startup, along with his work coaching over 100 managers.
- The course is designed to be **accessible, practical, and growth-oriented**, helping us avoid common mistakes and accelerate our impact as managers.

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)

Conclusion

That’s it.

Not the end—just the moment you stop walking with a guide and start carrying the weight yourself.

You’ve got the tools. The stories. The bruises that come with learning anything real.

Now carry it forward.

Ownership doesn’t show up in the big speeches. It shows up in the quiet. In what you do when no one’s clapping. In what happens after the meeting ends.

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

You can’t force someone into ownership.

You don’t know how much someone is carrying.\
But you feel it when they stop moving.

This isn’t about accountability frameworks or “holding people to outcomes.”\
It’s about what shuts people down—and what might help them open back up.

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

Become A Debugging Master [Part 17] - Share The Learning

A lot of engineers move on immediately after landing a fix, but the best ones take the time to reflect and prevent similar issues in the future. Here are the core points from the lesson:

- Retrospectives help you identify root causes and system weaknesses so you can either prevent a future incident or make it much easier to detect and fix
- A good postmortem analyzes what went well and what didn’t across detection, notification, response, mitigation, and analysis, with detailed documentation to capture all learnings
- Writing a clean, detailed doc with screenshots and explanations makes it much easier for future engineers to learn from the incident without having to dig through chaotic logs or chat threads
- Big tech cultures like Facebook normalize failure and focus on minimizing damage and learning quickly, often using formal SEV reviews to improve systems and processes over time

Become A Debugging Master [Part 15] - Monitor System Health

Fixing a bug isn’t the end — true resolution means confirming the fix worked at scale. Here are the core points from the lesson:

- Always monitor system health after a fix using real metrics, not just local device testing, to verify the problem is truly resolved
- Track both user-facing metrics (like revenue, call minutes, login attempts) and code-facing metrics (like error rates, ingress/egress traffic, build failures)
- Be aware of natural variations in user metrics across days, weekends, and holidays so you don’t misinterpret normal fluctuations
- Revisit your original blast radius notes and make sure the impacted areas are reflected in your dashboards to fully validate recovery
- Understand the difference between root causes (e.g., spike in Firestore reads) and lagging indicators (e.g., billing costs) when monitoring your fix

Example metrics dashboard: <https://convertkit.baremetrics.com/>

Become A Debugging Master [Part 14] - Debugging Case Study: Meta

Let's make things concrete with a clear debugging case study from Meta. Here are the core points from the lesson:

- Mastering the deployment process (web continuous deploys vs mobile gated releases) and internal tools like “Where Is My Diff” at Meta can make it faster to rule out likely causes
- Being deeply familiar with experiments, gatekeepers, and other release tooling can help you spot issues like sudden error spikes or QA/test build failures without needing to dig into the code immediately
- Effective debuggers can quickly answer questions like when a code change deployed, what experiments launched, and what version a user was on during a bug report
- Going deep into tooling and metrics, not just code, lets you identify root causes faster, communicate precisely with teams, and resolve issues much more efficiently

How Facebook does continuous deployment: <https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale/>

Build Deep Relationships Quickly In Tech [Part 20] - Everyday Is Networking Day

Networking doesn't need to be hard. In fact, it should be easy. This lesson teaches you:

- What networking should feel like when you're doing it properly
- Why networking shouldn't feel like a hard, conscious, extra effort
- Ways to make networking seem more natural
- One of the most common mistakes engineers (and introverts in general) make when it comes to networking and maintaining relationships

Build Deep Relationships Quickly In Tech [Part 15] - Have Their Back

Disagreement is everywhere in tech, and it's often quite stressful. However, it's also a prime time for you to deepen your network and relationships. This lesson teaches you:

- Why having someone's back in times of disagreement is so powerful
- The main avenue to have someone's back
- How engineers completely waste the meetings they go to
- How having someone's back against yourself is insanely powerful
- Where so many engineers go wrong when it comes to their mentality around being right

Build Deep Relationships Quickly In Tech [Part 14] - Easy Ways To Earn Trust

Gaining trust is always harder than losing trust, but that doesn't mean it needs to be slow. This lesson teaches you:

- How you can earn trust simply by doing your work
- A very natural and technical way to earn trust as an engineer specifically
- Powerful ways to earn trust while scaling up your influence
- The immense power of a $5 coffee ☕️

Related resources:

- Learn how to do good work with our code quality course: [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- The Instagram oncall revamp case study: [\[Case Study\] Revamping Oncall For 20 Instagram Engineers - Senior to Staff Project](https://www.jointaro.com/lesson/esVxIGXYC5BdgxXUkO6H/case-study-revamping-oncall-for-20-instagram-engineers-senior-to-staff-project/)

Build Deep Relationships Quickly In Tech [Part 8] - In-Person Is King

Remote and flexible work are amazing, but they do come with massive downsides, especially when it comes to networking. This lesson teaches you:

- The fatal flaw with remote work, particularly with accruing social capital
- Why humans aren't intrinsically wired to work remotely (quite the opposite)
- What gets lost in translation during remote work and video calls
- What types of engineer should prioritize in-person work

SWE Internship Survival Guide [Part 3] - Do Your Research

Preparing before your internship starts can dramatically boost your success and confidence. Here are the core points from this lesson:

-  Do early research to understand your team, tech stack, workflow, and company culture so you can hit the ground running
- Gather information in two key areas: the day-to-day process (tools, tech, work style) and desired outcomes (like return offer criteria and evaluation timelines)
- Use sources like your future manager, forums, and most importantly, upperclassmen who’ve done similar internships—they’ll offer the most candid, balanced insights
- Ask thoughtful questions to get meaningful answers (e.g., “What do you wish you had known at the start?” instead of “Did you like it?”)
- Even learning small details—like which version control system is used—can give you a valuable head start and make your first week much smoother

Learn how to succeed overall in school as a Computer Science student here: <https://www.jointaro.com/course/15-years-of-software-engineer-knowledge-in-1-hour-30-minutes/succeeding-in-school/>

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

Ship & Grow 500k+ User Side Projects [Part 2] - Done Is Better Than Perfect

Code quality is important, but side projects sort of break the rules here. This lesson teaches you:

- How good engineers often mess up their side projects from the very beginning
- Why making mistakes is perfectly fine (good even) when starting a side project
- How fast you should launch the v1 of your side project

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.