Write A Stellar Resume As A Software Engineer [Part 12] - Esoteric Terms

As a software engineer, it is absolutely critical for you to write a resume that is incredibly easy to understand, particularly for the recruiter (who, as a reminder, is a non-technical person). Unfortunately, it's very easy for engineers to get this wrong. This lesson teaches you:

- Why engineers often unintentionally make their resumes near impossible to understand
- What esoteric terms are and the categories they fall into
- How to get rid of esoteric terms from your resume with an in-depth example

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

Pinterest Case Study: The Ultimate Guide To Navigating A PIP

This was a non-engineer who had several years of experience before joining Pinterest.

- **Before**: 90 days after joining, was told they needed to improve

- **During**: “Completely blindsided” when placed on PIP at the 4 month mark. Goalposts kept shifting, didn’t receive feedback until 4 weeks later

- **After**: Took the termination after taking leave for interview prep

Break Into Tech And Become A Software Engineer [Part 5] - Know Your Fundamentals & Frameworks

In this lesson, Brian highlights the balance between knowing your technical fundamentals and understanding modern frameworks to build effective software applications.

This lesson covers:

- The importance of having both foundational knowledge and framework expertise to speak the same technical language as co-workers, especially those with computer science degrees
- How understanding design patterns, software development lifecycles, and common best practices prevents you from reinventing the wheel and helps you navigate technical discussions
- Key resources like *Clean Code*, *You Don’t Know JavaScript*, and *The Phoenix Project* that deepen your knowledge of coding fundamentals and software development processes

If you need extra help breaking into tech, join Brian's exclusive, cohort-based bootcamp (just 10 students per batch). Use this special link for $800 off: <https://www.parsity.io/taro>

Connect with Brian on LinkedIn: <https://www.linkedin.com/in/brianjenney/>

Negotiation Course: Closing The Deal

If you’re willing to sign the offer, **you have manufactured leverage you can use to squeeze out additional compensation with high probability**. Tell the recruiter you’re willing to sign the offer immediately if they can give you X, where X is a bit higher than the current offer.

A good choice is to ask for an extra $10K-$20K in sign-on bonus. Companies are willing to do this since it’s a one-time cost but they can guarantee you sign. But $10K is be life-changing for many people.

Making the final request focused on salary or equity is a bit more difficult since it often requires more people’s approval. Your goal in this final round of negotiation is to propose something quick and a no-brainer for the company.

Phrasing:

> I'm eager to use my experience to have impact quickly at \[COMPANY\]. I'm willing to sign the offer today if you can add a signing bonus of $15,000. This would make the offer compelling for me so I can commit to \[COMPANY\] for the next phase of my career.

Ideally you want things in writing. Some recruiters will tell you they can’t put it in the formal offer until you’ve verbally agreed, which is fine, but in that case, you can still ask them for a quick email recap with the numbers included.

15 SWE Years In 1.5 Hours [Part 6] - Networking

Your network is your net worth. Too many software engineers neglect their social skills as they solely build up their technical skills. This lesson teaches you:

- Why networking isn't just "politics"
- The key to effective networking
- How altruism can produce massive career benefits, explained with a powerful, real-life example

Why You Should Always Negotiate Your Offers

- Negotiation is particularly life-changing, especially if you're early-in-career. It's also really high ROI as the cost is effectively just a couple emails and some potential awkwardness.
- Negotiation doesn't hurt anyone within or outside the company - It's effectively a part of life when it comes to the hiring game.
- What you negotiate for isn't connected to your costs: It's about getting what's fair given the market rate and your current leverage situation (i.e. do you have other offers).
  - Even if an offer is good given your personal situation, you should try negotiating, especially if it's below fair market rate for that level/company/geography and you have competing offers.
  - You can always do something with extra money!

If you need premier negotiation support, check out our 3+ hour negotiation course: [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/)

15 SWE Years In 1.5 Hours [Part 17] - Promotion

Of course, you can switch jobs to progress your career, [but you will eventually hit a wall](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/you-cant-job-hop-to-success/). At the end of the day, you need to get promoted to have a meaningful long-term, professional trajectory. This lesson teaches you:

