Ace Your Tech Interview As A Software Engineer [Part 30] - Talk To Your Recruiter

Too many software engineers see the tech recruiter as the enemy when they really shouldn't be. In reality, one of the core keys behind a successful interview loop is leveraging your recruiter optimally. This lesson teaches you:

- How to understand the world through the eyes of a recruiter, particularly when they have given you a chance and let you into their company's interview process
- Why software engineers usually fail to collaborate with their recruiter properly to maximize their chances of passing the interview
- The true cost of interviewing a software engineer (it's probably higher than you realize)
- How you can reach out optimally to recruiters to figure out what's going to be on your upcoming interview with an in-depth message example

Ace Your Tech Interview As A Software Engineer [Part 14] - Referrals

Having a current employee put you into their hiring pipeline via a referral is one of the most powerful ways to level up your job search. However, referrals are often misunderstood by software engineers. This lesson teaches you:

- The 2 different types of referrals and which one is better (spoiler: engineers usually struggle getting the better one)
- The massive difference between *weak referrals* and *strong referrals*
- Why you are more special than you realize and how you can leverage that to get more strong referrals
- How to approach professional networking properly to cultivate huge amounts of strong referrals over time

To help you get strong referrals, check out our networking course: [Networking Guide: Build Deep Relationships Quickly In Tech](https://www.jointaro.com/course/networking-guide-build-deep-relationships-quickly-in-tech/)

How Rigid Should You Be With Your Coding / Content Schedule?

As a 17 year veteran of Amazon, Steve understands seasonality. Q4, the holiday season, is crunch time. There’s a huge pressure on Amazon employees to keep up with demand, and engineers will routinely spend long hours to ensure stability and quality.

The key to doing sustained creative work is to lean in and lean out of periods of intense work, at the right times. Amazon employees know that Q4 will end, and therefore, the crunchtime will end within a few months.

Similarly, for content creation or writing code, **it’s important to segment your schedule into chunks where you can create a deadline or “crunch time”.**

Another perspective is to think about quantity vs quality. For your side projects or content creation endeavors, it’s worth being rigid for a bit (“a commit everyday” or “a video every week”), but it’s also worth changing the routine after some time.

Burnout happens when people don’t see an end in sight from a stressful period. 

- [Learn about burnout](https://www.jointaro.com/lesson/xsbM1ctL9HYa6d7E9ejh/the-silent-killer-of-too-many-software-engineer-careers-burnout/)
- [Avoid burnout](https://www.jointaro.com/question/CfPvvtIW02MxVwR1fnP4/how-can-i-avoid-burning-myself-out/)
- [3 Mistakes Engineers To Avoid (from an Eng Director)](https://www.jointaro.com/lesson/lhj2batcsdMiEOSKOGLo/3-mistakes-too-many-software-engineers-make-from-a-director-at-airbnb/)

Connect with Steve: 
- [Taro](https://www.jointaro.com/profile/aZJL3ucq9dQnscO09F4JDRkgPo72/)
- [YouTube](https://www.youtube.com/@ALifeEngineered)

"Why is Taro named Taro?" - 9/13/2022

- Here are the 3 main constraints we had on a name:
  - It should be short (4-8 characters).
  - There should be a good domain for it, ideally a ".com" website URL.
  - It should have positive associations.
- The reason it took 3 months to find a name for our product and company after we quit our jobs is because we spend the first 3 months thinking about what idea we wanted to do.
- "Tech Career Growth" is a wonderful name for our free community, but it's not a great product name as it's too long and too literal.
- We took ~3 weeks to decide on a name. Here was our process:
  - Come up with guiding principles for the name (covered above)
  - Brainstorm a bunch of names (100+)
  - Narrow it down to ~8 based on the above principles
  - Make a deck with the final candidates, weighing pros and cons
  - Have a couple rounds of discussion/debate to pick 1 name
- You can think of "Taro" as a similar play to "Apple". Doesn't really describe what the product is, but it's a food with positive associations and a short name.
- The logo is a "T" and has additional symbolism by looking like roads. Our goal with Taro is to help you **navigate** your career!

[Part 1] Meta Intern Success Series - Internship Program Overview

- The Meta software engineer internship program is very legit. It resembles the experience of working as a full-time Meta engineer as closely as possible, complete with calibrations and a formal manager.
- The program is also hard. The pass rates that got mentioned around the company were 50 to 75%. It's one of the harder software engineer internships to get a return offer from as the goal is to perform at E3 MA. If this is your first software engineer internship or you have only interned at companies weaker than Meta prior, the high bar can be overwhelming.
- However, the reward is tremendous. Meta is an incredible company to work at and amazing as a career starter. Meta is also one of the highest paying companies for the entry-level band (E3), and the signing bonus for return offer interns is sky-high (60k to 100k).
- 4 outcomes for Meta software engineer interns:
  - No offer: As mentioned before, many interns will unfortunately be here. The numbers after this correspond to the percentage of the "surviving" pool.
  - MA (70%): "Meets All Expectations", which is a regular return offer. The vast majority of successful software engineer interns get this. 
  - EE (25%): "Exceeds Expectations", which is given to very strong interns.
  - Rockstar (5%): For interns that completely crush it and are very close to functioning as a mid-level engineer (E4).
- Internship schedule (assuming standard 12 week length):
  - Weeks 1-3: Onboarding
  - Weeks 5-6: Mid-cycle review
  - Weeks 10-11: Final calibrations (return offer is decided here)
  - Weeks 11-12: Relax and have fun. Only your performance from Weeks 1 - 10 is counted towards your final review
- As a software engineer intern, you formally report to an intern manager (IM), which is shown on the org chart. On top of the IM, you will have 1-3 other peers who will review your diffs and help you. During calibrations, feedback from your IM and these peers will determine your final rating.

For more expert internship advice: [Full SWE Intern Advice Playlist](https://www.jointaro.com/topic/software-engineering-intern/)

The Best Gift You Can Give Yourself When It Comes To Productivity

Which of these is the best gift you can give yourself when it comes to productivity?

True or false: Phones are great productivity tools as they allow us to accomplish almost anything in a really convenient way. This is why we should make sure that we always have our phones close by as we are working.

Where should you have your phone when you are trying to do deep work?

Between flow state and context switching, which is the safer option to invest into to make yourself more productive?

One of the best ways to improve your productivity is to block off chunks of time where you can focus without having to context switch.

Engineer Your Ideal Tech Career [Part 11] - Michael Novati: Becoming A High-Level IC

Next, [Michael Novati](https://www.linkedin.com/in/michaelnovati) chats about his impressive career advancement and passion for high-level IC work. Michael progressed from a new grad engineer to Staff engineer at Facebook within 3 years, and then Senior Staff after.

He reflects on the key steps he took to progress quickly, common misconceptions people have about being a high-level IC, and the types of people who may love this work longer-term.

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)

15 SWE Years In 1.5 Hours [Part 4] - Debugging

No matter how careful you are as a software engineer, your code will always have bugs. On top of that, you will also need to spend time fixing bugs in code written by other people. This lesson teaches you:

- Why debugging is always a valuable skill (while feature development often isn't)
- How debugging forces you to develop a deeper understanding of the system
- The framework and process you need to understand in order to fix any bug

DSA Crash Course [Part 22] - Linked List Intro Lecture

In this lecture, Alvin explains the basic structure of a singly-linked list.

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

DSA Crash Course [Part 8] - Anagrams Approach

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

> Write a function, *anagrams*, that takes in two strings as arguments. The function should return a boolean indicating whether or not the strings are anagrams. Anagrams are strings that contain the same characters, but in any order.

```
anagrams('restful', 'fluster') # -> True
```

```
anagrams('cats', 'tocs') # -> False
```

```
anagrams('monkeyswrite', 'newyorktimes') # -> True
```

```
anagrams('paper', 'reapa') # -> 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/>

DSA Crash Course [Part 3] - Max Value Walkthrough

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

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

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 6] - Freezing on the Spot

In system design interviews, clear communication is crucial. Many candidates struggle not because they lack knowledge, but because they fail to express their ideas effectively. This video highlights a common issue: Freezing under pressure.

- Instead of freezing when faced with a complex problem, keep the conversation going by asking clarifying questions. This not only helps you gather necessary information but also engages the interviewer.
- If unsure what to ask, focus on understanding the system’s functionality. Questions about the product’s purpose and user journey can guide your design process.
- Involving the interviewer through questions shows your experience and keeps the interview on track.

In short, don’t let nerves stop you—ask questions to maintain momentum and communicate 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>

[Become A Go-To Person 1/18] How This Course Works

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

Maximize Your Productivity As A Software Engineer [Part 22] - Introspect And Reflect

As software engineers, we are constantly getting things wrong, including our productivity system. This is why it's important to learn how to evolve and improve over time - There are very things in engineering where you can just set it and forget it. This lesson teaches you:

- How to set up introspection time and why it's important
- What questions to ask yourself when you reflect
- How to process action items to improve your productivity system

Maximize Your Productivity As A Software Engineer [Part 13] - Decomposition

When you get a huge project as a software engineer, it's easy to get overwhelmed and just sort of... do nothing (or close to it). This lesson teaches you:

- What a well-decomposed project looks like with a concrete example
- How decomposing projects hacks your brain to make it more motivated and productive

To dive deep into tactics on decomposing projects, check out our in-depth explainer: ["How do I make software less overwhelming?"](https://www.jointaro.com/question/YseMPDw538jhyS1MWlTs/how-do-i-make-software-less-overwhelming/)

Learn from the code quality course 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/)

Write A Stellar Resume As A Software Engineer [Part 21] - The REAL Secret For A Top Tier Resume

Unfortunately, it's possible to optimize your resume to the teeth and still not get results. This will be incredibly common for more junior engineers. This lesson teaches you:

- A simple 2-step process to understand how to make an incredible resume
- What to do if you have perfected your resume and you still aren't getting enough interview calls
- Why you are far more powerful than you realize the second you learn how to code and deploy software to production
- How to build impressive side projects that are meaningful on a resume and get you interviews
- How to make impressive open-source contributions that are meaningful on a resume and get you interviews

To dive deeper into building impressive side projects: [\[Taro Top 10\] Building Impressive Side Projects](https://www.jointaro.com/playlist/vKUWMgmmaEvzcYUXZs4B/)

To dive deeper into making impressive open-source contributions: [\[Course\] Become An Open Source Master](https://www.jointaro.com/course/become-an-open-source-master/)

Write A Stellar Resume As A Software Engineer [Part 5] - Resume Gaps

Having an employment gap is effectively inevitable as a software engineer, especially in a layoff-economy. This leads to resume gaps, which unfortunately have a lot of stigma. This lesson teaches you:

- Why employers (rightfully) hold resume gaps against you
- How to include your resume gap on your resume
- What to do in common resume gap scenarios if a company probes you about it during an interview

If you have recently been laid-off, you can check these out as well: [\[Taro Top 10\] Navigating Tech Industry Layoffs](https://www.jointaro.com/playlist/pE7pP0nXDx4X7mOChzHS/)

Grow From Mid-Level To Senior Engineer [Part 9] - Code Quality

Mid-level engineers are usually very solid at coding, but what most don't realize is how high the ceiling truly is when it comes to code quality. This lesson teaches you:

- The difference in code quality between junior, mid-level, and senior engineers
- What a senior engineer level pull request looks like

Become a code quality master by taking our course 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/)

Onboarding Tips Within Larger Companies

In a large company, you should expect a more formal onboarding process. However, don’t let this be an excuse to move slowly. Your goal is (still) to set up your environment and land code within a week.

Big companies will have many teams which may have slightly competing priorities. That means you need to invest in relationships and understand how the work connects between teams. Disperse and collect knowledge from around the company.

Spend some time understanding the unique terminology and culture of the company. Companies like Amazon, Meta, Google, Microsoft are large enough that they have their own set of acronyms, languages, and cultures!

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.