Master The DSA Interview [Part 16] - Alternate Approaches

The beautiful (and sometimes frustrating) thing about software engineering is that almost every technical problem has a ton of possible solutions. This lesson teaches you:

- Why being able to come up with alternate approaches is so important as a software engineer at the top level
- How to have a proper discussion with your interviewer about alternate approaches
- What a great alternate approach discussion looks like, discussed with an in-depth example

Dive deeper into real system design here: [\[Course\] System Design Masterclass: Shipping Real Features To Production](https://www.jointaro.com/course/frontend-system-design-masterclass-building-playlists/)

Master The DSA Interview [Part 9] - Outline Your Approach

Once you have clarified exactly what you need to deliver with a data structures and algorithms interview problem, you need to figure out how to deliver it. This lesson teaches you:

- How to come up with a data structures and algorithms solution plan
- The many benefits of coming up with a plan proactively
- What a good data structures and algorithms plan looks like, explained with an in-depth example

Master The DSA Interview [Part 8] - Clarify The Problem

Don't just start coding when you get a data structures and algorithms problem in an interview. This lesson teaches you:

- The first thing you should do when getting a data structures and algorithm problem, which is critical for setting you up for success
- Why dealing with ambiguity is so important as an engineer
- The overall question categories you should pull from when clarifying a problem
- How exactly to clarify a data structures and algorithms problem, shown with an in-depth example

Top System Design Interview Mistakes [Part 14] - Don't Save the Hardest for Last

In this lesson, we focus on the importance of addressing the most challenging aspects of a system design problem early on:

- We often make the mistake of delaying the hardest parts of the problem. While starting with simpler tasks might seem productive, it can lead to incorrect design choices and suggest we're unaware of the core challenges

- We should immediately focus on the most complex parts of the problem. Tackling these challenges first demonstrates our understanding and prevents us from getting sidetracked by less critical aspects

- In our interview example, we show how the candidate misses the core problem behind the messaging app, tackling the simpler pieces instead

- Effective problem solving involves working through strategies for the hardest issues, like the message-to-notification fan-out, and evaluating their pros and cons

- By focusing on the toughest problem first, we show strong judgment and prioritization skills. This approach ensures that we manage our time well and address the most critical aspects of the design effectively

If you need extra help with your system design interview, [Formation.dev](https://formation.dev/partners/taro) can provide you hands-on, personalized support. Join us here: <https://formation.dev/partners/taro>

Top System Design Interview Mistakes [Part 13] - Identifying Key Issues

In the final segment of the system design series, we focus on the importance of driving the design of your system during interviews. In this video, we cover how to identify key issues. Here's the video's core points:

- Avoid following a rigid structure. For example, don't just jump into a data model or architectural diagram without considering the unique requirements of the system you're designing, such as group messaging dynamics
- Actively ask clarifying questions to understand the requirements better. This helps in identifying and addressing key issues specific to the problem, rather than sticking to a generic approach
- Tailor your approach based on the specifics of the problem. If dealing with a unique system, like a group messaging app, adapt your design to handle unique challenges, such as managing multiple notifications from a single message
- Lead the discussion by probing into requirements and challenges. This ensures that your design addresses the most critical aspects of the problem

If you need extra help with your system design interview, [Formation.dev](https://formation.dev/partners/taro) can provide you hands-on, personalized support. Join us here: <https://formation.dev/partners/taro>

[Become A Go-To Person 2/18] What Industry Experts Say

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

[Timeless Career Advice] IC vs Manager

This video discusses how much the software industry pays in the US in terms of total compensation. 

In addition, we discuss the decision to be an individual contributor vs engineering manager.

Connect with Louie:

- SmallBets community: [**https://smallbets.com/?utm_source=taro**](https://smallbets.com/?utm_source=taro)
- Twitter: [**https://twitter.com/LBacaj**](https://twitter.com/LBacaj)
- LinkedIn: [**https://www.linkedin.com/in/louiebacaj/**](https://www.linkedin.com/in/louiebacaj/)
- Newsletter: [**https://newsletter.memesmotivations.com/**](https://newsletter.memesmotivations.com/)

Write A Stellar Resume As A Software Engineer [Part 17] - Projects

In this day and age, 99% of software engineers have a "Projects" section on their resume. Of those engineers, 90%+ of them won't get any benefit from their "Projects" section when it comes to their resume passing the recruiter screen and getting them an interview. This lesson teaches you:

- Why projects are at a natural disadvantage compared to work experience on your resume
- What it takes to make a personal project actually impressive on your resume
- The proper link to include to show your project
- How to make a project GitHub actually have the chance to impress a recruiter and get you an interview

To get more users on your side project: ["\[Side Project\] How to get more users + interviews?"](https://www.jointaro.com/question/Z456XTkusKszxcHjVfYA/side-project-how-to-get-more-users-interviews/)

Write A Stellar Resume As A Software Engineer [Part 4] - 1 Resume To Rule Them All

Writing tons of different resumes is one of the easiest ways to waste time and overwhelm yourself on the software engineer job search. This lesson teaches you:

- Why you should only have 1 resume, especially if you're an earlier-in-career engineer
- Why "full-stack" engineer is often a trap for more junior engineers
- How to figure out the 1 resume you should write
- What to do if you really can't write just 1 resume (i.e. how to break the tie)

Grow From Mid-Level To Senior Engineer [Part 22] - Instagram Ads Survey Cleanup Workstream

See something, say something: You'll be surprised at how much opportunity you can find by championing this mentality, including to senior levels. This lesson goes through:

- The weird organizational dynamic that led to a bunch of senior scope existing "for free" but easy to ignore as a junior or mid-level engineer
- The simple but powerful trick Alex used to turn several smaller issues into a senior-level project
- How Alex continued to deepen the impact of this survey cleanup workstream by digging deeper and doing the right thing
- The learnings from this case study that you can apply to your day-to-day to find senior scope

Grow From Mid-Level To Senior Engineer [Part 21] - Instagram Ads Testing Tool

Sometimes being a little selfish can help you tremendously when finding senior scope as it did in this case study. This lesson goes through:

- The problem Alex was solving with Instagram ads internal testing, particularly with mobile engineers
- How Alex came up with a very simple solution to the testing problem (far simpler than senior engineer technical complexity)
- How Alex scaled both himself and his basic Instagram ads testing tool
- The learnings from this case study that you can apply to your own day-to-day at work to find senior scope

Master The Behavioral Interview [Part 20] - Write Stuff Down

Writing English is far more important than writing code, and this applies to mastering the behavioral interview as a software engineer as well. This lesson teaches you:

- How to create a powerful Q&A database to master the behavioral interview
- What you should be remembering from your written preparation vs. not

Master The Behavioral Interview [Part 19] - Cultural Values

Culture fit is real. A lot of tech companies have toxic culture and don't vet for it properly, but that doesn't change the fact that culture fit is extremely important to running a healthy engineering organization. This lesson teaches you:

- Why cultural values are important
- What you should do to effectively study and internalize the cultural values of a company you are interviewing with
- How to weave a company's cultural values into your behavioral interview answers through an example with Alex for his Meta interview

If you're curious as to how Meta's engineering culture works: ["Is sprint planning and agile not a thing at Meta?"](https://www.jointaro.com/question/tB7borE2AWb1KcuFEcon/is-sprint-planning-and-agile-not-a-thing-at-meta/)

Master The Behavioral Interview [Part 12] - Double Dip

Software engineers and people in general don't realize how incredibly powerful questions can be when you ask the right ones. This lesson teaches you:

- How the best questions that you can ask in a behavioral interview actually help you pass on top of extracting useful team selection information
- What the 2 core failure modes are when it comes to you asking the interviewer questions

Nail Your Promotion As A Software Engineer [Part 21] - Attribution

The best software engineers don't need to be told what to do; they're able to come up with impactful projects on their own. This lesson teaches you:

- Why ideas are worthless and how engineers can come up with great ideas and get 0 credit for them
- The hard work you need to do to convert an idea into an actual roadmap project
- What it takes to get massive credit on the attribution axis for projects

Here's the case study Alex referred to in this lesson: [\[Case Study\] Revamping Oncall For 20 Instagram Engineers - Senior to Staff Project](https://www.jointaro.com/lesson/esVxIGXYC5BdgxXUkO6H/case-study-revamping-oncall-for-20-instagram-engineers-senior-to-staff-project/?playlistId=EWIo3USNcsgXbCs5PS0h)

Nail Your Promotion As A Software Engineer [Part 14] - Observe Other Engineers

Don't know what you need to do as a software engineer to get promoted? Observe engineers who are better than you! However, this is a surprisingly difficult skill to develop. This lesson teaches you:

- Which engineers you should observe and how to find them
- What you should be looking for when observing other engineers
- What "silent hero" work is and how very senior engineers do a lot of it
- The concrete avenues you should look at when trying to figure out why a higher-level engineer is superior to you
- Why getting jealous of engineers above you is a colossal waste of time, even if you are truly better than them

From Multiple Rejections to Landing Six Offers and Negotiating A $100K Raise

*Unlock all events and courses with Taro Premium. Join at a discount with Yogi's link: [**https://www.jointaro.com/r/yogi-sharma/**](https://www.jointaro.com/r/yogi-sharma/)*

In 2017, amidst the bustling innovation and relentless pace of Facebook, I encountered a pivotal moment in my career. The sting of receiving not one, not two, but three job rejections in as many weeks (and *first round rejections* at that) set the stage for a profound professional transformation. This period, marked by deep introspection and resilience, was not just about coping with disappointment; it became a launchpad for unprecedented growth and success.

But all that came after an initial period of dejection.

The journey from those initial rejections to eventually landing six coveted job offers, with negotiations exceeding $100k, is a testament to the power of strategic habit shifts and mindset realignment. The experience, while daunting, unfolded the essential principles of leveraging one’s time and energy efficiently, ensuring readiness for job transitions *without compromising current job performance*.

In this talk, I aim to demystify the path from setback to success. I will unveil the practical strategies and mental adjustments that not only helped me navigate the turbulent waters of job searching but also equipped me with the tools to excel beyond expectation, which I have used in my work with over 400 professionals in my coaching practice. This narrative is more than a personal victory; it's a blueprint for anyone facing the disheartenment of rejection, providing actionable insights to transform challenges into opportunities for substantial growth and achievement.

Join me as I dissect the critical principles, mindset shifts, and habit changes that can empower us all to turn job search woes into wins, illustrating that with the right approach, navigating the job market can be a journey of triumph even though tribulation are inevitable at times.

Negotiation content on Taro:

- [**\[Taro Top 10\] Pay Negotiation**](https://www.jointaro.com/playlist/uyWSc5q79zFw2Ei7w59d/)
- [**\[Masterclass\] Understanding And Optimizing Your Pay In Tech**](https://www.jointaro.com/lesson/gk408yBIV2fa5RjVR213/masterclass-understanding-and-optimizing-your-pay-in-tech/)

Yogi's next event about going from the PIP danger zone to a top performer: [**https://www.jointaro.com/event/behind-the-scene-from-meets-most-greatly-exceeds-in-3-months-at-facebook/**](https://www.jointaro.com/event/behind-the-scene-from-meets-most-greatly-exceeds-in-3-months-at-facebook/)

Yogi on LinkedIn: <https://www.linkedin.com/in/yogi1/>

Failure Mode: Excessive Handholding

A common failure mode of onboarding is that, even 6 months into the job, the engineer still needs support to make code changes. Either with their workflow or a technical question about the code.

The sign of progress as you ramp up is if your questions and code reviews are evolving over time. The types and depth of interaction you have with coworkers should change.

The key to doing this is to reflect:

- Look at earlier code comments you received
- Write down questions you’ve had
- Don’t make the same mistake twice
- Ask your onboarding buddy to look for patterns

Reference question: [What does it mean to not require handholding anymore?](https://www.jointaro.com/question/5vEWajcZlSi7nlohTGtJ/what-does-it-mean-to-not-require-handholding-anymore/)

Ace Your Tech Interview As A Software Engineer [Part 21] - Recruiter Screen

Having a recruiter talk to you is one of the most common ways tech companies start the interview process for software engineers. Here's the thing: These recruiter screen ones can be surprisingly tricky for many software engineers. This lesson teaches you:

- When recruiter screens happen
- How difficult recruiter screens can be, how often software engineers fail them, and why many software engineers are terrible at them (when they really shouldn't be)
- What to expect in a recruiter screen so you can pass it with ease

Ace Your Tech Interview As A Software Engineer [Part 11] - Struggling? Send More Applications

One of the most common reasons for a struggling software engineer job search is that they simply aren't applying enough. The good news is that this can be easily fixed with the proper behavior adjustments. This lesson teaches you:

- How you can conquer the job search with sheer math
- A healthy conversion rate for application -&gt; interview chance
- Why you should almost never spend too much time on any individual application (quantity &gt; quality)
- The framework to follow on whether you should apply a ton or apply more selectively

Here are the Big 2 job searching websites:

- <https://www.linkedin.com/jobs/>
- <https://wellfound.com/>

On top of the Big 2, we've seen engineers have success with:

- <https://otta.com/>
- <https://www.workatastartup.com/> - Jobs at Y Combinator startups specifically, the greatest incubator in the world which is behind Stripe, DoorDash, Airbnb, and many more FAANG-adjacent companies

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.