How To Know If You’re Doing Well

Your goal while onboarding is to connect your work to the bigger picture of what your team/org/company is working on, and build your own ideas around priorities.

**Signs that you're helping people**:

- Are you adding value? Are you able to help people newer than you?

- Are you able to improve the onboarding process and get feedback from coworkers about the changes you're making?

- Are you able to understand and contribute to code reviews?

**Signs that you're not doing well**: 

- You're not engaging with people on the team
- You're not getting assigned any work of value, even when you propose ideas
- You need constant support for the work you're doing

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

Principal Engineer (L8) Describes Most Important Skill - Pong Eksombatchai

Pong is a Principal Engineer at Pinterest.

- **Most important skill**: technical communication. As a Principal Engineer, you can't have sufficient impact on your own. Effective technical communication enables you to work through others and advise other teams on the recommended technical path. 
- **Advice**: model the behavior and culture you want. A Principal Engineer is, by default, a role model for the team and org, so their actions set the tone.

Here's the full playlist asking engineers what the most important skill is for their level: [Asking 7 Levels Of Engineers The Most Important Skill](https://www.jointaro.com/playlist/J9Io5lDGaYUpI8vGrUyI/)

Helpful links:
- [SWE2 --> Principal Eng in 4 years](https://www.jointaro.com/lesson/Lvf1TDKt1R4ZJSCr9BVv/rockstar-software-engineer-story-sw2-greater-principal-in-just-4-years/)
- Taro's top 10 to get promoted from [senior to staff engineer](https://www.jointaro.com/playlist/YD8LMCSlE71VUGUbNAWM/)
- [David Pan on what makes a great tech lead](https://www.jointaro.com/lesson/uHqZZ15SK19MatEvLSO6/what-makes-a-truly-great-tech-lead-a-vp-of-engineerings-perspective/)
- [Pong on LinkedIn](https://www.linkedin.com/in/chantat-eksombatchai-268142b8/ )

[Case Study] How to Quit Your Job The Right Way (w/ ex-Netflix TL Michael Lin)

[Michael](https://www.jointaro.com/profile/Ab2xedZA7RhROW0wo9wBHIJbAsX2/) famously [quit his $450,000 job at Netflix](https://www.jointaro.com/blog/why-i-quit-a-450k-engineering-job-at-netflix/), and asked for (and received) a severance package in the process! If you're thinking about quitting your job, consider these points **before** leaving: 

### Timing is important
- It’s better to leave on the 1st of the month than the 31st because employee benefits renew on a monthly basis.
- If you leave on the 1st, it’s like getting a full extra month of benefits. 
- But if you leave on the 31st, your benefits may end the next day.

### Quitting is a trade-off
- You’re weighing that the negatives of staying outweigh the negatives of losing out on income.
- If you have to cut vacations, move away from loved ones, and say no to social events, then those negatives may outweigh the negatives of your job.

### Act with urgency
- If your career is not going the right way, take action quickly.
- If you stay an extra two years at a job you wanted to leave and did this over five jobs in your lifetime, that’s ten years of your life spent doing work you never wanted to do.

---------
- Connect with Michael on [LinkedIn](https://www.linkedin.com/in/michael-lin-tech/)
- Subscribe to [Michael's newsletter](https://michaellin.substack.com/)

Related questions: 
- ["Should I request a voluntary layoff to my manager?"](https://www.jointaro.com/question/FnInc1bJ3AUJBz0grFyj/should-i-request-a-voluntary-layoff-to-my-manager/)
- ["Should I quit to prep for interviews?"](https://www.jointaro.com/question/Cno3oaZkvUu7BPLhHB7g/should-i-quit-to-prep-for-interviews/) from a Data Engineer

System Design Series: Taro Playlists [Part 6] - Overall Approach And Tradeoffs

You can [find the full system design doc here](https://docs.google.com/document/d/15WaM8Ojan82g0m2mtz6kC2Hiyj0Q6VbjfqRmVNDI3qw/edit?usp=sharing) - Feel free to use it as a template for when you're designing systems at your job!

The tactics are covered in the doc linked above, so this summary will focus on the "meta" context behind this part and additional commentary:

- When it comes to determining your overall approach, it's important to understand the priorities and values of your team/company. You can't have it all when building software; when you invest more in a certain attribute, it will generally take away from others. Here are some example attributes:
  - Execution speed
  - Feature robustness
  - Code readability
  - System scalability
  - Design and aesthetic
- Taro and very early-stage startups in general will make warped decisions as the prioritization leans extremely heavily towards execution speed. The goal is to 80/20 as much as possible when it comes to all the other attributes surrounding quality.
- Since this case study is a pretty basic CRUD play building on top of an existing model, there isn't too much complexity around the approach. However, you generally want to propose 2+ concrete approaches and the tradeoffs behind them, especially at a Big Tech company where you often have many, many options.
- Here are the technical design principles covered in the video:
  - **Single source of truth**: This is a very easy way to systems to break and have inconsistent experiences. Let's say your content object has 2 fields, a boolean of "hasLikes" and then an array of users who have liked this particular piece of content. You can either check the emptiness of the array to see if the object has likes or consult the boolean. It's extra work maintaining these 2 different representations of this information, and if they fall out of sync and 2 services/surfaces each read from a different one, things will get weird.
  - **Smart server, dumb client**: You cannot scale the user's device unless you ship them a new computer or phone. However, you can theoretically infinitely scale your server-side. This is why clients (i.e. usually front-ends) should be as dumb as possible with the back-end abstracting away as much complex logic as possible. This is especially true when your product is a mobile app as there will always be users lagging on older versions of the app - You don't want to have to make a mobile update every time you have a basic product logic change. Make your back-end protocol generic, flexible, and powerful.
  - **Be additive with data model**: This is primarily relevant with mobile apps as you will have users on older builds. If you change or remove a field, older builds will break. You can't count on your users to all update to the latest version of your app immediately.

What To Do If Your Manager Seems Detached

Build Deep Relationships Quickly In Tech [Part 1] - How This Course Works

Trying to break into FAANG, but you have no close friends there willing to give you a strong referral? Aiming for a promotion, but you don't have enough senior peers to vouch for you? These are career shortfalls engineers face constantly, and it's because *they don't have a strong enough network*.

This course is here to fix that issue for you, because at the end of the day, your network is your net worth, especially in a hyper-competitive tech market. Here are the core parts of the lesson:

- Your instructor [Alex Chiou](https://www.linkedin.com/in/alexander-chiou/) walks you through his extensive 10+ year Silicon Valley background with rapid career advancement, ending up as a high-performing tech lead making $750k at Robinhood. Most importantly, he goes through how he's built a massive network full of talented people willing to fight for him across his career and the many career benefits he's reaped from that.

- We walk you through the course objectives. By the end of the course, you will:

  - 🌟 Understand the **\#1 rule** of networking

  - 2️⃣ Set up a basic **2-step process** for networking

  - 🤝 Know how to find the **best people** for your network

  - 🏃 Develop tools to **build relationships fast**

  - 🛑 Save time by **avoiding common mistakes**

DSA Crash Course [Part 10] - Most Frequent Char Approach

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

> Write a function, *most_frequent_char*, that takes in a string as an argument. The function should return the most frequent character of the string. If there are ties, return the character that appears earlier in the string.
>
> You can assume that the input string is non-empty.

```
most_frequent_char('bookeeper') # -> 'e'
```

```
most_frequent_char('david') # -> 'd'
```

```
most_frequent_char('abby') # -> 'b'
```

```
most_frequent_char('mississippi') # -> 'i'
```

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 Crack System Design Interviews - Part 1: Introduction to the course

This course will help you understand system design interviews, prepare for them, and learn what to keep in mind during the process. Here's what we'll cover:

- **Understanding the Interview:** We'll review the structure of a system design interview and how it evaluates your skills, focusing on preparation, communication, and problem-solving.
- **Importance of Communication:** We'll discuss how to effectively communicate your ideas, understand requirements, and collaborate with the interviewer.
- **Technical and Problem-Solving Skills:** We'll explore how to leverage your experience and knowledge to answer questions effectively, drawing on real-world examples and theoretical understanding.
- **Preparation Strategies:** We'll cover various methods for preparing for system design interviews, including mock interviews, independent learning, and structured courses.
- **Step-by-Step Guidance:** We'll break down the interview process into manageable steps, offering clear and concise instructions to help you succeed.

Do mock interviews from one of the services on the [perks page](https://www.jointaro.com/perks/) (e.g. [Exponent](https://www.tryexponent.com/?ref=taro)) or [Taro's networking tool](https://www.jointaro.com/networking/?selectedServices=Mock+Interviews).

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

Master The DSA Interview [Part 23] - Don't Just Surrender

When preparing data structures and algorithms, you will almost certainly get frustrated at many points in the process. How you react to those moments will dictate how well you do in those interviews:

- What to do when you're stuck on a data structures and algorithms problem in prep so you can actually learn the problem and its concepts
- How to unblock yourself on a data structures and algorithms problem properly in prep, shown with an in-depth example

Master The DSA Interview [Part 22] - The #1 Tool For DSA Prep

As a mainstay of the software engineering industry for 15+ years, data structures and algorithms have more than their fair share of online resources to help you learn it. This lesson teaches you:

- The #1, time-tested resource to learn data structures and algorithms
- The trap many engineers fall into when learning data structures and algorithms when it comes to tool selection
- How to organically expand LeetCode into the rest of your learning tree
- What to do when you get a FAANG interview

If you're interested in NeetCode, you get a discount on it with your Taro Premium membership. Redeem it here by using code TARO at checkout: <https://neetcode.io/pro?utm_source=taro>

Grow From Junior To Mid-Level Engineer [Part 2] - At A Glance: Junior Vs. Mid-Level

What exactly does it mean to be a junior engineer vs. a mid-level engineer? What's the gap? This lesson teaches you:

- What it means at a high-level to be a junior vs. a mid-level engineer
- The difference in execution between a junior engineer and a mid-level engineer
- The types of tasks junior engineers work on vs. a mid-level engineer
- The ownership and scope difference between a junior vs. a mid-level engineer
- The difference in organizational complexity between junior engineers and mid-level engineers

Maximize Your Productivity As A Software Engineer [Part 21] - Verify Your Foundation

Work and life are deeply interconnected, despite how much we want this to not be the case. If your personal foundation isn't there, it's hard to get anything done working a mentally-intensive job like software engineer. This lesson teaches you:

- How it's possible to implement literally all the advice from this course and still not be productive
- What to do if you're stuck in a productivity rut that you just can't get out of
- The ingredients behind a healthy personal foundation

Learn more about how to have good work-life balance here: [\[Taro Top 10\] Work-Life Balance](https://www.jointaro.com/playlist/JNCZ1vbRF3NwsOQCqblt/)

Maximize Your Productivity As A Software Engineer [Part 19] - Eat The Frog

The first couple hours after you start work are absolutely crucial - Unfortunately many software engineers waste this crucial time, working on the wrong type of tasks. This lesson teaches you:

- What it means to eat the frog (don't worry, it doesn't involve any actual eating or 🐸s)
- Why eating the frog is so important
- The difference between junk food tasks and core tasks

Maximize Your Productivity As A Software Engineer [Part 15] - Live And Breathe Quality

One of the biggest myths in the tech industry is that in order to move incredibly fast, you need to sacrifice quality and do a mediocre job. This lesson teaches you:

- The dangers of cutting corners when it comes to engineering work
- Why having high code quality leads to you landing code faster
- Different ways for you to weave quality into your work for an immediate positive return on investment for your time

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

Write A Stellar Resume As A Software Engineer [Part 2] - Why You NEED A Killer Resume

As a software engineer, there are a million different things you can do. Choosing the right things to work on from engineer to engineer, but the good news is that having a great resume is one of those right things for every engineer. This lesson teaches you:

- Why optimizing your resume is one of the highest return on investments you can possibly do
- Understanding the overall job search funnel and how a good resume fits within it

Grow From Mid-Level To Senior Engineer [Part 11] - Debugging

Debugging is one of the most important skills every software engineer needs to develop. Despite this, many software engineers see bugs as a source of frustration instead of opportunity. This lesson teaches you:

- The mindset shift that has to happen when a mid-level engineer grows to senior engineer when it comes to bugs, particularly large production outages
- How senior engineers solve different types of bugs of a broader scope compared to mid-level engineers

To get better at debugging, check out: [\[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/)

Nail Your Promotion As A Software Engineer [Part 6] - An Easy Way To Understand The Next Level

What does it actually take to get promoted? A lot of software engineers are overwhelmed with all the possible ways to grow, which ultimately leads to inaction. This lesson teaches you:

- A straightforward mental framework to understand why you aren't at the next level yet
- Questions you can ask yourself to identify gaps in your behavior to level up

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.