Come Up With 500k+ User Project Ideas [Part 6] - Your Idea Is Worthless (For Now)

While the idea behind a side project or any tech product is extremely important, ideas as a whole are usually placed on a pedestal they don't deserve. This lesson teaches you:

- Why ideas are initially worthless
- What truly makes a side project valuable (hint: it's not that much about the idea)
- Why you shouldn't build out the vision of that random MBA you just met for 0 pay and 10% equity

Missed Estimates

In this segment, we’re challenged with a new scenario: an individual contributor consistently misses their own estimates. This is our opportunity to apply the essence of management—creating positive, sustainable change in organizational performance.

- We frame the issue not just as a problem to fix, but as an opportunity to **create a delta** in this person’s effectiveness and the team’s overall reliability.
- Our goal is to **understand the root cause**—is it due to optimism bias, poor time management, lack of clarity, or systemic issues in the planning process?
- We can introduce **structured changes**: better estimation techniques, mentoring, regular retrospectives, or adjusting sprint planning to account for variability.
- We aim for improvements that are **sustainable**—equipping the individual with tools or frameworks they can continue to use independently.
- As always, our success isn’t in reacting to the problem but in **proactively shaping a better outcome** that would not have happened without our involvement.

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)

So Many Software Engineers Get This Wrong About FAANG - Big Tech Isn't A Monolith

Many software engineers who aspire to get into Big Tech have this consistent, utopian vision of what working there is like. This couldn't be further from the truth and thinking in this way severely holds back your career direction.

Here are the core points from the video:
- **Big Tech companies aren't all the same** - Even though there are commonalities working at companies with such massive scale, each company has its own culture and unique way of doing things. For example, the life of the average engineer at Amazon is going to be *very* different from that of the average engineer at Microsoft.
- **Big Tech can vary within themselves** - Once you reach 5,000+ employees, it is impossible to maintain a completely homogenous culture throughout the entire company. Organizations and teams will develop unique sub-cultures, so even 2 engineers within the same company can have very different experiences, even if they're the same level and working on the same tech stack.
  - Meta is an extreme example by giving its major acquisitions (WhatsApp, Instagram, Oculus) a lot of autonomy in how they run. Meta is almost like 4 different companies in 1.

