Grow From Senior To Staff Engineer [Part 3] - At A Glance: Senior Vs. Staff

As a senior engineer, you have probably gotten generic guidance on how to get to staff, advice like *"Do more leadership"*. Let's rise above the meaningless engineering career matrix standards and provide something concrete. This lesson teaches you:

- How the dynamic evolves between an engineer and their manager as they grow from senior to staff
- The core behavioral difference between senior and staff engineers as they tackle problems
- The difference between senior and staff engineers with the projects they work on
- The difference between senior and staff engineers with their ownership reach
- The difference between senior and staff engineers with their organizational reach

Grow From Senior To Staff Engineer [Part 2] - Why Is The Staff Promotion So Hard?

Countless senior engineers hit a wall as they push for staff. This lesson teaches you:

- How the Staff Engineer role in and of itself is special by being a relatively new career invention
- The easiest way to tell if a Senior Engineer isn't ready to become a Staff Engineer
- Why the Staff Engineer promotion is fundamentally different from prior promotions
- Why many teams can't support an additional Staff Engineer promotion
- How you can be performing as a Staff Engineer and still not get the promotion

Asking Great Questions [Part 26] - Go Deeper: Follow Through

Asking great questions is a skill that takes months, if not years, to develop. So let's take the knowledge from this course and apply it! You get better by doing, not just consuming.

