One Of Management’s Hardest Tasks: Properly Giving Feedback

This video explores the complexities of effective feedback in engineering management, emphasizing the balance between honesty and empathy. It also highlights how mentoring approaches must evolve based on the experience level of the engineer receiving feedback.

- **Honest feedback is essential for growth**: Engineering managers must avoid both extremes—being overly harsh or too protective of emotions—and instead aim to deliver candid, constructive feedback with empathy.
- **Empathy does not mean avoidance**: Withholding critical feedback to preserve feelings can be detrimental to an engineer’s development; it’s important to be honest even when the message is difficult.
- **Good mentorship goes beyond directives**: Effective managers explain the *why* behind advice, helping reports internalize the underlying principles rather than just follow instructions blindly.
- **Tailor feedback to experience level**: Junior and mid-level engineers often need clear, actionable advice, while senior engineers should be given higher-level guidance and trusted to translate it into execution independently.
- **Mentoring is a skill that evolves**: The ability to adjust mentoring style across a range of experience levels is a key marker of a strong engineering manager.

DSA Crash Course [Part 62] - Shortest Path Walkthrough

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

Code along and test your work in the following editor workspace: <https://structy.net/problems/shortest-path?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/)

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.

Software Engineers - Don't Forget These 2 Things When Considering A Team

These 2 more tactical aspects are often forgotten by software engineers when evaluating a team, even though they are huge influencers on your work-life balance and career growth on a team:
- **Oncall** - You want to make sure that the team has a healthy system there where you aren't oncall too often, and the system is stable (so you don't need to wake up in the middle of the night constantly to fight fires). For more information on how to evaluate the health of an oncall rotation, check out the linked discussion below from an Atlassian Software Engineer.
- **Code review speed** - It is easy for slow iteration here to stack up. If your team takes 3 days on average to review your PR and you need 3 revisions to finalize your commit, that means it will take you 2 entire weeks to land code (which is abysmal). A good team will turnaround code reviews in <1 day.

