Engineer Your Ideal Tech Career [Part 15] - Role Types

Depending on what role you’ve narrowed your sights on, there are a number of things you can do in your current role to begin charting progress — from picking a specialization, to start scoping projects and reviewing code, to volunteering for mentorship opportunities and hiring.

Should you be thinking about a change soon, there are also actionable interview prep tips (and mistakes to avoid!) in this section.

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)

Engineer Your Ideal Tech Career [Part 6] - What's Your Ideal Role Type?

In this video, we begin by debunking common career misconceptions that often plague individuals progressing through their career. We then cover the major role types you can aim for as a software engineer. These are only three options, and there are more nuanced ones to explore.

Specifically, we cover becoming a:

- High-Level Independent Contributor (IC)
- Tech Lead
- Engineering Manager

We'll also cover what it looks like to be at the pinnacle of your career in each of those roles.

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)

Amazon Behavioral Interview [Part 1] - Intro

This video introduces a mini-course designed to help viewers master behavioral-based interview questions, commonly used by top companies like Google and Amazon.

- **Focus:** The course emphasizes a framework and process to effectively answer these questions, drawing on the instructors' extensive experience (one was a Google interviewer, the other an Amazon Barraiser).
- **Benefits:** By learning this approach, viewers can confidently handle any interview, reduce stress, and significantly increase their chances of landing their desired job.
- **Content:** The course includes downloadable worksheets and other resources to guide viewers through the process of mastering the "STAR" method (Situation, Task, Action, Result) for answering behavioral questions.
- **Instructors:** The instructors have a combined wealth of experience in interviewing and being interviewed at top companies, ensuring the course provides valuable and practical insights.
- **Goal:** The ultimate goal is not just to teach the STAR method, but to boost viewer confidence and significantly improve their chances of success in job interviews.

Learn more about Alan's job search program, Kadima Careers, using this [discount link](https://signup.kadimacareers.com/mQBsDvu).

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

15 SWE Years In 1.5 Hours [Part 11] - Behavioral Rounds

Data structures and algorithms (DSA) suck up all the air in the room, but behavioral rounds are actually the most important interview round. This lesson teaches you:

- The signal behavioral interviews give that DSA interviews cannot
- The 3 keys you need to communicate in a behavioral interview
- How to structure your behavioral interview answers effectively

