At Big Tech, You're Just A Cog In The Machine

Many people idolize FAANG companies, because they own these amazing products that everyone uses. However, working on these products is rarely as glamorous as people think: The experience is often worse the more successful the product is.

Here are the core points from the video:

- **Your ownership will probably be super tiny** - This is especially true at non-senior levels (junior and mid-level). Big Tech companies have thousands of amazing, ultra-productive engineers, and there's only so much ownership to go around. It's not uncommon for a Big Tech engineer to make $200k+ per year mainly working on a single button.
- **The work is very incremental** - Since Big Tech's product suite is so mature, it's very hard to find 0 to 1 work there, which people generally find to be more exciting. Almost all "shipped" code is wrapped in an experiment at Big Tech, and a lot of these experiments will fail.
- **It can be hard to feel fulfilled** - It's not the most exciting to own a single widget within a feature within a broader service within the overall product, and it's definitely not something that's cool to share when people ask you what you do.

Related resources:

- ["What's the difference between Big Tech and startups in terms of learning and growth?"](https://www.jointaro.com/question/KWXIrFIR1EIJsvdOdo7u/whats-the-difference-between-big-tech-and-startups-in-terms-of-learning-and-growth/)
- ["What does it mean to not have enough scope to be promoted?"](https://www.jointaro.com/question/bJuagPwOEEy5vkcXKkqh/what-does-it-mean-to-not-have-enough-scope-to-be-promoted/)

"What does your day to day look like?" - 8/19/2022

- *In short, it varies a **lot**.* Startups are extremely unpredictable, and the biggest problem facing the company will change every month or even every week.
- However, there are 2 constants:
  - **Talking with new Taro Premium members** - We chat 30 minutes with every new member to get to know them, make sure they're set up properly within the community, and understand their job and career goals. These meetings add up, and we have a decent amount of them every day.
  - **Talking with Rahul** - There's always a ton going on, and we always have a bunch of ideas on how to evolve Taro, so we need a lot of time to talk each day, usually 45 minutes to 1 hour. According to YC, cofounders falling out is the #1 reason startups fail, so we really want to make sure that doesn't happen.
- We try to get a decent amount of code in every week, but it's hard to find time for it and the company's top priorities are often times not build related.
  - On a side note, the highest build priority for us right now is to really make the Taro web app silky smooth.
- We are fundraising right now, so that's dominating our lives.
- We have a lot of meetings in general as networking is crucial for startups.

What To Do If Your Manager Seems Detached

This segment addresses the common experience of feeling disconnected from a manager and provides tactical advice for becoming more visible and driving engagement in that relationship. The message is rooted in realism: most managers are overwhelmed, and visibility must be earned through structured communication.

- **Managers often appear detached—not maliciously, but due to bandwidth**: With many reports and constant demands, a manager may not track every individual’s progress or struggles unless the impact is urgent or visible.
- **Visibility must be self-driven**: It's essential to lower the "activation energy" required for a manager to know what’s going on. Regular updates make it easier for them to stay engaged and supportive.
- **Weekly written updates are powerful**: Creating a consistent cadence of updates helps establish a communication rhythm. These should include:
  - *Top of mind*: What’s currently being prioritized.

  - *Priorities*: Key goals from the current or past week.

  - *Actions*: Clear tasks being worked on, by either the employee or the manager.
- **Proactive documentation helps managers help more effectively**: Preparing and sharing this structure before one-on-ones gives the manager context and allows for more productive, actionable feedback.
- **Taking initiative builds influence**: Instead of expecting a manager to chase progress or identify gaps, the individual contributor can shape the relationship by driving clarity and making collaboration easier.

The Most Misunderstood Part Of Tech Pay - Stock Options

This segment unpacks **stock options**, a type of equity compensation typically offered by startups rather than large public tech companies. It contrasts stock options with RSUs and explains how options function, including taxation and risk.

- **What Stock Options Are:** A stock option gives the right to purchase company shares at a predetermined price (the “strike price”). These are common in startups but rare in large public companies like Google or Facebook.
- **Grant and Vesting Mechanics:** Similar to RSUs, options usually vest over four years with a one-year cliff. The total grant allows employees to buy a fixed number of shares—often a large number—at a low strike price.
- **Value and Risk:** The value of stock options depends on the company’s success. While paper valuations can be high, employees must actually buy the shares (unlike RSUs, which are granted). If the company never goes public, the options might end up worthless.
- **Types of Stock Options:**
  - **ISOs (Incentive Stock Options):** Taxed only upon sale, usually favorable for employees.

  - **NSOs (Non-qualified Stock Options):** Taxed at the time of exercising and again at sale, even if the shares haven't yet generated real money—making them riskier.
- **Tax Implications:** With NSOs, employees may owe taxes just for exercising the option (based on fair market value), creating potential financial burden even before any profit is realized.

This complexity and risk/reward profile is a key difference from the more predictable RSU structure in big tech compensation packages.

DSA Interview Step #2: Figure Out Your Overall Strategy

Related resources:
- [[Taro Top 10] Effective Interview Prep](https://www.jointaro.com/playlist/HLBYxJI7D1j8STolrwum/)
- [[Taro Top 10] Finding A Tech Job](https://www.jointaro.com/playlist/E6R0wVJ5EyCfVnVrlfno/)

1 on 1 Meetings Are An Exercise In Proactivity

Why should you err on the side of creating a 1 on 1 meeting instead of waiting for it to be absolutely necessary?

True or false: Team meetings are more important than 1 on 1 meetings, so you should create them more aggressively for everyone to stay in sync.

Being proactive about setting up one-on-one meetings helps build strong relationships and avoid costly misalignments down the line.

- **Default to setting them up**: It’s better to create a recurring one-on-one and cancel it later than to realize too late that it was needed.
- **Low time cost, high value**: One-on-ones only use two people’s time, making them much less costly than poorly-run team meetings.
- **Prevent bigger issues**: Skipping one-on-ones can lead to being misaligned with key collaborators, which may cause serious problems later in a project.
- **Sync early with core stakeholders**: Especially in cross-functional teams or shared ownership scenarios, early and regular one-on-ones help prevent misunderstandings and build trust.

15 SWE Years In 1.5 Hours [Part 4] - Debugging

No matter how careful you are as a software engineer, your code will always have bugs. On top of that, you will also need to spend time fixing bugs in code written by other people. This lesson teaches you:

- Why debugging is always a valuable skill (while feature development often isn't)
- How debugging forces you to develop a deeper understanding of the system
- The framework and process you need to understand in order to fix any bug

DSA Crash Course [Part 10] - Most Frequent Char Approach

In this lesson, Alvin explores the strategy to solving the following interview problem:

> Write a function, *most_frequent_char*, that takes in a string as an argument. The function should return the most frequent character of the string. If there are ties, return the character that appears earlier in the string.
>
> You can assume that the input string is non-empty.

```
most_frequent_char('bookeeper') # -> 'e'
```

```
most_frequent_char('david') # -> 'd'
```

```
most_frequent_char('abby') # -> 'b'
```

```
most_frequent_char('mississippi') # -> 'i'
```

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: <https://www.linkedin.com/in/alvin-zablan-b73a92117/>

Master The DSA Interview [Part 28] - Don't Forget: Other Interview Types Exist

Data structures and algorithms are a core part of the software engineering interview loop, but it's important to remember that there are other critical interview types as well, including for FAANG. This lesson teaches you:

- How many engineers who completely fail their Big Tech interview actually did well on the data structures and algorithms portion, wasting all of their LeetCode grind
- How the amount of time you spend on data structures and algorithms preparation will vary based on the types of interviews you have
- How the amount of time you spend on data structures and algorithms preparation will vary based on your level
- General attributes to use to calculate the amount of time you need to allocate to data structures and algorithms

Please ask your recruiter what's going to be on your interviews. Don't be afraid to be a bit aggressive and don't be shy. Follow the advice here: <https://www.jointaro.com/course/ace-your-tech-interview-and-get-a-job-as-a-software-engineer/talk-to-your-recruiter/>

Master the behavioral interview with this course: [Master The Behavioral Interview As A Software Engineer](https://www.jointaro.com/course/master-the-behavioral-interview-as-a-software-engineer/)

Master the system design interview with this course: [The Top Ways People Fail System Design Interviews](https://www.jointaro.com/course/the-top-ways-people-fail-system-design-interviews/)

Master The DSA Interview [Part 22] - The #1 Tool For DSA Prep

As a mainstay of the software engineering industry for 15+ years, data structures and algorithms have more than their fair share of online resources to help you learn it. This lesson teaches you:

- The #1, time-tested resource to learn data structures and algorithms
- The trap many engineers fall into when learning data structures and algorithms when it comes to tool selection
- How to organically expand LeetCode into the rest of your learning tree
- What to do when you get a FAANG interview

If you're interested in NeetCode, you get a discount on it with your Taro Premium membership. Redeem it here by using code TARO at checkout: <https://neetcode.io/pro?utm_source=taro>

Engineering Management Made Easy: The ABCs for First-Time Managers

How to avoid burnout, enjoy being a manager, and multiply your team’s efforts.

I will share mistakes that I made when I first became an Engineering Manager and what I learned from those, followed by Q & A.

Connect with Umang on LinkedIn: [**https://www.linkedin.com/in/umangv/**](https://www.linkedin.com/in/umangv/)

Become An Open Source Master [Part 3] - What Is Open Source?

We'll start with an introduction to open source, which encompasses not just software but also data, education, standards, hardware, and access.

- Open-source software is released under a license that allows users to use, study, change, and distribute it for any purpose.
- There are various open source licenses with different levels of permissiveness, but for this course, we'll focus on projects under the MIT license.
- Open-source code empowers users to study and adapt software to their needs, similar to how user scripts or custom style sheets modify websites.
- You can learn from open-source projects like React to understand how companies build complex systems.
- If you make changes, you can fork the project or submit your changes back to the original project through a pull request.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Grow From Junior To Mid-Level Engineer [Part 19] - Go Deeper: Follow Through

Take the related courses:

- [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- [Ask Great Questions That Get Great Answers Quickly](https://www.jointaro.com/course/ask-great-questions-that-get-great-answers-quickly/)
- [Become The Go-To Expert As A Software Engineer](https://www.jointaro.com/course/become-the-go-to-expert-as-a-software-engineer/)
- [Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)

[Become A Go-To Person 3/18] Jordan's Story (Imposter Syndrome)

Dealing with imposter syndrome and getting to the senior level.

A course by [Jordan Cutler](https://www.linkedin.com/in/jordancutler1/), Senior Software Engineer at Pinterest and Author of the [High Growth Engineer Newsletter](https://read.highgrowthengineer.com/)

Maximize Your Productivity As A Software Engineer [Part 19] - Eat The Frog

The first couple hours after you start work are absolutely crucial - Unfortunately many software engineers waste this crucial time, working on the wrong type of tasks. This lesson teaches you:

- What it means to eat the frog (don't worry, it doesn't involve any actual eating or 🐸s)
- Why eating the frog is so important
- The difference between junk food tasks and core tasks

Maximize Your Productivity As A Software Engineer [Part 15] - Live And Breathe Quality

One of the biggest myths in the tech industry is that in order to move incredibly fast, you need to sacrifice quality and do a mediocre job. This lesson teaches you:

- The dangers of cutting corners when it comes to engineering work
- Why having high code quality leads to you landing code faster
- Different ways for you to weave quality into your work for an immediate positive return on investment for your time

Maximize Your Productivity As A Software Engineer [Part 12] - Just 1 Thing

As a software engineer, it is incredibly easy to get overwhelmed with the sheer amount of tasks on your plate. This lesson teaches you:

- What you need to do every single day to give yourself the gift of focus and be productive
- What to do if you absolutely need to get multiple major tasks done in a day
- How to enforce your focus on your singular task by systematizing it

Grow From Mid-Level To Senior Engineer [Part 11] - Debugging

Debugging is one of the most important skills every software engineer needs to develop. Despite this, many software engineers see bugs as a source of frustration instead of opportunity. This lesson teaches you:

- The mindset shift that has to happen when a mid-level engineer grows to senior engineer when it comes to bugs, particularly large production outages
- How senior engineers solve different types of bugs of a broader scope compared to mid-level engineers

To get better at debugging, check out: [\[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/)

Master The Behavioral Interview [Part 19] - Cultural Values

Culture fit is real. A lot of tech companies have toxic culture and don't vet for it properly, but that doesn't change the fact that culture fit is extremely important to running a healthy engineering organization. This lesson teaches you:

- Why cultural values are important
- What you should do to effectively study and internalize the cultural values of a company you are interviewing with
- How to weave a company's cultural values into your behavioral interview answers through an example with Alex for his Meta interview

If you're curious as to how Meta's engineering culture works: ["Is sprint planning and agile not a thing at Meta?"](https://www.jointaro.com/question/tB7borE2AWb1KcuFEcon/is-sprint-planning-and-agile-not-a-thing-at-meta/)

From "Meets Most" to "Greatly Exceeds" in 3 Months at Facebook

Imagine pouring your heart and soul into your work, only to be met with criticism instead of commendation. This scenario is all too familiar for many engineers who, despite their hard work, find themselves at odds with their manager's expectations due to a misalignment with business priorities. My own journey at Facebook serves as a testament to this common predicament. Tasked with two major projects, I found myself at a critical juncture halfway through, being told my efforts were not meeting expectations.

I was not always doing exceptional at Facebook, but this time I knew that I was not below the "meets expectation" mark. I had been there before, but this time was not it.

Learn more about ratings at Facebook (aka Meta): <https://www.jointaro.com/topic/meta/performance-review/>

Despite knowing that, the assessment of the manager was a bitter pill to swallow, leaving me furious and speechless. However, it also marked the beginning of a transformative journey. I ventured into realms that many engineers shy away from, embracing principles that I previously overlooked. This shift in behavior and perception propelled me from being perceived as merely meeting most expectations to greatly exceeding them, achieving a rating leap that not only vindicated my efforts but also significantly enhanced my bonus.

In this seminar, I aim to share the insights and strategies that catalyzed my dramatic turnaround. I will delve into how a recalibration of focus and an embrace of broader impact can elevate your work from good to exceptional. Additionally, I will touch on the crucial balance between maintaining stellar job performance and navigating a job search. This balance is critical for ensuring you are not cornered should your job search extend longer than anticipated. Join me as I unravel the nuances of achieving long-term career satisfaction through sustained excellence and strategic job search efforts.

Check out these resources for additional deep insights into performance review:

- [\[Masterclass\] How To Navigate Your Performance Review In Tech](https://www.jointaro.com/lesson/b0B8uqIAUnBLE10jJHJG/masterclass-how-to-navigate-your-performance-review-in-tech/)
- [\[Masterclass\] How To Work Better With Your Engineering Manager](https://www.jointaro.com/lesson/2PbJb2fuqF3iMHy57eEg/masterclass-how-to-work-better-with-your-engineering-manager/)

Presented by Yogi Sharma: <https://www.linkedin.com/in/yogi1/>

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.