Improve your question asking skills directly in the Taro forum (while getting answers 10x better than anything you'll find on Blind and Reddit): <https://www.jointaro.com/questions/create/>

Find great engineers to learn from with Taro Networking: <https://www.jointaro.com/networking/?selectedServices=Friendly+Coffee+Chat>

If you can make it, come to Alex's Group Office Hours where you can ask questions in-person: <https://www.jointaro.com/p/alex-chiou/>

Find all Taro community events (including in-person ones where you get free drinks/snacks) here: <https://www.jointaro.com/events/>

Take the related courses:

- [\[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\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)

Asking Great Questions [Part 5] - Figure It Out Or Get Help?

As a software engineer, you need to figure out a lot of things on your own (that's why you get paid the big bucks). However, you don't want to go the extreme where you endlessly run yourself into a wall by not getting help. This lesson teaches you:

- When to figure it out on your own vs. get help
- The dynamic behind solving complex engineering problems
- How to identify if you're stuck
- When to ask for help earlier instead of later

Asking Great Questions [Part 2] - There Are No Stupid Questions

All questions start off from a positive place: An intent to learn more about the world. What matters is how you move forward with that positive energy when executing your question. This lesson teaches you:

- Why there's no such thing as a stupid or dumb question
- Why software engineers need to ask a *ton* of questions in order to succeed
- How bad questions corrupt their initially positive core can weaken the reputation of the asker
- How good questions follow through on their initially positive core to maintain that positive energy and strengthen the reputation of the asker

[Become A Go-To Person 14/18] Give Presentations To Become An Expert

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 20] - Just Jump In

If there's one thing software engineers love to do, it's prepare. They'll read and watch and listen to countless resources in order to get "ready" to tackle their meaty technical challenges. This lesson teaches you:

- Why "preparing" to do a task is basically the same as doing nothing
- The right mentality you must have to tackle any software engineering task efficiently, going away from the mindset that got you through school
- How to effectively dive into a task and get it done fast

Maximize Your Productivity As A Software Engineer [Part 17] - The Demon In Your Pocket

Smart phones unlock infinite opportunity, but they also unlock infinite distraction - We've all lost countless hours towards mindlessly scrolling through the many addictive apps on our mobile devices. This lesson teaches you:

- A basic tactic to prevent you from getting distracted by your smart phone
- A more involved and technical tactic to discourage smart phone user, which Alex is a big fan of
- An extremely aggressive tactic to get your smartphone away from you, used by a Staff Engineer at LinkedIn who's also a parent!

Write A Stellar Resume As A Software Engineer [Part 7] - It's Too Long

Having a resume that's too long is one of the easiest ways software engineers get their resume (and their job candidacy) immediately thrown out. This lesson teaches you:

- The optimal length for a resume
- Why shorter is better when it comes to resumes (and why very long resumes make 0 sense)
- How to convert your years of experience to a resume length
- Tactics to trim down your resume and make it more concise

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

Master The Behavioral Interview [Part 22] - Do Mock Interviews

Software engineers love working and studying solo, but this is extremely difficult with behavioral interviews. This lesson teaches you:

- Why behavioral interviews are inherently collaborative and effectively require mock interviews to master
- How to get the most value from your mock behavioral interview sessions

Master The Behavioral Interview [Part 15] - Mid-Level Engineer

Mid-Level engineers are engineers who have a good amount of experience but aren't exactly senior yet. Most software engineers fall into this bucket. This lesson teaches you:

- The expectations from a mid-level engineer overall and how that reflects in behavioral interviews
- The kinds of stories mid-level engineers tell in behavioral interviews

Master The Behavioral Interview [Part 10] - When You Don’t Have An Answer

If you're an earlier-in-career software engineer, there is a very high chance that you will get a behavioral interview question where you don't have an answer. This lesson teaches you:

- How to gracefully and immediately react when you get a behavioral interview question asking for a scenario that you have never been in before
- Backup options that you can present to the interviewer to still answer the question despite not having an answer that 100% fits

Managing Up: Enabling Managing Up to You

Taro members get a discount to join [Ethan's Level Up community](https://levelupwithethanevans.substack.com/taro25)

Ethan's other courses on Taro: 

- <https://www.jointaro.com/course/the-growth-and-promotion-recipe-magic-loop/>
- <https://www.jointaro.com/course/maximizing-a-severance-package/>

Managing Up: Politics and Ethics

Managing Up: Skip Level Leaders

Managing Up: Senior Peers

Negotiation Course: Get Other Offers

Researching data points is helpful when constructing a negotiation argument, but the **best** argument you have is an offer in hand from a comparable company. 

The big mistake most tech workers make is to be reactive with recruiters. If you decide to interview with a company, figure out comparable companies and apply to them as well. (Google and a seed-stage startup are not comparable.)

Talking to many recruiters and companies at once is painful, but it's better to concentrate the pain in a short window, rather than spreading it across several months. You can also negotiate interview dates, though this is admittedly harder in a bad economy.

As soon as you have a verbal offer, push all your other loops to skip you to onsite using that as leverage ("Don't let the awesome candidate of me get away!").

Negotiation Course: Don't Give A Number First

The most important rule of negotiation is "Don't give a number first." Don’t talk about what compensation you’re expecting, and definitely don't share what you were making at your last job. 

It’s actually illegal in 22 states for recruiters to ask about your prior compensation (CA, NY, IL): <https://www.hrdive.com/news/salary-history-ban-states-list/516662/> 

Because of the info asymmetry we talked about before, there’s no benefit to you sharing a number, but a lot to lose. Henry Ford (the automaker in Detroit in the early 20th century) illustrated this well. He employed a tactic called "highball negotiation" where he would match the offer given by a landowner, even if it was inflated. Read more about this in "[The People's Tycoon: Henry Ford and the American Century](https://www.amazon.com/Peoples-Tycoon-Henry-American-Century/dp/0375707255)" by Steven Watts

Example dialog from the recruiter:

> We really need a number before proceeeding”

Sample candidate reply:

> At this time, I’m more focused on determining if the role is a good fit. I’m confident we can figure out an agreeable number once we mutually agree that we could work together.

Nail Your Promotion As A Software Engineer [Part 22] - The Project Credit Formula

You have been given your projects for the performance review cycle, and they're okay but not amazing. How can you make the most of this opportunity and cobble together a case for promotion? This lesson teaches you:

- The definition of scope, another tech term that is commonly thrown around but horribly misunderstood
- The overall formula to determine how much credit you get for a project
- How to be creative and get the most credit from every project you work on
- How projects of a certain scope can either by increased by 1 level or decreased by 1 level

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.