To dive deeper into behavioral interviews, take our course here: [Master The Behavioral Interview As A Software Engineer](https://www.jointaro.com/course/master-the-behavioral-interview-as-a-software-engineer/)

15 SWE Years In 1.5 Hours [Part 5] - Succeeding In School

Most software engineers start off their journey in tech by getting a university degree. However, most students don't leverage their time in school optimally. This lesson teaches you:

- The most valuable asset you get from school (hint: it's not good grades)
- Why school isn't very effective at teaching you how to do software engineering in the real world
- What you should do instead to enhance your technical skills instead of purely focusing on getting good grades

Come Up With 500k+ User Project Ideas [Part 15] - Putting It All Together: Idea Scorecard

You now have a side project idea. How can you tell if it's good? This lesson teaches you:

- A systematic scorecard you can use to grade the quality of a side project idea
- What a bad side project idea looks like, demonstrated with concrete scorecard examples
- What a good side project idea looks like, demonstrated with concrete scorecard examples

DSA Crash Course [Part 18] - Recursion Intro Lecture

In this lecture, Alvin introduces the mental model we should use when applying recursion.

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

Become An Open Source Master [Part 24] - Anticipate Common Pushback

- We might get pushback on our pull requests if we don't address all edge cases or introduce performance regressions.
- Follow the project's coding conventions and make sure our code is clean and well-tested.
- Be gracious and adaptable when contributing to someone else's project.

Taro discussions about testing: 

- [What are your thoughts about Test Driven Development?](https://www.jointaro.com/question/SYwVplJYcyO8Sr7PLT2j/what-are-your-thoughts-about-test-driven-development-do-you-think-it-adds-value-in-your-career/)
- [Automated vs manual UI testing?](https://www.jointaro.com/question/frpv5BLQ63ZqvmDcTIkY/automated-vs-manual-ui-testing/)

Connect with James:

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

Become An Open Source Master [Part 7] - Improve Something You Use

The video advises that we should start by finding a project that we're passionate about, rather than aiming for the biggest or most well-known ones.

- **Choose projects that you already use or are familiar with**, as this gives you a head start in understanding the project's goals and potential areas for improvement.
- **The dependency graph on GitHub can help you identify potential projects** by showing the dependencies of projects you're already working on.
- **Consider contributing to smaller or medium-sized projects by companies**, as these can offer valuable learning experiences and opportunities to build relationships with professional developers.
- **Contributing to open source can lead to career opportunities**, as demonstrated by the example of Sophie Alpert and her work on the React project.

Article shown by Sophie Alpert: [Using React to speed up the Khan Academy question editor](https://sophiebits.com/2013/06/09/using-react-to-speed-up-khan-academy)

Connect with James:

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

Grow From Junior To Mid-Level Engineer [Part 8] - Debugging

When it comes to software, there will always be bugs. What many realizes don't realize is that your attitude towards bugs is a huge marker of your seniority. This lesson teaches you:

- Why junior engineers usually don't get assigned bugs
- The differences between junior engineers and mid-level engineers when it comes to bugs
- How to evaluate bug complexity overall
- What a mid-level engineer bug looks like vs. a junior engineer bug

Improve your debugging ability with our masterclass: [\[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/)

Grow From Junior To Mid-Level Engineer [Part 3] - It's On You

For later promotions (i.e. senior and beyond) there are many other factors at play besides your personal skill and growth. This isn't the case for junior engineer -&gt; mid-level engineer. This lesson teaches you:

- The fundamental difference between the junior -&gt; mid-level promotion and others when it comes to landing impact
- How to choose teams and projects as a junior engineer aiming to grow fast
- What matters when it comes to the junior -&gt; mid-level promotion

Understand more about project credit for promotion here: <https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/its-not-just-about-impact/>

Clear Communication For SWEs [Part 14] - How Communication Changes With Seniority

I discuss how communication expectations evolve from junior to senior engineer roles. Junior engineers focus on asking insightful questions and providing clear updates. Mid-level engineers lead projects, suggest improvements, and collaborate effectively. Senior engineers take on leadership roles, communicate strategic decisions, and provide insights based on experience. Adapting communication styles based on audience expertise is crucial for career growth.

Connect with me on LinkedIn: <https://www.linkedin.com/in/ryan-wiens/>

The How of the Engineering Career Ladder: Five Essential Foundations for Advancement

Session led by [Shine Garg](https://www.linkedin.com/in/shinegarg/)

Engineering career ladders lay out the “what” of the software engineering career path—what competencies and behaviors are needed at each milestone. However, they often lack guidance on the “how.”

Understanding how—and how quickly—you can acquire and exhibit these competencies significantly impacts your career trajectory, financial future, and sense of fulfillment in life.

This talk demystifies the process of climbing the engineering career ladder. Join us to learn the five essential foundations for advancing your career and achieving your goals.

Asking Great Questions [Part 6] - Be Clueless In Public

The best software engineers are those who embrace their lack of knowledge. This lesson teaches you:

- Why it's better to ask your question in a broader audience
- The difference levels of visibility when asking a question with higher being better
- A huge, often unknown benefit that comes with asking questions in public which allows even junior engineers to become leaders
- Why you should always try to create a record of your question and its answer(s)

[Timeless Career Advice] Startup vs Big Tech

One of the fundamental questions you face as an engineer is where to work. Should you join a startup, medium-sized company, or Big Tech? What are the pros or cons of working at a tech or non-tech company?

Connect with Louie:

- SmallBets community: [**https://smallbets.com/?utm_source=taro**](https://smallbets.com/?utm_source=taro)
- Twitter: [**https://twitter.com/LBacaj**](https://twitter.com/LBacaj)
- Newsletter: [**https://newsletter.memesmotivations.com/**](https://newsletter.memesmotivations.com/)

Write A Stellar Resume As A Software Engineer [Part 16] - Leveling

For the vast majority of engineers, they want to get the highest level they possibly can from an interview opportunity. How you write your resume is a substantial part of achieving this goal. This lesson teaches you:

- How to format your resume based on what level you were at different points in time
- How including your exact promotions can actually hurt you
- When to include your level on a resume vs. not

Write A Stellar Resume As A Software Engineer [Part 13] - ATS Obsession

With so many resumes being sent in to any decent engineer job opening, automation is often deployed to filter out resumes. The big piece behind this is the ATS. This lesson teaches you:

- What an ATS (Applicant Tracking System) is
- How the ATS fits into the tech recruiting pipeline and how engineers commonly misunderstand that process
- What engineers usually do to incorrectly optimize for the ATS while sabotaging their overall changes
- What you need to do to properly get past the ATS

Write A Stellar Resume As A Software Engineer [Part 6] - Poor Spelling And Grammar

The vast majority of software engineers don't have English as their first language, and this leads to many basic spelling and grammar mistakes on resumes. Unfortunately, this hurts engineers far more than they realize. This lesson teaches you:

- Why there is 0 tolerance for spelling and grammar errors on a resume (i.e. 1 mistake is enough to get your resume tossed out entirely)
- How spelling and grammar mistakes speak volumes about a software engineer's overall skill
- Basic ways to perfect the spelling and grammar of your resume, even if English isn't your first language

Negotiation Course: Negotiating With An Exploding Offer

An exploding offer is an offer that must be accepted within a time limit (potentially as short as a few hours), otherwise it will expire.

**Exploding offers are often fake** and you can take longer than the supposed deadline. However, you should protect yourself in the small chance that the explosion is real by having backup options.

If you face an exploding offer, the first step is to understand where the urgency is coming from:

> What’s the timing constraint? I’ve dedicated 3 weeks interviewing here and enjoyed meeting the team, but I'm curious why there's such an urgency at this point in the process?

A few options for how to request more time: 

- **(less effective)** Explain that you’re still collecting data and wrapping up the process so you’d like another week. Something like: "*I’m in the last round with the company so I’m confident I can get back to you by Monday.*"
- **(more effective)** Ask for more information. "*One thing I heard in the interview is that many of the mobile developers have transitioned to work on dev infra, which is interesting for me. Could I chat with someone who does made that transition?*" 
  - In a similar way, you can also request to chat with folks in the management chain, e.g. the director or VP.
  - When Rahul was at Meta, he’d do calls with people who got offers coming from Pinterest

Worst case scenario, you have to renege or quit shortly after joining. You should avoid this if possible (there is potential reputational damage), but we'll talk about this scenario in the next video.

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.