5 Offers w/ FAANG Companies As A New Grad: Details + Lessons

In 2014, Rahul graduated from Stanford with a BS and MS in Computer Science. He received new grad Software Engineer offers from 5 companies: 
1. Facebook
2. Twitter
3. Microsoft
4. Google
5. Square

This video outlines the exact details of the offers, and models out the increase (or decrease) in value of those offers 8 years later, in 2022. The total compensation of the offers range from $174K/year to $262K/year, and those numbers go a lot higher if you factor in stock appreciation.

If you want to better understand how compensation works in top tech companies, first watch [this video](https://link.jointaro.com/819tdsqwJj4VnaEC6).

"How can I get the most out of Taro Premium?" - 9/7/2022

- **Ask us questions!** 🙏 🙏 🙏
  - You can do it from the Taro web app [here](https://app.jointaro.com/questions/create).
  - A lot of your growth corresponds to how much you put yourself out there. The more you share, the more opportunities you're giving yourself to "get lucky" and receive some incredible, insightful advice you can apply to your job and level up.
  - *You don't need to have a good question or even a full question at all to ask something.* Taro is a judgment-free zone. Feel free to just share your current situation and thoughts on it and end your question with something like, "Do any of you have thoughts on how I can improve this situation?"
- Follow the tag corresponding to your level
  - The biggest commonality when it comes to career issues is level.
  - There are very clear patterns among senior engineers pushing for staff, mid-level engineers pushing for senior, etc.
  - In the Taro mobile app, go to the tags page and find the one for your level. If you follow it (or unfollow and then follow it again), it will float to the top of your home feed.
- Share your feedback
  - Every Taro Premium member is effectively a "mini product manager" of the company.
  - If you find a bug or have a feature idea that would help you a lot, please let us know!

What To Do If Your Manager Doesn’t Care About Your Work

This clip explores a common frustration where employees feel ignored by their managers, even when providing regular updates. The root cause is usually a misalignment in perceived project importance.

- **Perceived neglect often stems from misaligned priorities**: If your manager appears disengaged, it's likely because your project isn't among the top priorities they are focused on.
- **Managers typically operate with a clear project hierarchy**: In teams with many contributors, managers mentally stack-rank initiatives. Only a few projects (typically the top 1–2) receive the lion’s share of attention and resources.
- **Impact matters more than effort**: You may be doing good work, but if it’s not on a high-impact initiative, it won’t attract your manager’s attention or advocacy.
- **You have two options**:
  1. **Switch to a higher-priority project** that better aligns with team goals.

  2. **Build a compelling case** for why your current project should be elevated in importance—explain its impact, urgency, and strategic value.
- **Visualizing impact can help**: The graph referenced (a power law curve) illustrates that a small number of projects generate most of the value. Aim to work on—or reframe your work as—one of those high-leverage efforts.

Job Switching Is Great For Pay But With Major Caveats

This video segment explores **job switching as a strategy to increase compensation**, acknowledging its significant financial benefits while outlining important limitations. It offers a balanced view of when and how to leverage this option effectively within a career in tech.

- **Job switching can deliver major pay increases**, especially when moving from lower-paying companies to top-tier tech firms like Facebook, Google, or Airbnb. Offers from these companies often represent a different compensation tier altogether.
- **The current tech market is highly competitive**, driven by remote work and talent shortages, which makes switching jobs particularly lucrative for engineers not already paid at “top of market” rates.
- **However, job switching comes with diminishing returns**. Frequent transitions (e.g., every 6–12 months) can raise red flags for recruiters due to high costs of hiring and onboarding, making a two-year tenure the informal minimum standard.
- **Banding limits how much pay can increase** through switching if already working at top-tier firms. For example, a mid-level engineer will only be offered a similarly banded role and compensation elsewhere.
- **Job switching doesn’t contribute to actual growth as an engineer**. Preparing for interviews (e.g., Leetcode) is time-consuming and doesn’t improve the long-term skills needed to succeed or progress to leadership roles like principal engineer.

This Is Required To Put The Interviewer On Your Side

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

This Tool Is Especially Amazing For Big Tech Interviews

20 Years Of Fighting Procrastination [Part 5] - Debug Your Productivity

Procrastination thrives when you confuse learning with progress. Here are the core points from the lesson:

- Jumpstarting productivity means producing *before* you feel ready — even a rough draft unlocks momentum
- Replace the one-way flow of tutorials with a feedback loop: code → learn → refine
- Writing personal notes or process logs boosts clarity and reduces future ramp-up time
- Systematize repeatable work into reusable components to move faster with each project
- Build a library of “done before” artifacts you can copy, tweak, and ship again and again

Build Deep Relationships Quickly In Tech [Part 1] - How This Course Works

Trying to break into FAANG, but you have no close friends there willing to give you a strong referral? Aiming for a promotion, but you don't have enough senior peers to vouch for you? These are career shortfalls engineers face constantly, and it's because *they don't have a strong enough network*.

This course is here to fix that issue for you, because at the end of the day, your network is your net worth, especially in a hyper-competitive tech market. Here are the core parts of the lesson:

- Your instructor [Alex Chiou](https://www.linkedin.com/in/alexander-chiou/) walks you through his extensive 10+ year Silicon Valley background with rapid career advancement, ending up as a high-performing tech lead making $750k at Robinhood. Most importantly, he goes through how he's built a massive network full of talented people willing to fight for him across his career and the many career benefits he's reaped from that.

- We walk you through the course objectives. By the end of the course, you will:

  - 🌟 Understand the **\#1 rule** of networking

  - 2️⃣ Set up a basic **2-step process** for networking

  - 🤝 Know how to find the **best people** for your network

  - 🏃 Develop tools to **build relationships fast**

  - 🛑 Save time by **avoiding common mistakes**

Come Up With 500k+ User Project Ideas [Part 7] - The Alex Formula

Repeated excellence is the key to any very successful tech career. Alex has accomplished this time and time again with around a dozen side projects that have 10,000+ users, and he's here now to spill the beans. This lesson teaches you:

- The exact playbook Alex uses to repeatedly build successful apps with several thousand users
- The "Honer vs. Innovator" philosophy when it comes to understanding engineer types
- Why you should (probably) stop trying to be Steve Jobs and go hard down the innovator route
- How honers are often incredibly underrated and can still achieve stellar career outcomes
- The ideal place to be on the honer &lt;-&gt; innovator spectrum when it comes to side projects

Come Up With 500k+ User Project Ideas [Part 2] - What Makes A Project Valuable

Most engineers optimize for the wrong thing when they build personal software projects, which is 99% of engineer portfolio projects don't matter at all. This lesson teaches you:

- The only metric that matters when it comes to the quality and impressiveness of your side project
- Why getting actual users supercharges the learning and growth you get from building a side project, far more than choosing the best "modern" tech stack ever could
- Common traps engineers fall into that make their side project meaningless, especially when it comes to recruiting

DSA Crash Course [Part 7] - Big-O Examples Lecture

In this lecture, Alvin shows examples of code with different Big-O complexities.

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 18] - Fishing

Many engineers think that they got rejected due to the interviewer being bad or "out to get them". While low-quality interviewers do exist (and there are a lot of them), it is often the engineer's fault by being a weak candidate. This lesson teaches you:

- Why there is often a discrepancy between what engineers believe is the cause of their data structures and algorithms interview rejection and what reality actually is
- What fishing is and how it forces interviewers into a very awkward situation that makes them seem icy to the candidate
- How to not do fishing during an interview so you can have a real chance of passing (and make the interviewer more likely to help you)
- Why asking the interviewer for a raw hint is a recipe for failure

Master The DSA Interview [Part 15] - Edge Cases

Too many engineers only care about the happy flow, but it is the easy thing to do. This lesson teaches you:

- Why handling edge cases is so important as an engineer, especially at FAANG
- The mindset you need to have to tease out edge cases systematically
- Common edge case scenarios for data structures and algorithms problems
- What a great edge case analysis looks like, explained with an in-depth example

Take the code quality course here: [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

Master The DSA Interview [Part 4] - DSA Prep Is Insanely High ROI

It's easy to look at data structures and algorithms and see them as an annoying waste of time. However, there's more to them than you think. This lesson teaches you:

- A healthy perspective to have when it comes to studying data structures and algorithms
- Why data structures and algorithms are uniquely positioned when it comes to career return on investment for your time
- How to transform your mindset to actually be excited when grinding LeetCode

Become An Open Source Master [Part 2] - How This Course Works

We'll explore the benefits of open source and how to contribute to existing projects in this course.

- Understand the benefits of open source and the mindset needed to work effectively in the open source ecosystem
- Learn how to get involved in someone else's project, understand their codebase, and make meaningful contributions
- Explore how contributing to open source can benefit your career by showcasing your skills and building your professional profile.
- This course won't cover how to create your own open source project or what it's like to work on one from within a company.

Connect with James: 

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

Grow From Junior To Mid-Level Engineer [Part 6] - Code Quality

In order to survive as a junior engineer, you need to learn how to code fast. The next step is to learn how to code *well*. This lesson teaches you:

- The 2 core components behind code quality
- The differences between junior and mid-level engineers when it comes to their pull request quality
- The many ingredients behind a clean pull request and which ones matter the most
- What a clean pull request looks like, one showing strong mid-level engineer behavior
- The differences between junior and mid-level engineers when it comes to their technical decision making
- Why communication is so important when it comes to technical decisions and how mid-level engineers do it better than junior engineers
- How to understand seniority from fresh junior to strong mid-level through the lens of technical decision making
- A simple metric to measure your code quality and see if you're making good progress to mid-level

Take the code quality course here: [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

Grow From Junior To Mid-Level Engineer [Part 1] - How This Course Works

Congratulations on breaking into tech as an engineer! Let's get you off to a great start. Here are the core parts of the lesson:

- Your instructor [Alex Chiou](https://www.linkedin.com/in/alexander-chiou/) walks you through his extensive 10+ year Silicon Valley background with rapid career advancement, ending up as a high-performing tech lead making $750k at Robinhood. More importantly, he goes through how he was able to grow his mentees to lightning fast promotions, particularly at Meta where he grew 10+ junior engineers (E3) to mid-level engineers (E4) in just 1 year!

- You'll understand what it means to be a junior vs. a mid-level engineer in the market, including the interview space

- We walk you through the course objectives. By the end of the course, you will understand:

  - 💡 Truly understand the **difference** between a junior engineer and a mid-level engineer

  - 🛠️ Learn to **code** like a mid-level engineer

  - 💪 Know what it means to be truly **independent**

  - 🧠 Have the right **mindset** to act as a mid-level

  - ✅ Define a clear **roadmap** to mid-level

If you haven't already, we recommend taking the overall promotion course here: [Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)

How To Be An Effective Tech Lead [Part 1] - How This Course Works

As a software engineer, you need to eventually grow into a tech lead to pursue more senior levels. However, it's much easier being a bad tech lead instead of a good tech lead - This course is here to help you be the latter. Here are the core parts of the lesson:

- Your instructor [Jocelin Ho](https://www.linkedin.com/in/jocelinho/) walks you through her extensive 10+ year tech background as a Meta tech lead and the CTO/Cofounder of Cooby (Sequoia-backed startup), where she built engineering teams from scratch and mentored other tech leads

- You'll understand if this course is a good fit for you

- We walk you through the course objectives. By the end of the course, you will know:

  - 💡 The full definition of an effective tech lead

  - 💻 What technological skills tech leads must possess

  - 🙌 How tech leads demonstrate true leadership

  - ✅ Practical tips to start acting as a tech lead

Master The Behavioral Interview [Part 25] - Go Deeper: Follow Through

Go through case studies by level to understand the expectations at each one: [\[Taro Top 10\] Understanding Engineering Levels](https://www.jointaro.com/playlist/e9rjATPbSyvRPsukXiHn/)

Take these courses as well:

- [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)
- [\[Course\] Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)

Master The Behavioral Interview [Part 24] - Challenge Yourself, Do Great Work

Behavioral interviews are fundamentally an exercise in storytelling. This means that in order to pass these interviews as a software engineer, you need great stories to begin with. This lesson teaches you:

- The 2-step process to become absolutely incredible at behavioral interviews
- The most common mistake software engineers make with their mentality when it comes to growth
- How to get better at coding, even if you're unemployed

For more resources on becoming a better software engineer:

- [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- [\[Course\] Build Side Projects With 500k+ Users: Coming Up With An Idea](https://www.jointaro.com/course/build-side-projects-with-500k-users-coming-up-with-an-idea/)
- [\[Taro Top 10\] How To Create Scope As An Engineer](https://www.jointaro.com/playlist/EWIo3USNcsgXbCs5PS0h/)
- ["What are the Core skills a SDE should be consistently developing?"](https://www.jointaro.com/question/Hs8VJtUb6bfTPjUgbj96/what-are-the-core-skills-a-sde-should-be-consistently-developing/)

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.