Get The Rating You Deserve [Part 6] - Slow & Steady

**In this section, we'll delve into the importance of patience and strategic thinking in career advancement.**

- **The Power of Patience:** We'll discuss the significance of taking a long-term perspective and understanding that significant growth often requires time and consistent effort.
- **Balancing Exploration and Exploitation:** We'll explore the delicate balance between learning and applying knowledge, and how to effectively allocate time to both.
- **Mindful Communication:** We'll emphasize the importance of clear and effective communication, both in expressing your desires and in actively listening to others.
- **The Role of Mindset:** We'll discuss the importance of cultivating a growth mindset, embracing challenges as opportunities for learning, and maintaining a positive outlook.

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

Grow From Junior To Mid-Level Engineer [Part 11] - Ask Great Questions

In order to grow fast as an engineer, you need to ask a lot of questions. This lesson teaches you:

- The differences between junior and mid-level engineers when it comes to asking question, particularly question quality
- What a junior engineer question looks like vs. a mid-level engineer question
- How to demonstrate technical mastery in your questions to make yourself look even better when asking for help

Master the art of question asking with our course: [Ask Great Questions That Get Great Answers Quickly](https://www.jointaro.com/course/ask-great-questions-that-get-great-answers-quickly/)

DSA Crash Course [Part 55] - Undirected Path Approach

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

> Write a function, *undirected_path*, that takes in a list of edges for an undirected graph and two nodes (\*node_A\*, *node_B*). The function should return a boolean indicating whether or not there exists a path between *node_A* and *node_B*.

```
edges = [
('i', 'j'),
('k', 'i'),
('m', 'k'),
('k', 'l'),
('o', 'n')
]

undirected_path(edges, 'j', 'm') # -> True
```

```
edges = [
('i', 'j'),
('k', 'i'),
('m', 'k'),
('k', 'l'),
('o', 'n')
]

undirected_path(edges, 'm', 'j') # -> True
```

```
edges = [
('i', 'j'),
('k', 'i'),
('m', 'k'),
('k', 'l'),
('o', 'n')
]

undirected_path(edges, 'l', 'j') # -> True
```

```
edges = [
('i', 'j'),
('k', 'i'),
('m', 'k'),
('k', 'l'),
('o', 'n')
]

undirected_path(edges, 'k', 'o') # -> False
```

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

Amazon Behavioral Interview [Part 5] - Stakeholder Management (Answer)

This video segment focuses on the interviewee's approach to stakeholder management.

- **Experience:** The interviewee highlights their experience managing global and cross-functional teams, emphasizing their ability to navigate complex situations with multiple stakeholders.
- **Example: Prioritizing Customer Support:** The interviewee describes a specific example at Tableau where they led an initiative to change the customer support prioritization system. This involved gathering input from various stakeholders (sales, support, finance) and addressing their concerns.
- **Challenges:** The interviewee acknowledges the challenges of balancing the needs of different stakeholders, particularly the conflict between prioritizing high-value enterprise customers and maintaining support for smaller businesses.
- **Strategies:** To address these challenges, the interviewee emphasizes the importance of:
  - Understanding the goals and priorities of each stakeholder.
  - Using data and facts to support decisions.
  - Building consensus through clear communication and collaboration.
  - Seeking support from key leaders (e.g., the Chief Revenue Officer) to help address resistance from certain stakeholders.
- **Key Takeaway:** Effective stakeholder management requires strong communication, active listening, and the ability to navigate conflicting priorities while maintaining a focus on overall business objectives.

Learn more about Alan's job search program, Kadima Careers, using this [discount link](https://signup.kadimacareers.com/mQBsDvu).

Negotiation Course: Get Other Offers

Researching data points is helpful when constructing a negotiation argument, but the **best** argument you have is an offer in hand from a comparable company. 

The big mistake most tech workers make is to be reactive with recruiters. If you decide to interview with a company, figure out comparable companies and apply to them as well. (Google and a seed-stage startup are not comparable.)

Talking to many recruiters and companies at once is painful, but it's better to concentrate the pain in a short window, rather than spreading it across several months. You can also negotiate interview dates, though this is admittedly harder in a bad economy.

As soon as you have a verbal offer, push all your other loops to skip you to onsite using that as leverage ("Don't let the awesome candidate of me get away!").

Grow From Junior To Mid-Level Engineer [Part 18] - Done Is Better Than Perfect

We all make mistakes. In fact, we'll all make a lot of mistakes as software engineers, especially when we're junior. This lesson teaches you:

- The many types of dumb things you will inevitably do as a junior engineer (and continue doing as a mid-level/senior/staff/principal engineer)
- The simple growth mentality and formula you should follow to speed run the junior to mid-level engineer
- Why it's awesome to be the dumbest person in the room
- A simple mathematical way to understand the difference between a fast-growing junior engineer and a slow-growing junior engineer

Learn how to learn from your mistakes here: ["How to turn a string of silly mistakes into a mature positive outcome?"](https://www.jointaro.com/question/JybGyc935lsYbM8dAo7Y/how-to-turn-a-string-of-silly-mistakes-into-a-mature-positive-outcome/)

Why Infrequent Manager 1 on 1s Severely Hurt Your Career

True or false: Delayed and infrequent manager 1 on 1s can seriously affect your career growth long-term.

Why is it crucial to have frequent, consistent 1 on 1 meetings with your manager?

Recurring one-on-ones act as a safeguard against the buildup of unresolved issues and help maintain consistent focus on career development and workplace health.

- **Prevents goal procrastination**: Infrequent one-on-ones make it easy to delay important but uncomfortable topics like career growth. Weekly cadence creates timely check-ins that keep development top of mind.
- **Creates built-in accountability**: Knowing a one-on-one is coming up each week reinforces reflection on progress and keeps both parties aligned on priorities and goals.
- **Maintains workplace “cleanliness”**: Like cleaning a home regularly, weekly meetings prevent work challenges from piling up. When issues are cleared consistently, the work environment stays healthy and manageable.
- **Supports better quality of work life**: Regular check-ins help address interpersonal or project-related friction early, reducing stress and misalignment over time.
- **Reduces communication lag**: By clearing the "trash" of misunderstandings or confusion regularly, one-on-ones create a more fluid and responsive working relationship.

How Does FAANG Hire? What Big Tech Recruiters Look For

[**Nikita Gupta**](https://www.linkedin.com/in/guptanikita16/) worked as a Senior Technical Recruiter at Uber and Amazon with 3+ years of recruiting and hiring experience. She extensively used applicant tracking systems (ATS) to search for the right candidates and hire them.

Nikita is an expert in helping candidates create better resumes and LinkedIn profiles in order to land more job opportunities. Her company [CareerFlow.ai](https://www.careerflow.ai/?via=taro) does exactly this.

As a full-cycle recruiter with experience in Big Tech and startups, Nikita will talk about how FAANG companies hire, and what misconceptions engineers often have when applying to jobs. She'll cover:

- Does "keyword stuffing" in resumes increase the chance of getting an interview?
- What are the top 3 things a recruiter looks for when opening a resume?
- How much does the recruiter screen matter in the overall interview process?
- How much does your LinkedIn matter in the job search?

Discounts for CareerFlow.ai's resume review service are available from the [perks page](https://www.jointaro.com/perks/). Use code `TARO` on [CareerFlow](https://www.careerflow.ai/resume-review?via=taro). 

Additional resources:

- [**\[Taro Top 10\] Effective Interview Prep**](https://www.jointaro.com/playlist/HLBYxJI7D1j8STolrwum/)
- [**\[Masterclass\] How To Write A Stellar Tech Resume That Gets You More Job Opportunities**](https://www.jointaro.com/lesson/OnQV2V3J8DYVBBuGbZx6/masterclass-how-to-write-a-stellar-tech-resume-that-gets-you-more-job-opportunities/)
- [**\[Masterclass\] How To Ace Your Big Tech Interview - Data Structures And Algorithms**](https://www.jointaro.com/lesson/V4sTACzfOh22nMVcUV3w/masterclass-how-to-ace-your-big-tech-interview-data-structures-and-algorithms/)

Become An Open Source Master [Part 10] - How To Evaluate A Project’s Health

We can evaluate potential open-source projects by examining their issues and community interactions:

- **Analyze the Issues tab**: Look for a healthy ratio of solved to open issues, evidence of tagging and triage, and positive community engagement. Check for responsiveness to older issues.
- **Observe conversations around issues and pull requests:** Get a sense of the community's dynamics, code quality standards, and how welcoming they are to new contributors.
- **Check the Discussions tab (if available):** See how the community debates future changes and get a feel for the project's overall vibe.
- **Utilize the Insights tab:** Look at statistics like open and closed pull requests, active issues, and contributors to gauge the project's activity level.

Connect with James: 

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

Grow From Senior To Staff Engineer [Part 13] - Bring Teams Together

Just because you're leading a team's worth of engineers doesn't mean that you're a staff engineer. This lesson teaches you:

- The difference between senior and staff engineers when it comes to the number of stakeholders on their projects
- The difference between senior and staff engineers when it comes to the depth of their XFN (cross-functional) collaboration
- How to align multiple teams, even those you aren't very familiar with

Master The DSA Interview [Part 13] - You Must Be Fast

Quality is important, but quantity is too, which is mainly demonstrated with velocity. This lesson teaches you:

- Why raw speed is so important with data structures and algorithms interviews in particular
- The quantity bar you need to hit to pass a data structures and algorithms interview the vast majority of the time
- Why interviewers often ask 2 data structures and algorithms problems in a single round
- How an interviewer asking you a harder data structures and algorithms could actually mean that they're trying to save you
- Tips for getting faster at data structures and algorithms

DSA Crash Course [Part 42] - Breadth First Values Walkthrough

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

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

How To Maximize Your Peer Feedback Impact And Build Stronger Relationships

- Like everything else in life, peer feedback follows The Golden Rule: If you want good feedback from your peers, you should write good feedback for them.
- If a peer feedback request doesn't have a specific ask, proactively ask your peers what they want your feedback to focus on. This really shows your peers that you care deeply about them as performance review is such a core part of every employee's life.
- Writing very powerful, salient feedback for your peers on this crucial stage of performance review is one of the effective ways to build immense social capital.

Engineer Your Ideal Tech Career [Part 7] - What's Your Specialization?

In this video, we walk through three (of many) specializations you can pursue, what type of work you may be working on in each, and who its a good fit for based on the work you like to do.

These are just three of many; each of these buckets are massive and cover a lot (while also having distinct sub-categories in each):

- Frontend/mobile
- Backend
- Generalist

Looking for mentorship from tech’s top engineers + personalized job hunt assistance and interview prep? [Formation.dev](http://Formation.dev) can provide you unlimited career coaching, technical mentorship, personalized practice, and mock interviews. Join us here: <https://formation.dev/partners/taro>

Worksheet: [Formation - Coding Your Career](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/courses%2Fslides%2FFormation%20Career%20Direction%20Worksheet.pdf?alt=media&token=f6344b78-529a-411e-a449-7a34a8d55fc8)

Tips On Navigating RSUs

This video highlights the complexity of **RSUs (Restricted Stock Units)** in tech compensation, emphasizing how RSUs introduce elements of personal investing into salary evaluation. Understanding how stock fluctuations affect total pay and managing risk becomes crucial.

- **Evaluating RSUs is similar to investing**, since compensation becomes tied to the company's stock performance. Joining when stock prices are low can lead to significantly higher gains if the stock appreciates.
- **Choosing a company means essentially “buying” into its future**, since RSUs form a large part of total compensation. A rising stock price increases income; a falling one diminishes it.
- **There is no universal rule for managing RSUs**, as financial goals and risk tolerance vary by individual. Compensation strategies should reflect personal financial context.
- **Some employees choose to sell RSUs immediately upon vesting**, aiming to diversify rather than concentrate risk. This reduces financial dependency on a single company’s performance.
- **Investing RSU proceeds into diversified assets like S&P 500 index funds** is a common approach for those seeking more stability and reduced exposure to employer stock.

Grow From Junior To Mid-Level Engineer [Part 13] - Be A Feedback Sponge

We all have blind spots, and you need feedback to see them. Getting feedback is especially important as an engineer given how information-dense the software field is. This lesson teaches you:

- Why a surprising amount of junior engineers are terrible with feedback
- Why you should almost never push back against feedback you disagree with
- How not being good with feedback can severely damage your career, explained with an in-depth example
- The differences between junior and mid-level engineers when it comes to handling feedback

For additional inspiration on truly becoming a feedback sponge, check out the words of wisdom from OpenAI ChatGPT engineer [Philip Su](https://www.linkedin.com/in/suphilip/) here: ["What's the core insight behind quick growth?"](https://www.jointaro.com/question/nJ762p255cGyuth36H6w/whats-the-core-insight-behind-quick-growth/)

This Is The Easiest Way To Get Better At Debugging

Before you go into any bug, it's important to write down all the relevant details into a task or ticket. Here's why:
- It makes it easier to get your bearings and start looking into the right places for debugging
- If you need to pass the bug to someone else, the knowledge transfer is much smoother as you have this artifact
- The written context will be very valuable for retrospectives

Here's the information you should put down:
- Steps to reproduce the issue
- The blast radius
- Relevant code pointers
- Priority of the bug

This video is a clip from our debugging masterclass. You can watch it here: [[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/)

Related resources:
- [[Case Study] Solving A Multi-Million $$ Instagram Bug](https://www.jointaro.com/lesson/WYk4J05iBqOuPtD0CYKX/case-study-solving-a-multi-million-dollardollar-instagram-bug/)
- ["How can I become more independent and better at unblocking myself with tricky technical issues?"](https://www.jointaro.com/question/QhqQQGrDgFjZbqohpKe0/how-can-i-become-more-independent-and-better-at-unblocking-myself-with-tricky-technical-issues/)
- ["What is the effective way to understand new repository in order to make the required changes in that repo?"](https://www.jointaro.com/question/KoxB3UU2zWC9pdYU6Rx0/what-is-the-effective-way-to-understand-new-repository-in-order-to-make-the-required-changes-in-that-repo/)

The Best Programming Languages For Interviews

- Try to use a more concise language like Python if possible. This is because interviews, DSA rounds in particular, are a precise time management exercise.
- However, if you are *very* familiar with a certain language, use that. The exception is if that language is very verbose like C.
- Avoid the trap of using a rarer, "fancier" language. It may cost you time to explain, and if you aren't actually that knowledgeable in it, you may get called out.

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 12] - System Design

System design is a crucial interview round, because it's both technical and actually needed on the job (unlike data structures and algorithms). This lesson teaches you:

- What a system design interview is looking for
- What not to do in a system design round
- How to learn system design organically

To dive deeper into system design interviews, take our course here: [How To Crack System Design Interviews As A Software Engineer](https://www.jointaro.com/course/how-to-crack-system-design-interviews-as-a-software-developer/)

Grow From Senior To Staff Engineer [Part 12] - Become The PM Right Hand

As a staff engineer, you need to have far more influence on the direction of the product, especially if you work on a product-facing team. This lesson teaches you:

- The difference in the depth of collaboration with the product manager between a senior engineer and a staff engineer
- Why staff engineers often need to partner closely with their product manager
- Which teams place more value on the engineer &lt;-&gt; product manager relationship
- What you should do to deepen your relationship between you and your product manager

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.