This clip was taken from our [masterclass on finding the best company/team for you - Click here to watch the full thing](https://link.jointaro.com/F4DDyKfuo3hMhj868).

Related resources:
- ["How do I factor in oncall into my team selection?"](https://link.jointaro.com/3LHQz46Ft1c7ZoXo6) - Question from a Junior Software Engineer at Atlassian
- [Code Review MUST Be Fast, Otherwise The Team Is Unhealthy](https://link.jointaro.com/oxK55E1bkX8nMeNGA)

Come Up With 500k+ User Project Ideas [Part 18] - Go Deeper: Follow Through

Join Alex for Group Office Hours (check the bottom right): <https://www.jointaro.com/p/alex-chiou/>

Share your side project idea in the Taro forum: <https://www.jointaro.com/questions/create/>

Community member made summary of the course: [Side Project Ideas - Summary Doc](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/courses%2Fgeneral_resources%2F%5BSUMMARY%5D%20Side%20Projects%20-%20Coming%20Up%20With%20An%20Idea.pdf?alt=media&token=d7a9aa4e-c02d-4663-ac91-a09547428fe2)

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/)
- [Get More Interviews: Write A Stellar Resume As A Software Engineer](https://www.jointaro.com/course/get-more-interviews-write-a-stellar-resume-as-a-software-engineer/)

DSA Crash Course [Part 74] - Minimum Change Walkthrough

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

Code along and test your work in the following editor workspace: <https://structy.net/problems/min-change?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/)

Become An Open Source Master [Part 21] - Start With Something Small

- Start with small contributions to get familiar with the workflow and build our confidence. Maintainers probably won't give you the adequate time of day if you have a large code change while being unkonwn.
- Fork the project to our own account, make changes, and commit them there.
- Answer the questions in the pull request template to help the maintainers understand our changes.

Github guide to forking a repository: <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo>

Connect with James:

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

Why Companies Do PIPs: The Ultimate Guide To Navigating A PIP

A PIP can seem cruel, but there’s a clear reason that companies use them year after year. Let’s start with the top priority for a manager: ensure the optimal performance of the team. For a manager, getting their reports promoted or singing their praises is important, but only insofar as it’s in service of the optimal performance of the team.

Another detail to realize is that the high performers on any team do an outsized amount of work. This is especially true in jobs that have tremendous leverage for the most skilled workers, such as software engineering (thus the famed “10x engineer”). When a company is large enough, a “bell curve” of performance will emerge. A PIP is focused on the employees who are deemed as low performers, typically the bottom 10% of the bell curve.

So, returning back to the original question: the reason why companies do PIPs is to **ensure optimal productivity and impact** for the overall employee base. If high performers sense that poor performance is not being addressed, they may leave the team. So a PIP is a way to push poor performers off the team.

The company also wants to push people out in a way that **minimizes the chance of a lawsuit**. Even though employment in the US is at-will, there’s still a chance of getting sued if the employee argues that they were fired for an illegal reason (e.g. due to a protected characteristic).

The company or manager may claim that the PIP is designed to help you, but that’s almost never the case. They’re more concerned about minimizing the negative impact on the broader team.

Finally, PIPs are often “weaponized” to fire people under the guise of performance when the company doesn’t want to call it a layoff. This is especially relevant now in the current economy as companies may enter an age of austerity.

DSA Crash Course [Part 77] - Max Path Sum Approach

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

> Write a function, *max_path_sum*, that takes in a grid as an argument. The function should return the maximum sum possible by traveling a path from the top-left corner to the bottom-right corner. You may only travel through the grid by moving down or right.
>
> You can assume that all numbers are non-negative.

```
grid = [
[1, 3, 12],
[5, 1, 1],
[3, 6, 1],
]

max_path_sum(grid) # -> 18
```

```
grid = [
[1, 2, 8,  1],
[3, 1, 12, 10],
[4, 0, 6,  3],
]

max_path_sum(grid) # -> 36
```

```
grid = [
[1, 2, 8, 1],
[3, 10, 12, 10],
[4, 0, 6, 3],
]

max_path_sum(grid) # -> 39
```

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

[Timeless Career Advice] How Software Engineers Use Code

How To Influence Your Team Without Authority

Huge thanks to [Ryan Kuck](https://www.linkedin.com/in/ryan-kuck/) for leading this session!

Have you had amazing idea with clear data to support it, but it was rejected? In this event we will talk about why that might have happened, and suggest alternate strategies for next time.

Spoiler alert: We use computers to reach millions/billions of users, but we are very different from computers ourselves. Presenting the best data to another person can actually backfire, unless it is coming from a place of shared goals/values and trust. It isn’t logical, but it is human nature. If you explain a better idea than I presented, and you even have rock solid evidence, I no longer am thinking about the user or our business impact but rather about how I just don’t want to “be wrong”.

Come to this event with your stories of challenges and successes of influencing your engineering team!

To dive deeper, check out these resources:

- [**"How do I lead without authority?"**](https://www.jointaro.com/question/BWv3hFSELbn59mXJbkNB/how-do-i-lead-without-authority/)
- [**\[Course\] Effective Communication For Engineers**](https://www.jointaro.com/course/effective-communication-for-engineers/)

Was Getting A Masters While Working Worthwhile? From a Distinguished Engineer

Andrew Zhai was a Distinguished Engineer at Pinterest.

After graduating from UC Berkeley in 2013, Andrew started working at Pinterest in Computer Vision. Within a few years, he decided to do a part-time Masters degree from Stanford to build his foundational knowledge of Machine Learning and Deep Learning.

Andrew says the academic rigor and the courses helped him achieve success in industry. For the Machine Learning (ML) field in general, the field evolved quickly enough that going 'back to school' was worthwhile.

[Andrew on LinkedIn](https://www.linkedin.com/in/andrew-zhai-2796ab34/)

Related:

- [Does having a Master's mean I can expect a salary equivaent of a 2 YoE SWE?](https://www.jointaro.com/question/YSMUN3uxDmGLqKxIvmXI/does-having-a-masters-mean-i-can-expect-a-salary-equivaent-of-a-2-yoe-swe/)
- [Do I need to do masters in Computer Science to move ahead in career?](https://www.jointaro.com/question/tKuUT3ELEa1uCGBuMykX/do-i-need-to-do-masters-in-computer-science-to-move-ahead-in-career/)
- [Is an online Master's Degree in Computer Science worth it for a non-CS Bachelor's degree holder with 2 YOE?](https://www.jointaro.com/question/Qth4ohK7HbHTEC83dwIJ/is-an-online-masters-degree-in-computer-science-worth-it-for-a-non-cs-bachelors-degree-holder-with-2-yoe/)
- [Rahul's Computer Science Masters Degree from Stanford in 7 Minutes](https://www.youtube.com/watch?v=iDu6slRfLY4)

How To Be An Effective Tech Lead [Part 12] - Foster Trust

Trust or social capital is the primary currency you need to get anything done as a tech lead. This lesson teaches you:

- Why fostering trust is so important for team efficiency, explained through a simple example
- How to build up trust when things aren't going perfectly (which will inevitably happen to you as a tech lead)
- How to build up trust when things are going well, taking full advantage of positive momentum

Learn how to build deep relationships fast here: [\[Masterclass\] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

This Is Why You Should Work For Big Tech

So many engineers want to work for FAANG and for good reason: There are lot of career benefits that Big Tech is exceptionally good at providing.

Here are the core scenarios where Big Tech is a slam dunk career choice for you:
- **You are earlier in career** - Big Tech will give you a rock solid foundation across all levels: Learning, compensation, job prospects - You name it. When you're younger, you will generally be more flexible with work-life balance (i.e. you're more physically able to work longer hours), so you will be better equipped to deal with the stress of Big Tech.
- **You need money** - More money is almost always useful, and if you live in a very high cost-of-living area (e.g. SF Bay Area), it becomes necessary. Big Tech gives a consistent, incredibly high income.
- **You value stability and are risk-averse** - Even with the layoffs, these companies are some of the safest places to be. Compared to peer companies, they have done far fewer layoffs across their lifespan and they have rock solid, wildly profitable business models.

Related resources:
- ["I want to land a job in a big tech as a SWE - How to do it?"](https://www.jointaro.com/question/MWJfUBnnUr8CKYFCO8bp/i-want-to-land-a-job-in-a-big-tech-as-a-swe-how-to-do-it/)
- ["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/)

"How can I help with what you guys are doing with Taro?" - 9/13/2022

- If you can afford it, please [join Taro Premium](https://app.jointaro.com/membership)!
  - If you work at a Big Tech company, there's a good chance you have L&D (learning and development) budget that you can use to expense Taro and pretty much get it for free! Here's a [template](https://docs.google.com/document/d/1xpY2XBKTpiMN-o7U2c1pvqai5afQSVIuGMgQZiB-_Rg/edit) you can share with your manager to get Taro reimbursed.
  - Here are the companies we know of that can reimburse Taro: Meta, Google, Amazon, Robinhood, Airtable, Yelp, Gusto, Shopify, Gusto, New Relic
- Send us your feedback!
  - As an early user of Taro, you have outsized power for taking a bet on us. We listen very closely to all user feedback at this stage.
  - On the mobile apps, we have a "Send feedback" button in your profile.
  - We're also on LinkedIn and the [Tech Career Growth Slack](https://join.slack.com/t/techcareergrowth/shared_invite/zt-lt2tbjcn-LOAVIDuGPI~nkuc4woHDLg).
- If the Taro's content is helpful for you, share it!
  - In the mobile apps, there's a share button on every Q&A and video.
  - We spent a lot of time on the underlying tech for this sharing, using something called "dynamic links". They work on every platform, matching the user to the Taro web app, iOS app, or Android app accordingly.
  - Fun fact: Taro content links will open up within the Android app after you install it and sign-in if you are shared a piece of Taro content and didn't have the app yet.
- If you're on Taro Premium, please share your perspective and answer questions! One of our core goals is to diversify the perspective on the platform.

Negotiation Course: Prefer Async Communication

Recruiters have much more information and practice with negotiation relative to job candidates. The pressure of a phone call and our desire to please others means that phone calls become dangerous places where engineers shoot themselves in the foot. Too many tech employees keep speaking on the phone call and end up revealing too much.

- Recruiters have orders of magnitude more knowledge about the job, the range of possible offers from the company, and even the range of possible offers are peer companies. 
- On the other hand, most job candidates have a handful of data points around their compensation could be, based on their past jobs and what their friends have told them.

This information asymmetry clearly favors the recruiter, who can read your emotions and take advantage of the knowledge gap to lowball you.

For that reason, you should prefer to eliminate phone calls or keep them short, and then be deliberate about your emails where you can craft the exact message you want to send. Async communication is also better for clarity and you can research on your own.

DSA Crash Course [Part 83] - Counting Change Approach

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

> Write a function, *counting_change*, that takes in an amount and a list of coins. The function should return the number of different ways it is possible to make change for the given amount using the coins.
>
> You may reuse a coin as many times as necessary.
>
> For example,
>
> counting_change(4, \[1,2,3\]) -&gt; 4
>
> There are four different ways to make an amount of 4:
>
> 1\. 1 + 1 + 1 + 1
>
> 2\. 1 + 1 + 2
>
> 3\. 1 + 3
>
> 4\. 2 + 2

```
counting_change(4, [1, 2, 3]) # -> 4
```

```
counting_change(8, [1, 2, 3]) # -> 10
```

```
counting_change(24, [5, 7, 3]) # -> 5
```

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

How To Be An Effective Tech Lead [Part 13] - Leverage The Power Of Feedback

Feedback is the main fuel you need to improve as a software engineer. It's especially important for tech leads as they are responsible for the well-being and productivity of many other people. This lesson teaches you:

- The proper mentality to have when it comes to feedback
- The right medium to deliver feedback based on its contents
- How to deliver feedback in a healthy way that doesn't hurt people
- What to do after receiving/delivering feedback to guarantee that it actually creates value

To dive deeper into how feedback is a gift, read through our excellent explainer here: ["Can someone elaborate on "always treating feedback as a gift"?"](https://www.jointaro.com/question/4DoEnMIq2ISadfAJuwp9/can-someone-elaborate-on-always-treating-feedback-as-a-gift/)

How To Be An Effective Tech Lead [Part 14] - Manage Expectations

As a tech lead, you will have a ton of things to do and not a ton of time. Because of this, you need to be crystal clear about what you're working on, why you're working on it, and when you're going to have that work done. This lesson teaches you:

- The danger and hugely negative consequences of mismanaging expectations
- Proactive mechanisms you can use to maintain alignment around expectations
- How to properly react and communicate when expectations are falling through

Understanding The $$$ Behind Stock Options - Hypothetical Startup Example

This video uses a hypothetical example from Carta to illustrate how startup stock options can lead to financial gain—or loss—depending on the company’s trajectory. It highlights both the upside potential of a successful IPO and the downside risk if the company underperforms.

- A fictional employee joins a startup, *Meatly*, in January 2020 and receives 16,000 stock options at a $1 strike price. After two years, 8,000 options (50%) have vested.
- When the company IPOs at $5/share, the employee exercises the options, spending $8,000 for shares now worth $40,000—a **$32,000 profit**.
- Alternatively, if the employee exercises at departure and the company later sells for only $0.75/share, the same $8,000 purchase yields **just $6,000 in value**, resulting in a **$2,000 loss**, not including taxes.
- This example underscores that **stock options carry real financial risk**, unlike RSUs, which are granted outright and do not require upfront payment.
- Employees need to carefully consider market performance and timing before exercising options to avoid losses.

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.