- Why working harder isn't enough to get you promoted
- The key to understanding how promotion works, particularly at top companies like FAANG
- How you need to evolve your behavior to reach senior levels and beyond

To dive deeper into getting promoted faster as an engineer, take our course here: [Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)

DSA Crash Course [Part 43] - Tree Sum Approach

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

> Write a function, *tree_sum*, that takes in the root of a binary tree that contains number values. The function should return the total sum of all values in the tree.

```
a = Node(3)
b = Node(11)
c = Node(4)
d = Node(4)
e = Node(-2)
f = Node(1)
a.left = b
a.right = c
b.left = d
b.right = e
c.right = f

#       3
#    /    \
#   11     4
#  / \      \
# 4   -2     1

tree_sum(a) # -> 21
```

```
a = Node(1)
b = Node(6)
c = Node(0)
d = Node(3)
e = Node(-6)
f = Node(2)
g = Node(2)
h = Node(2)
a.left = b
a.right = c
b.left = d
b.right = e
c.right = f
e.left = g
f.right = h

#      1
#    /   \
#   6     0
#  / \     \
# 3   -6    2
#    /       \
#   2         2

tree_sum(a) # -> 10
```

```
tree_sum(None) # -> 0
```

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

Grow From Senior To Staff Engineer [Part 18] - Product Hybrid

As a software engineer, you generally want to evolve past the code. There is 1 group of staff engineers who take that to the extreme. This lesson teaches you:

- What the product hybrid staff engineer archetype is
- The exact expectations of a product hybrid staff engineer
- How software engineers are uniquely positioned to hybridize as product managers
- Why most tech companies don't support the product hybrid archetype
- How to become a product hybrid staff engineer

