How To Quickly Understand Company Culture - Airbnb Example

Culture is more than what people say. It's about how things get done in the company. The best way to ramp up on a company's culture is to observe what people do and talk to as many people as possible when you first join.

Rachel also talks about the 2 unique aspects of Airbnb's culture: 
1. Mission-driven (as opposed to tech, sales, or founder driven)
2. Incorporating the best of different companies

If you want to learn more about how to understand an org/company and build up influence within it, here's some related resources:
- ["How do I sell the vision behind a large, org-level project?"](https://link.jointaro.com/ESa5WJyk682iwqJt9)
- ["How can I build up more influence in an org?"](https://link.jointaro.com/GVYFUhx46N2QWVeZ7)

Here's How To Identify A Superstar Leader

[**Ethan Evans**](https://www.linkedin.com/in/ethanevansvp/) is a retired Amazon VP who led teams of up to 800. Here are his two criteria to see your manager is worth working for.

**1\. Investing in people:**

- Look for a manager with a track record of **growing and promoting their team members**.
- Signs of this include:
  - Do reports of your manager often get promoted or take on higher responsibilities?
  - Does your manager actively create opportunities for your development and growth?
  - Does your manager provide good mentorship and guidance?
  - Managers with a loyal following strongly indicate their leadership qualities.

**2\. Personal trajectory:**

- Assess your manager's **career progression**.
- Look for:
  - Consistent upward movement and promotions.
  - A history of exceeding expectations and taking on greater challenges.
  - Faster-than-average advancement compared to peers.

**Reasoning:**

- A manager who invests in their people will more likely create a supportive and growth-oriented environment for you.
- A manager on a consistent upward trajectory signifies their competence and ability, potentially opening doors for their team's growth as well.

Explore more: 

- [Turning the Spotlight on Unsung Efforts: How to Be Perceived as Important and Impactful?](https://www.jointaro.com/question/G91Qd0GbID5AtnRbfGJE/turning-the-spotlight-on-unsung-efforts-how-to-be-perceived-as-important-and-impactful/)
- [How to manage a team towards high performance?](https://www.jointaro.com/question/O8vtGxsrwZebiSSlOlRd/how-to-manage-a-team-towards-high-performance/)
- [**\[Taro Top 10\] Software Engineer To Engineering Manager (IC -&gt; M Track)**](https://www.jointaro.com/playlist/oz0mnJvHHgM8NfVF7rgp/)

Negotiation Course: Reneging An Offer

Backing out after accepting an offer (*"reneging on the offer"*) is unfortunate but happens more frequently than you think. Imagine that you accepted a job offer, but two weeks later, you finally get an offer from another company that is better in every way. What do you do?

First, prevention is the best cure: try to get all the offers around the same time.

If the timing mismatch is unavoidable, you should do what’s best for you: don’t worry too much about the company.

In the US, employment is at-will, so there’s nothing legally preventing you from joining. Of course, you may have to give back any kind of signing bonus.

There may be reputational damage: talk about why the opportunity is incredibly unique and you hope to work with them again. Reneging on a large company is not as big a deal compared to a startup.

Software Engineering Vs School -- What's the Difference?

A core confusion for many new Computer Science graduates who land a role as an engineer is that **their job is only partially about coding**. Edsger Dijkstra once said:

> Computer science is no more about computers than astronomy is about telescopes.

A software engineer is much more than a computer programmer. You're a point of contact for your team, and you better get used to working with tons of other... humans.

And humans are often harder than computers to deal with :)

1️⃣ Learn to push back on requests or features
2️⃣ Communicate the value of your work
3️⃣ Understand how career growth works at your company

This video covers the main areas in which being a software engineer diverges from being a computer science student. The earlier in your career that you are able to fully recognize and account for these differences, the sooner you can go from a simple low-level engineer “who just writes code” to a more senior actor that is able to push the direction of both your team and other teams in your organization.

- Read the [blog post version](https://www.jointaro.com/blog/school-vs-swe-a-lot-of-nos/) of this
- Follow Jordan on YouTube: [https://www.youtube.com/@jordanhasnolife5163](https://www.youtube.com/@jordanhasnolife5163)

Related resources: 
- [Working with your manager for promotion](https://www.jointaro.com/question/iH4HPSNkRpGGCGSlNhNm/resurfacing-a-discussion-about-a-promotion-with-my-manager/)
- [Masterclass on choosing a good team and company](https://www.jointaro.com/lesson/0WEmTNZOMIh8xAdfO3JH/masterclass-how-to-choose-a-good-company-and-team-as-a-software-engineer/)
- [Masterclass about learning quickly in tech](https://www.jointaro.com/lesson/u9ldIvrTvV1wfWExccDR/masterclass-how-to-learn-quickly-in-tech/)

"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!

Grow From Mid-Level To Senior Engineer [Part 23] - Plot Your Growth Journey

The mid-level engineer to senior engineer promotion takes years for a very simple reason: You need to develop a *ton* of new skills to make it. This lesson teaches you:

- How to prevent yourself from becoming overwhelmed on your journey from mid-level to senior
- The standard growth path from L4 (mid-level) to L5 (senior) and what it means to be L4.5
- Why the L4.5 growth path that initially focuses on increasing your engineering excellence is generally the smoothest path to senior engineer

DSA Crash Course [Part 69] - Tribonacci Approach

In this lesson, Alvin explores the strategy to solving the following problem using dynamic programming:

> Write a function *tribonacci* that takes in a number argument, *n*, and returns the *n*\-th number of the Tribonacci sequence.
>
> The 0-th and 1-st numbers of the sequence are both 0.
>
> The 2-nd number of the sequence is 1.
>
> To generate further numbers of the sequence, calculate the sum of previous three numbers.
>
> Solve this recursively.

```
tribonacci(0) # -> 0
```

```
tribonacci(1) # -> 0
```

```
tribonacci(2) # -> 1
```

```
tribonacci(5) # -> 4
```

```
tribonacci(7) # -> 13
```

```
tribonacci(14) # -> 927
```

```
tribonacci(20) # -> 35890
```

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

Negotiation Course: Determine Levers You Can Pull

The typical 4 highest-order bits for a compensation package in tech are salary, equity, signing bonus, and annual bonus. 

Ask an open-ended question to understand what the recruiter is dealing with: 

> What parts of the offer are you able to adjust the most?

In some companies, you’re just given a salary, a single dimension to negotiate on. In this case, your job is to **invent other parameters on which you can negotiate**. e.g. talk about benefits, title, and other things that you’re willing to give up in order to optimize the thing you really care about.

You can share other offers here, but be prepared to show proof (Rahul had to do this in 2013 when he had to show the Google recruiter the numbers from the Twitter offer)

Nail Your Promotion As A Software Engineer [Part 20] - Quality Of Delivery

Anything worth doing is worth doing right, and this applies to software engineers as well. This lesson teaches you:

- Why quality of delivery is such an important project axis when it comes to promotion, especially to senior levels and beyond
- The immense value of smooth delivery when it comes to your perception among engineering leadership
- Concrete angles to consider when maximizing your quality of delivery

The Importance of Reflection With Time Management

Why is reflection important when it comes to productivity?

True or false: If you aren't getting as much done as you want, you should just work harder.

Which one of these is a concrete tactic you can use to shore up your reflection?

Establish what you want to get done in a given day or week. But if you don't get it done, then you NEED to reflect on **"why"**? Some possible reasons you might come up with it: 
- Procrastination
- Lack of clarity
- Missing information 
- Ad-hoc meeting

Now use this as learning going forward to make better estimates. Reflection is important enough that you should block time your calendar for it.

Master The DSA Interview [Part 17] - How To Pass FAANG DSA Rounds

Why is it so hard to break into FAANG? Well, it's because FAANG tends to push engineers far harder on data structures and interviews problems. This lesson teaches you:

- The score spectrum FAANG interviewers use to grade candidate
- What it means to get a "Yes" vote on a data structures and algorithms round
- What it means to get a "Strong Yes" vote on a data structures and algorithms round (very important when the market is bad)
- What a strong passing data structures and algorithms interview performance looks like, explained with an in-depth example

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.

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

20 Years Of Fighting Procrastination [Part 5] - Debug Your Productivity

Procrastination thrives when you confuse learning with progress. Here are the core points from the lesson:

- Jumpstarting productivity means producing *before* you feel ready — even a rough draft unlocks momentum
- Replace the one-way flow of tutorials with a feedback loop: code → learn → refine
- Writing personal notes or process logs boosts clarity and reduces future ramp-up time
- Systematize repeatable work into reusable components to move faster with each project
- Build a library of “done before” artifacts you can copy, tweak, and ship again and again

[Part 6] Meta Intern Success Series - How Most Interns Fail

Here are the common ways software engineer interns at Meta fail:
- **Misalignment of expectations**: Make sure that you're getting feedback regularly from your intern manager (IM) and ask every 2-3 weeks for a honest, real take on how you're trending. Don't wait until mid-cycle for real feedback!
- **Doesn't take feedback well**: Remember, feedback is a gift. Respond to it gracefully and quickly; treat every piece of feedback with urgency. As a software engineer intern, you barely know anything (which is expected): If you get constructive criticism, there is a 99% chance that it is correct.
- **Writes sloppy code**: Volume is straightforward and not that special - Most interns know how to write a lot of code from school. The point of your internship is mostly to teach you how to write good, clean, production-level code. Make sure your diffs are thoughtful, focused, and atomic with thorough context sections and test plans.
- **Sphere of influence is too small**: Don't only rely on your IM; you need to have 2-3 other peers to vouch for you in final calibrations. It can be comfortable asking your IM for help on everything, but you have to diversify: Make sure that you also ask other peers for help and to review your diffs. Consider having a recurring 1:1 (once every 3-4 weeks) with your non-IM peers.

DSA Crash Course [Part 68] - Fibonacci Walkthrough

In this lesson, Alvin walks through the python implementation for the *fib* problem. The goal here is to solve it recursively and then apply dynamic programming to speed it up.

Code along and test your work in the following editor workspace: <https://structy.net/problems/fib?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/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

Ace Your Tech Interview As A Software Engineer [Part 37] - Getting The Offer

Congratulations, you got the offer! However, the journey isn't over yet. This video teaches you:

- The exact steps you should follow after getting an offer (it doesn't even have to be a formal offer letter)
- Why offers are often even more valuable than software engineers think, even the more lackluster ones
- How to communicate with other companies you're in the interview loop for after you have gotten any offer (even a verbal one)

To master the art of negotiation, follow the advice here: [The Insider's Guide To Negotiating Your Tech Salary And Compensation](https://www.jointaro.com/course/the-insiders-guide-to-negotiating-your-tech-salary-and-compensation/)

The Hardest Part Of Peer Feedback: Giving Them Constructive Criticism

- When the feedback prompt asks you for what your peer can improve on, it is *not* asking you what your peer is doing poorly. If you see your peer doing something toxic/negative, you should give them that feedback *immediately*. Don't wait 6-12 months until performance review season to drop this giant ball on them.
- The *real* question behind this prompt is: "How can your peer expand their scope?". This often times involves something they're already doing well that they can do even better and expand to achieve even greater impact.
- This question will be much easier to answer once you have a deep understanding of engineer levels as a lot of this feedback will be around what you think your peers can do to reach the next level.
- Example: Your peer is very passionate about automated testing and always pairs their landed code with robust test coverage. You suggest that they push to spread this behavior across the entire team with an overall testing initiative.

Life After PIP: The Ultimate Guide To Navigating A PIP

One of the biggest concerns for anyone who has received a PIP is about how it may effect their future job prospects. The answer is, no, a **PIP does not need to follow you around**. You can (and will) find a fresh start and a thriving career if you want it. 

Remember, a PIP is about **both** employee and employer. When you change jobs, your employer is changing, so the situation leading to the PIP is very different.

As you reflect on your next role, it’s worthwhile to allocate some time to reflect: 

- Collect feedback from others: at the minimum, save a copy of your PIP and figure out what feedback there is transferable to another job.
- Collect feedback from yourself: Write down your reflections: what did you enjoy (or not) about your past work experience. What types of projects and people were fun for you?

Grow From Senior To Staff Engineer [Part 22] - Go Deeper: Follow Through

Start a career discussion in Taro: <https://www.jointaro.com/questions/create/>

Join Taro events: <https://www.jointaro.com/events/>

Related courses:

- [Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)
- [Managing Up: Build Effective Relationships With Your Boss](https://www.jointaro.com/course/managing-up-build-effective-relationships-with-your-boss/)
- [Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)
- [System Design Masterclass: Shipping Real Features To Production](https://www.jointaro.com/course/frontend-system-design-masterclass-building-playlists/)

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.