Related resources:
- [[Masterclass] Should You Work At FAANG? - What Big Tech Is Like For Software Engineers](https://www.jointaro.com/lesson/JnEnRphdi5TaPZl1Zrl8/masterclass-should-you-work-at-faang-what-big-tech-is-like-for-software-engineers/) - The full video where this clip was taken from
- ["Typical Day of Average FAANG Software Engineer?"](https://www.jointaro.com/question/sOoGZwl8fsQ3hq8yv10v/typical-day-of-average-faang-software-engineer/)
- ["How much is the tech culture within a company a predictor of its overall growth?"](https://www.jointaro.com/question/o7CVNROK0yiRa7YEeFNH/how-much-is-the-tech-culture-within-a-company-a-predictor-of-its-overall-growth/)
- [promotions.fyi](https://www.promotions.fyi/) - This is the website Rahul mentions at the end of the video

Is Distinguished Engineer Worth It? Dealing With Pressure And Work/Life Balance

Andrew became a Distinguished Engineer at Pinterest after working there for more than 9 years. He talks about: 

- The importance of persuasion and executive communication at this level.
- The amount of hours he put in to attain the Distinguished Engineer title at Pinterest. Andrew would frequently stay at the office until midnight, and his work/life balance suffered for years.
- Why he left his role at Pinterest (he made it to the top of the career ladder, literally could not get promoted further) to start a startup. 

Relevant links: 
- [How do you stay on top of everything?](https://www.jointaro.com/question/tgoVPigLZjzx7Z3qmMNH/how-do-you-stay-on-top-of-everything/)
- [How to keep my mental health while working in a competitive team and having kids?](https://www.jointaro.com/question/wpPPjI1gZtM5eNaCxlB0/how-to-keep-my-mental-health-while-working-in-a-competitive-team-and-having-kids/)
- [Master The Art of Successful Negotiations](https://www.jointaro.com/lesson/zQWx8Vq89OA2lERWnjvL/master-the-art-of-successful-negotiations-unlock-your-full-potential/)
- [Andrew on LinkedIn](https://www.linkedin.com/in/andrew-zhai-2796ab34/)

Break Into Tech And Become A Software Engineer [Part 10] - Why It's Better To Share

In this lesson, Brian explains the value of building in public as a tool for personal accountability, skill development, and community building.

This lesson covers:

- How building in public holds you accountable to your goals and helps you communicate more effectively, a key skill for software development
- The importance of using public sharing to connect with like-minded people and build a supportive community
- Why building in public improves your discoverability and can lead to networking, job opportunities, and genuine collaboration

If you need extra help breaking into tech, join Brian's exclusive, cohort-based bootcamp (just 10 students per batch). Use this special link for $800 off: <https://www.parsity.io/taro>

Connect with Brian on LinkedIn: <https://www.linkedin.com/in/brianjenney/>

What To Do If Your Manager Pings You Too Much

Receiving tons of interruptive messages or "can you take a quick look at this?" pings is something that every successful engineer must deal with.

The underlying cause of getting pinged too much by your manager is generally an indication that you're not effectively guarding your time.

A few options to consider:

- Understand the demands on your manager. Why do they feel the need to ping you so much? Do they not understand what you're doing, or perhaps they're facing a ton of pressure from their manager about high-pri bugs?
- Document how you're spending your time, and how that is making it harder for you to do the higher priority work.
- When you talk to your manager about the issue, bring up a proposed solution along with calling out the problem.

Related resources:

- ["How does one effectively handle pressure especially when the stakes are high?"](https://www.jointaro.com/question/Bxle0iRRpQXJV88KTpn4/how-does-one-effectively-handle-pressure-especially-when-the-stakes-are-high/)
- ["How to figure out what the most important projects are?"](https://www.jointaro.com/question/CgCPA60bDDHoOteN7Lmb/how-to-figure-out-what-the-most-important-projects-are/)

[Become A Go-To Person 6/18] Become The Product Expert

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

Negotiation Course: How To Practice Negotiation Skills

Just like anything else, practice makes perfect. But conceptually understanding negotiation and practicing negotiation is very, very different.

Be aware of the difference in the incentives and working model between a job negotiation (once every 2 years) and your operational model on the job (every day).

- One (the job) is built on shared understanding, sharing vulnerability. There's a clear incentive to make life more comfortable for people around you.
- One (the negotiation) is **not** built on shared understanding. The person who wins is the person who can tolerate discomfort.

The upshot of all this is that negotiation is extremely important but you don’t get to practice much. Verbalize the advice and practice in conversation with a friend or family member.

DSA Interview Step #1: Clarify The Problem

- The first step for any data structures and algorithms (DSA) problem is to *clarify the problem*. This means understanding exactly what the input and expected output are.
  - A common failure mode for candidates is that they will jump straight into coding, not doing this step. This leads to them wasting a lot of time writing code that isn't actually relevant.
- Often times in an interview, you will get a purposefully ambiguous problem - This happens with Big Tech a lot. The goal is get signal on the candidate's communication abilities.
- Clarifying the problem can help you *a lot* as it's very possible that the problem's scope is much more limited than you initially thought.

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

15 SWE Years In 1.5 Hours [Part 18] - Negotiation

You did it - You finally made it through the interview gauntlet and gotten an offer. However, you're not done yet. This lesson teaches you:

- Why you should always negotiate
- Why tech companies are not your friend (even FAANG when they give you an initial offer that has more money than you've ever seen)
- The #1 rule of negotiation that engineers constantly violate
- How tech compensation is more than just salary, especially at top companies

Take Rahul's full negotiation course here: [The Insider's Guide To Negotiating Your Tech Salary And Compensation](https://www.jointaro.com/course/the-insiders-guide-to-negotiating-your-tech-salary-and-compensation/)

Negotiation Course: Recognize The Information Asymmetry

First, let's make clear a harsh truth of the world: Companies are economically incentivized to pay you as little as possible, even if you think they're generous.

**You don’t get what you deserve, you get what you ask for.** Many candidates are unaware how high compensation can go, and therefore never ask about it. This leads to them being underpaid, and the information asymmetry is used to benefit the company.

Recruiters and companies talk to candidates every week or even every day. On the other hand, you probably only talk to a few companies every few years. So recruiters have way more information about what you’re likely making and what you may expect.

Motivation

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>

In this video, I discuss the common challenges engineers face when preparing for engineering manager interviews, highlighting that the criteria for these roles differ significantly from those of individual contributor positions. Many engineers are unaware of these differences, which can lead to confusion and poor performance during the interview process. I emphasize the importance of understanding these unique expectations to improve your chances of success. I encourage viewers to reflect on their own experiences and consider how they can better prepare for these types of interviews.

Master The DSA Interview [Part 26] - Find A Buddy

When it comes to data structures and algorithms, it's best to not go it alone. This lesson teaches you:

- Why data structures and algorithms is the easiest part of the interview space to partner with someone on
- How having a data structures and algorithms buddy is greatly helpful for your personal morale
- A sample meetup agenda that you can use when you meet with your data structures and algorithms interview buddy

Find a data structures and algorithms interview buddy here: <https://www.jointaro.com/networking/?selectedServices=Mock+Interviews>

Grow From Senior To Staff Engineer [Part 19] - Code Machine

As a software engineer, one of your most powerful tools to land more impact is to write more code. While many engineers write less code as they grow to staff, there is 1 large exception. This lesson teaches you:

- What the code machine staff engineer archetype is
- Why the code machine archetype is quite rare and usually not supported
- How to become a code machine

As this lesson talks about, code machines have both a stunning degree of velocity and quality. Level up your code quality here: [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

Negotiation Course: Negotiating With An Exploding Offer

An exploding offer is an offer that must be accepted within a time limit (potentially as short as a few hours), otherwise it will expire.

**Exploding offers are often fake** and you can take longer than the supposed deadline. However, you should protect yourself in the small chance that the explosion is real by having backup options.

If you face an exploding offer, the first step is to understand where the urgency is coming from:

> What’s the timing constraint? I’ve dedicated 3 weeks interviewing here and enjoyed meeting the team, but I'm curious why there's such an urgency at this point in the process?

A few options for how to request more time: 

- **(less effective)** Explain that you’re still collecting data and wrapping up the process so you’d like another week. Something like: "*I’m in the last round with the company so I’m confident I can get back to you by Monday.*"
- **(more effective)** Ask for more information. "*One thing I heard in the interview is that many of the mobile developers have transitioned to work on dev infra, which is interesting for me. Could I chat with someone who does made that transition?*" 
  - In a similar way, you can also request to chat with folks in the management chain, e.g. the director or VP.
  - When Rahul was at Meta, he’d do calls with people who got offers coming from Pinterest

Worst case scenario, you have to renege or quit shortly after joining. You should avoid this if possible (there is potential reputational damage), but we'll talk about this scenario in the next video.

DSA Crash Course [Part 58] - Connected Components Count Walkthrough

In this lesson, Alvin walks through the python implementation for the *connected_components_count* problem.

Code along and test your work in the following editor workspace: <https://structy.net/problems/connected-components-count?language=py>

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/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

Master The DSA Interview [Part 24] - It's About Consistency

How should you spend your time with data structures and algorithms problems? This lesson teaches you:

- Why it's better to have consistent, more reasonably sized studying blocks for data structures and algorithms instead of monster 1-day sprints
- What a good data structures and algorithms prep schedule looks like, shown with an in-depth example

Nail Your Promotion As A Software Engineer [Part 27] - Writing Your Packet

You have gone through the entire performance review cycle and done a ton of amazing work. So how do you now capture all the great things you've done so you have a great shot at promotion? This lesson teaches you:

- How to make writing your self-review/promotion packet easy (hint: it requires following the advice of this course)
- When to start writing your performance review materials
- How to work with your engineering manager to optimize the quality of your promotion packet

The Five Pillars of Business

In this first module, we explore the essence of individual contributor roles through the lens of core business functions. This sets the stage for understanding how management fits into the bigger picture.

- We break down IC roles across the **five pillars of business** (from Josh Kaufman): value creation, marketing, sales, value delivery, and finance—clarifying how each function contributes.
- The **essence of software engineering** is to create value by building software that solves problems for customers.
- Marketing professionals focus on **raising awareness** of that value, while salespeople focus on **exchanging value**, usually closing deals.
- Roles in value delivery, like customer support or DevOps, ensure that users receive and benefit from the value created.
- Finance professionals ensure **business sustainability**, tracking what’s working financially and what isn’t.
- This clarity of purpose—knowing what success looks like—is often **missing in management**, which leads us to part two: defining the true essence of a manager’s role.

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)

DSA Crash Course [Part 63] - Island Count Approach

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

> Write a function, *island_count*, that takes in a grid containing Ws and Ls. W represents water and L represents land. The function should return the number of islands on the grid. An island is a vertically or horizontally connected region of land.

```
grid = [
['W', 'L', 'W', 'W', 'W'],
['W', 'L', 'W', 'W', 'W'],
['W', 'W', 'W', 'L', 'W'],
['W', 'W', 'L', 'L', 'W'],
['L', 'W', 'W', 'L', 'L'],
['L', 'L', 'W', 'W', 'W'],
]

island_count(grid) # -> 3
```

```
grid = [
['L', 'W', 'W', 'L', 'W'],
['L', 'W', 'W', 'L', 'L'],
['W', 'L', 'W', 'L', 'W'],
['W', 'W', 'W', 'W', 'W'],
['W', 'W', 'L', 'L', 'L'],
]

island_count(grid) # -> 4
```

```
grid = [
['L', 'L', 'L'],
['L', 'L', 'L'],
['L', 'L', 'L'],
]

island_count(grid) # -> 1
```

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/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

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.