Learn to sharpen your product sense with these resources: [\[Taro Top 10\] Product Management For Engineers](https://www.jointaro.com/playlist/66TyB60SRRmdnm0jmf55/)

What Gets Communicated Gets Done: Why Slack Sucks

15 SWE Years In 1.5 Hours [Part 15] - Onboarding

You have started a fancy new job at a company you really like. How do you hit the ground running and impress people fast? This lesson teaches you:

- Why being new is actually a superpower, not a weakness like many engineers think
- Why you need to be aggressive and extremely deliberate when onboarding, especially at the very beginning
- What you can do to *add value* while onboarding instead of merely absorbing value

To dive deeper into onboarding, take our course here: [The Complete Onboarding Guide For Software Engineers](https://www.jointaro.com/course/the-complete-onboarding-guide-for-software-engineers-succeeding-when-youre-new/)

Master The DSA Interview [Part 29] - LeetCode Stockholm Syndrome

Even after passing the data structures and algorithms interview, a surprising amount of engineers maintain a toxic relationship with it. This lesson teaches you:

- What LeetCode Stockholm Syndrome looks like
- Why it doesn't make sense to continue studying data structures and algorithms after you have started the job
- The key towards true growth as a software engineer (hint: it's not LeetCode)
- A super simple way to understand data structures and algorithms studying and how it fits into your life

Engineer Your Ideal Tech Career [Part 5] - Gathering Requirements And Preferences

As an introduction to this next section, you can expect to start defining what your long-term career and path may look like based on your preferences you defined in the last section.

For each dimension, pick one option only to make your goals as clear as possible. If one dimension doesn’t resonate with you, that’s okay! Skip it vs. making arbitrary goals.

The dimensions we’ll cover are:

- Role types
- Specializations
- Company stage
- Becoming a founder

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)

Asking Great Questions [Part 7] - Diversify Your Asks

It is tempting to stick with what you know. When it comes to asking questions, this means asking the same person again and again after they have helped you before. However, this isn't the way to go when it comes to your growth. This lesson teaches you:

- How repeatedly getting help from just 1 person can strain your relationship with them
- The tech industry-specific danger of only having 1 person to answer your questions
- The tactical survival benefit of diversifying the pool of people you ask questions to
- How getting help from a lot of people builds up a huge career asset with long-term social capital, which is crucial for more senior engineers

Grow From Senior To Staff Engineer [Part 6] - You Need Tenure

Software engineers like to give up when their team isn't going perfectly, often interviewing with another company entirely to jump ship. While this can work earlier in your career, it almost always stops as you're approaching staff. This lesson teaches you:

- Why job hopping to a staff uplevel at a top company is almost impossible
- Why you need to be in the same team for 2+ years in order to have a real case for staff
- The ingredients to develop the presence and impact of a staff engineer

Becoming A Legendary Meta Coder: The Story of the First E7 Code Machine

There are many complex ways [**to get to staff and beyond**](https://www.jointaro.com/course/grow-from-senior-to-staff-engineer-l5-to-l6/why-have-archetypes/), but one of them is actually quite straightforward (at least at Meta): *Just write more code than everyone else by a **staggering** amount.*

That's exactly what [**Michael Novati**](https://www.linkedin.com/in/michaelnovati/) did to get to Staff \[E6\] at Meta and eventually Senior Staff \[E7\]. Since Michael was early Facebook, there actually wasn't a Staff Engineer archetype at the time to capture the way he was adding immense value to the company. So they added it! Thanks to Michael, there is now a formal "Code Machine" archetype in the official Meta internal wiki.

Michael will be breaking down:

- His story about how he became Meta's first incredibly senior "Code Machine" engineer
- The most impactful projects he worked on
- How he managed his time effectively to write so many diffs.

At the end, we'll have time for Q&A where you can ask Michael questions about topics like:

- How he grew so quickly and crafted such an extraordinary career
- What the early days at Meta were like
- Different ways to create a unique brand for yourself, your work, and your career

If you need extra help breaking into top tech companies like FAANG, [**Formation.dev**](http://Formation.dev) is here to provide you hands-on, personalized support. Join Michael and the rest of the awesome team at Formation here: [**https://formation.dev/partners/taro**](https://formation.dev/partners/taro)

20 Years Of Fighting Procrastination [Part 9] - Say FU (Focus Uninterrupted) To Meetings

Sitting through too many meetings can quietly kill productivity. This video offers a framework for reclaiming your time and focusing on deep work. Here are the core points from the lesson:

- One time in Rahul's past, there was very senior Facebook engineer boosted output and morale by declaring “meeting bankruptcy” and skipping all meetings for a month to focus on heads-down coding
- Most meetings aren’t necessary—test their value by asking if they make you more effective and whether the same information could be shared asynchronously
- As you get familiar with your company’s culture, work with your manager to trim or redesign meetings that don’t drive impact, especially recurring ones

Master The Behavioral Interview [Part 24] - Challenge Yourself, Do Great Work

Behavioral interviews are fundamentally an exercise in storytelling. This means that in order to pass these interviews as a software engineer, you need great stories to begin with. This lesson teaches you:

- The 2-step process to become absolutely incredible at behavioral interviews
- The most common mistake software engineers make with their mentality when it comes to growth
- How to get better at coding, even if you're unemployed

For more resources on becoming a better software engineer:

- [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- [\[Course\] Build Side Projects With 500k+ Users: Coming Up With An Idea](https://www.jointaro.com/course/build-side-projects-with-500k-users-coming-up-with-an-idea/)
- [\[Taro Top 10\] How To Create Scope As An Engineer](https://www.jointaro.com/playlist/EWIo3USNcsgXbCs5PS0h/)
- ["What are the Core skills a SDE should be consistently developing?"](https://www.jointaro.com/question/Hs8VJtUb6bfTPjUgbj96/what-are-the-core-skills-a-sde-should-be-consistently-developing/)

Become An Open Source Master [Part 11] - Go With The Flow

We can contribute to open source projects by either creating something new or picking up existing work. It's important to communicate with the community owner or maintainer and earn their trust. We can do this by opening discussions, being open to feedback, and starting with small, well-defined tasks.

Example strong pull request (PR) from TinyBase: <https://github.com/tinyplex/tinybase/issues/130>

Connect with James:

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

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.