Master The DSA Interview [Part 21] - Programming Language Selection

There are a ton of programming languages you can use for a data structures and algorithms interview. This lesson teaches you:

- A basic flowchart to follow to determine which programming language you should use in data structures and algorithms interviews
- Why it's often not worth it to pick up an entirely new but "optimal" programming language for data structures and algorithms interviews
- How overly verbose languages can ruin your chances, explained with an in-depth example

How to Crack System Design Interviews - Part 4: Choosing Design Tradeoffs

When discussing design trade-offs in a system design interview, it's important to go beyond simply reciting known trade-offs. Instead, we take a more analytical approach:

- **Consider non-functional requirements:** We examine the impact of non-functional requirements, such as durability guarantees, on the system design and user experience.

- **Analyze access patterns:** We study how users interact with the system, considering the frequency of different API calls and their implications for optimization.

- **Make informed decisions:** Based on our analysis, we make conscious trade-offs, such as prioritizing read performance over immediate data consistency.

- **Use standard terminology:** We employ clear and concise engineering terms to ensure accurate communication and efficient use of interview time.

- **Be open to feedback:** We remain flexible and adjust our assumptions based on feedback from the interviewer, recognizing their expertise and knowledge of the system.

[Gaurav Sen](https://www.linkedin.com/in/gkcs/) has conducted 1000s of system design interviews while working at Uber and building his [YouTube channel](https://www.youtube.com/@gkcs) to 500K+ subscribers. His platform [InterviewReady](https://interviewready.io/?_aff=JOINTARO) combines video explainers, live Zoom classes, and an automated System Design Judge.

Grow From Junior To Mid-Level Engineer [Part 9] - Become A Go-To Person

One of the most obvious signs of engineer seniority is that everybody on their team goes to them for help with certain areas. More senior = more areas. This lesson teaches you:

- The easy way to understand the difference in mentality between junior and mid-level engineers when it comes to ownership
- How to become a go-to person for your area
- The one mantra you need to follow to organically deduce all the proper action items to become a go-to person

Speed run your way to becoming a go-to person with [Jordan's](https://www.linkedin.com/in/jordancutler1/) course: [Become The Go-To Expert As A Software Engineer](https://www.jointaro.com/course/become-the-go-to-expert-as-a-software-engineer/)

Negotiation Course: What If I HAVE To Give A Number?

A common complaint is that despite their best efforts, some tech workers are forced to give an expected compensation number to do a full interview at a company.

**Rebuttal #1**: You can just put a placeholder. e.g. put $1 for your salary expectation.

**Rebuttal #2**: Collect data from your network and provide a wide range. Ambiguity is your friend here, just talk about how compensation is one factor for you.

**Rebuttal #3**: Finally, even if you give a number you're unhappy with with, the interview is still good practice for you.

By the time you provide numbers, you ideally have done the legwork to know what to expect.

If you have to give a number, say the minimum number that is feasible for you. e.g. you need $250k TC to pay mortgage but the job's upper band is $180k)

SWE Internship Survival Guide [Part 4] - How Internships Work At Top Companies

Top-tier internships at companies like Meta or Google are structured, high-impact opportunities that can transform you into a confident, job-ready new grad. Here are the core points from this lesson:

- Legitimate internships at top companies have clear structure—interns are given managers, mentors, well-scoped projects, and timelines
- Interns are treated like junior engineers, often contributing to real production work and collaborating closely with full-time teammates
- Larger companies offer more formal evaluation processes for return offers, which helps reduce ambiguity and stress compared to smaller, less organized internships
- You’ll likely focus on one or two substantial projects to avoid context switching and to enable deeper, more meaningful contributions
- Adopt a collaborative mindset with fellow interns—success isn’t zero-sum, and sharing knowledge will help everyone grow and build stronger networks

Tech Lead Blueprint 5/17 - TL Duties

Connect with Lalit on LinkedIn: <https://www.linkedin.com/in/lalitkundu/>

Negotiation Course: Life After Joining

Our careers are long and the real hard work begins once we join a company. Beyond negotiation and compensation, there are many other factors that go into a fulfilling career, such as technology, network, and company culture. Compensation is one part of the job, but there are intangibles that are hard to measure. Don’t feel like you need to go for the highest number.

Once you join a company, learn how performance is evaluated and what makes up compensation. Prioritize people, learning, and culture for long-term career success.

Why Chasing Promotion Could Hurt You

Daniel has never gunned for a promotion when choosing teams or projects. In fact, he's actively turned down promotions he was offered at Microsoft and Meta (Philip Su famously down-leveled himself at Meta so he was no longer a Director). 

Here's why chasing a promotion could end up causing more stress and end up hurting your career in the long run. 

- Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)
- Videos from [Philip Su](https://www.jointaro.com/tagname/Philip%20Su/)

Related video: 
- [Taro Premium Session: Mentoring Meta Engineers From E3 -> E5](https://www.jointaro.com/lesson/EX9563YnxcJb62cCmetg/session-5-mentoring-junior-swes-e3-to-senior-e5-in-just-25-years-at-meta/)
- [Rockstar Software Engineer Story: SW2 -> Principal In Just 4 Years](https://www.jointaro.com/lesson/Lvf1TDKt1R4ZJSCr9BVv/rockstar-software-engineer-story-sw2-greater-principal-in-just-4-years/)
- ["Is there something as growing too quickly?"](https://www.jointaro.com/question/o9oyCcIjWT4Xa6w1Eau5/is-there-something-as-growing-too-quickly/)

Grow From Junior To Mid-Level Engineer [Part 10] - Be Vulnerable

As a junior engineer, you will have a lot of weaknesses. How you deal with them will greatly determine how fast you grow. This lesson teaches you:

- The definition of true strength and how it relates to being vulnerable
- A simple strategy to become very independent very quickly
- The difference in mindset when it comes to independence for junior engineers vs. mid-level engineers
- Why you can't solo-study your way towards becoming a great engineer

Ship & Grow 500k+ User Side Projects [Part 4] - Planning Your Initial Launch: API Example

You have now figured out what should go into your side project MVP (minimum viable product). How do you bring it to life? This lesson teaches you:

- The exact steps to follow to ship your MVP
- What good decomposition looks like, explained with an in-depth example

You can go deeper into the mechanics of software decomposition here: <https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/break-it-down/>

Negotiation Course: Negotiation Is All About Leverage

The idea of **BATNA** (Best Alternative To A Negotiated Agreement) is about your ability to walk away from a deal. It is "*the most advantageous alternative that a negotiating party can take if negotiations fail and an agreement cannot be made.*" This will dictate your success in any kind of negotiation.

**As soon as you want something too badly, and the other party knows that, you will be taken advantage of**. (This is also how Venture Capitalists operate, by the way.)

There are three ingredients needed to gain leverage (and therefore successfully negotiate): 

1. Time (patience)

2. Information

3. Options (leverage)

If you have all 3, you can walk into negotiations with confidence.

Onboarding Gives You Special Powers: Make Sure To Use Them

Most people view onboarding as a position of weakness: They don't know anything while the team knows everything, and now they need to bridge that gap. While that's somewhat true, onboarding is *not* a position of weakness, and thinking this will only make your onboarding slower and less effective.

Here are the core points from the video:
- **Nobody wants to be mean to the newbie** - This means that you have extra slack to ask questions and request help more aggressively than the average team member. However, this "aura" doesn't last forever - Make sure to really use it while you have it! The first month in particular is when the team will be extra accommodating of you.
- **You will never have fresh eyes again** - Being new gives you a perspective that tenured members of your team simply can't have. Use this to share new ideas and suggestions to the team: Tactically, you are very well equipped to improve the onboarding process. Don't only view onboarding as a state where you need to be dependent on others and consume help - Feel empowered to bring about positive change as well.

Related resources:
- ["How do you overcome the fear of asking stupid questions / bothering people when you need help?"](https://www.jointaro.com/question/vNE8kgpx2zdI1wACg9jA/how-do-you-overcome-the-fear-of-asking-stupid-questions-bothering-people-when-you-need-help/)
- ["What does it mean to not require handholding anymore?"](https://www.jointaro.com/question/5vEWajcZlSi7nlohTGtJ/what-does-it-mean-to-not-require-handholding-anymore/)
- ["I'm afraid of asking questions when I don't know how to start a new ticket - How to get over the fear?"](https://www.jointaro.com/question/ReLSgQGmVGlXkwrupN5T/im-afraid-of-asking-questions-when-i-dont-know-how-to-start-a-new-ticket-how-to-get-over-the-fear/)

DSA Crash Course [Part 73] - Minimum Change Approach

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

> Write a function *min_change* that takes in an amount and a list of coins. The function should return the minimum number of coins required to create the amount. You may use each coin as many times as necessary.
>
> If it is not possible to create the amount, then return -1.

```
min_change(8, [1, 5, 4, 12]) # -> 2, because 4+4 is the minimum coins possible
```

```
min_change(13, [1, 9, 5, 14, 30]) # -> 5
```

```
min_change(23, [2, 5, 7]) # -> 4
```

```
min_change(102, [1, 5, 10, 25]) # -> 6
```

```
min_change(200, [1, 5, 10, 25]) # -> 8
```

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

DSA Crash Course [Part 50] - Max Root to Leaf Path Sum Walkthrough

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

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

Break Into Tech And Become A Software Engineer [Part 18] - Work For Free

In this lesson, Brian discusses the value of working for free as a way to gain experience, while emphasizing that it’s not truly "free" but a trade for validation and learning.

This lesson covers:

- How free work is a way to gain experience and build credibility, but it’s essential to set clear deliverables and avoid being taken advantage of
- Approaching local businesses with well-defined projects to solve real problems, not just offering technical solutions, and using these opportunities to practice communication skills
- Sharing your experiences online, requesting recommendations, and using badges to validate your work and make yourself more attractive to future employers

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

Behind the scenes of a $320K → $1.05M negotiation in Silicon Valley

[Yogi Sharma](https://www.linkedin.com/in/yogi1/), an early employee at Facebook, shares an epic story about negotiating a massive compensation increase from his offer at Uber while discovering his true worth in the process.

---

I am a mathematician and engineer at heart, and I hate negotiations. I want people to evaluate the value of my work and pay me accordingly.

That is the mindset I had before this negotiation with a big ride-sharing company that opened my mind to the possibilities of a different way of operating.

In this candid behind-the-scenes conversation, I will discuss the mindset, preparation, and tactics that went into a negotiation (for the role of a SWE) that started at $320k and ended at $1.05M.

Even harder than doing such negotiation was the decision to decline such a lucrative job offer. (Thanks to that decision, I ended up finding my current profession.) Towards the end, I will also share my rationale behind such a seemingly crazy decision.

If you feel you are doing the work needed for a promotion or raise, but don’t seem to get it, this talk is perfect for you. I used to be that person and struggled to get the rewards I thought I deserved. This negotiation changed me deeply, and I hope to share a few insights that would help you too.

Connect with Yogi Sharma: 

- LinkedIn: <https://www.linkedin.com/in/yogi1/> 
- Taro: <https://www.jointaro.com/p/yogi-sharma/>

Master The DSA Interview [Part 25] - Do Mocks

Many engineers actually know all of the data structures and algorithms concepts, but they aren't able to bring that out during the live interview when it actually matters. Luckily, there's a solution for that. This lesson teaches you:

- Why there's a fundamental dynamic shift between studying data structures and algorithms and actually solving the problems in a live interview
- The many concrete differences between data structures and algorithms in study mode vs. live interview mode
- General tips on how to both give and receive a good mock interview
- What a quality data structures and algorithms interview scorecard looks like so you can create good ones when you give a mock interview

Find mock interview partners here: <https://www.jointaro.com/networking/?selectedServices=Mock+Interviews>

Supercharging Relationships - Building Bridges With Bosses, Teammates, Mentors, And Tech Leads

Discover the secrets to thriving in complex work environments by mastering the art of navigating workplace politics and dealing with difficult people! Jai explains the pioneering concepts in "Connect" by Dr. Carole Robin and Dr. David Bradford, as well as their acclaimed work at Stanford's Graduate School of Business on Interpersonal Dynamics.

Tailored specifically for engineers targeting senior levels, this masterclass will equip you with the skills and strategies to expertly handle challenging situations and personalities in the workplace. By attending, you will learn how to:
- Recognize and navigate the subtle complexities of workplace politics
- Understand and manage difficult people by identifying their motivations and triggers
- Build trust and create psychological safety with colleagues and superiors
- Effectively giving and receiving feedback
- Managing conflicts and promoting cooperation

Our expert-led session will provide actionable insights and practical tools that you can apply immediately to your professional life. Unlock your full potential by overcoming common obstacles and building strong, effective relationships with your colleagues.

Don't let workplace politics or challenging personalities hold you back. This session will let you take control of your professional success by mastering interpersonal dynamics!

This session was by HashiCorp full-stack engineer Jai Bhagat: [Connect With Jai On LinkedIn](https://www.linkedin.com/in/jaybhagat/)

To go deeper on the subject, here's more great resources around relationship building:
- ["How do you network effectively within a company?"](https://www.jointaro.com/question/DwT9GtdYK9nwFV3a7jrU/how-do-you-network-effectively-within-a-company/)
- ["Working with a micromanager"](https://www.jointaro.com/question/50HJtR05yMOB97LrkiCX/working-with-a-micromanager/)
- [[Masterclass] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

Grow From Senior To Staff Engineer [Part 14] - Raise Leaders

As a senior engineer, you are expected to make the engineers around you better. As a staff engineer, this expectation is amplified by another degree. This lesson teaches you:

- The difference in the levels of engineers that senior and staff engineers mentor
- The difference in mentorship depth between senior and staff engineers
- How to raise senior engineers
- What it looks like to give staff engineer level mentorship compared to senior engineer mentorship, explained with an in-depth example

Dive deeper into mentorship with this case study: [\[Case Study\] Mentoring Junior SWEs \[E3\] to Senior \[E5\] In Just 2.5 Years At Meta](https://www.jointaro.com/lesson/EX9563YnxcJb62cCmetg/case-study-mentoring-junior-swes-e3-to-senior-e5-in-just-25-years-at-meta/)

Get The Rating You Deserve [Part 7] - Build Relationships Proactively

**In this section, we'll explore the importance of building and nurturing relationships in your career.**

- **Proactive Relationship Building:** We emphasize the importance of building relationships before you need them, focusing on giving value and aligning goals.
- **Mindful Communication:** We discuss the power of effective communication, including active listening, empathy, and clear expression of needs and desires.
- **Leveraging Power for Good:** We explore how to use power to create positive change and foster strong relationships, rather than for personal gain.
- **Overcoming Pitfalls:** We identify common pitfalls in relationship building, such as impatience and a short-term focus, and provide strategies to avoid them.
- **Practical Tips:** We offer actionable advice, such as dedicating time to relationship building, seeking out opportunities to help others, and practicing empathy and understanding.

If you want to get personalized support from Yogi, you can reach out to him at [coaching@yogisharma.com](mailto:coaching@yogisharma.com) or schedule an introductory call to dive into your situation at <https://tinyurl.com/meetyogi>.

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.