Growth And Promotion 5/6: Prioritization

Key points:

- 💡 Prioritizing important tasks over urgent but less important tasks is key to career success.
- 🔔 Urgency often creates false importance, like notifications that demand attention but don't actually matter.
- 🔥 Focus on tasks that are both urgent and important first, like handling emergencies.
- 🚫 Learn to say 'no' to tasks that are urgent but not important in order to focus on high-impact work.
- 🤔 Many tasks we put off are important but hard, and tackling them first can improve productivity.
- 🏗 Break down large, difficult tasks into smaller pieces to make consistent progress every day.
- 🪨 Think of your day as a jar: put the big rocks (important tasks) in first before filling it with sand (small tasks).
- 👥 Delegation is key to efficiency: give away tasks you’ve mastered to others so you can focus on higher-value work.

Starting at Amazon as a Senior Manager, then Director, then Vice President, Ethan has decades of experience at top tech companies. This career growth course is developed from his own knowledge and input from his extensive network of fellow coaches and executives.

- Connect with [**Ethan on LinkedIn**](https://www.linkedin.com/in/ethanevansvp/)
- Taro members get a discount to join [Ethan's Level Up community](https://levelupwithethanevans.substack.com/taro25)

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

Master The DSA Interview [Part 19] - Perfection Obsession

Getting the optimal solution to a data structures and algorithms problem is great, but it isn't always possible. This lesson teaches you:

- Why pursuing the optimal solution upfront when you're very stuck can easily lead to your rejection in a data structures and algorithms interview
- What to do instead when you're unable to get the optimal solution upfront
- How being completely stuck can lead to a vicious cycle that forces you to fail interviews
- A simple way to think about data structures and algorithms problem solving in general

Master The DSA Interview [Part 5] - It's A Parasite

While data structures and algorithms are pivotal when it comes to cracking interviews, you need to be careful about how you interact with them. If you don't, they can easily tank your job search. This lesson teaches you:

- Why data structures and algorithms are parasitic
- How data structures and algorithms are actually the most shallow interview type, especially for non-junior engineers
- Other activities you can do on the job search to achieve more well-rounded results
- The decision tree you should use to figure out if you should go hard on data structures and algorithms studying

To learn how to build up your network: [\[Masterclass\] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

To learn how to build effective side projects: [\[Taro Top 10\] Building Impressive Side Projects](https://www.jointaro.com/playlist/vKUWMgmmaEvzcYUXZs4B/)

Break Into Tech And Become A Software Engineer [Part 20] - Demystifying Resume Selection

In this lesson, Brian shares insights from his experience as an engineering manager, explaining how resumes are sorted into "no," "maybe," and "yes" piles during the hiring process.

This lesson covers:

- Why resumes with a skills mismatch or unclear roles are put into the "no" pile, and how to avoid this by clearly presenting your relevant experience and skills
- The challenge of standing out from the crowded "maybe" pile, where many passionate junior developers end up due to generic projects and experiences
- Tips for increasing your chances of landing in the "yes" pile by demonstrating experience, showcasing personality, and experimenting with different resume approaches to see what resonates with employers

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

Break Into Tech And Become A Software Engineer [Part 7] - The 6 Steps For A Great Side Project

In this lesson, Brian walks through six key steps for creating a meaningful and impactful side project that builds skills, credibility, and even potential business opportunities.

Brian's ["Side Project Template" Google Doc](https://docs.google.com/document/d/1H508NN2HCnnKmkRMgCg3pj_mXr3i8x3Np0jS6w4xzCs/edit#heading=h.cueymdkrqyb1).

This lesson covers:

- Starting with data or APIs to ensure your project is feasible and solves a real problem you care about
- Choosing the right front-end and back-end stack that balances familiar and new technologies while focusing on full-stack development
- Structuring your project with clear user flows, a deployment strategy, and involving real users for feedback, making your project more impressive and valuable in interviews

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

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

Become An Open Source Master [Part 25] - Taking The Next Step In Open Source

We've come to the end of our journey exploring open source contributions.

- This course focused on contributing to existing repositories, not creating your own. Creating a successful open-source project involves technical and marketing challenges. James is doing this right now with TinyBase: <https://github.com/tinyplex/tinybase>
- **Open source takes time and patience**. It takes time to learn a codebase, earn trust, and become a strong contributor.
- Don't get discouraged by rejections or setbacks. Every piece of feedback helps you grow.
- The social side of open source is critical. It's about teamwork, building relationships, and demonstrating your ability to work well with others.

Ask a question in the Taro forum: <https://jointaro.com/questions/create>

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>
- LinkedIn: [**https://www.linkedin.com/in/jamespearce/**](https://www.linkedin.com/in/jamespearce/)

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>

Grow From Junior To Mid-Level Engineer [Part 12] - Disambiguation

Engineers will constantly get tasks that aren't fully defined, especially if they work at a top tech company like FAANG. This lesson teaches you:

- The differences between junior and mid-level engineers when it comes to disambiguation
- How mid-level engineers are much more effective at disambiguation compared to junior engineers, explained with an in-depth example

Top System Design Interview Mistakes [Part 10] - Don't Speak Only in Hypotheticals

In this video, we discuss a common mistake in technical interviews - Talking only in hypotheticals instead of applying knowledge to practical scenarios. Here are the key points we cover:

- Many candidates discuss system design concepts theoretically without considering real-world applications
- We provide an example contrasting a hypothetical approach with a more practical one
- The goal is to show real-world engineering skills, not just theoretical knowledge
- **Our main advice:** Avoid "it depends" answers and make assertive decisions with proper justification

If you need extra help with your system design interview, [Formation.dev](https://formation.dev/partners/taro) can provide you hands-on, personalized support. Join us here: <https://formation.dev/partners/taro>

Why Startups Can Be Better Than FAANG For Career Growth

Whether you are just starting your career or have years of experience in Big Tech, startups can be a powerful accelerator for your career and expose you to unique opportunities.

[**Ben Rudolph**](https://www.linkedin.com/in/brudolph/), cofounder and CTO of Peregrine, argues the value of startups in this talk. Ben built Peregrine from within the San Pablo homicide Investigations Unit where, among other cases, he worked with detectives to help solve a high profile cold homicide case. After spending a year embedded onsite with the customer and securing their first contract, Ben has overseen the growth of the company from 2 to 100+ people. Their technology now serves over 30 million citizens and ingests approximately a million data points every 10 minutes.

Topics covered:

- Understanding how the right startup can offer unique experiences not available in Big Tech.
- Deciding if and when to explore startups for your next career move.
- Effectively evaluating the potential of a startup.
- Common traits of top-performing startup engineers.
- Comparing the mindset required for success in startups vs large tech companies.

Related discussions on Taro:

- [**How to evaluate a startup?**](https://www.jointaro.com/question/UCG4XxyEOTjjyg4pEuwY/how-to-evaluate-a-startup/)
- [**How Effectively Do Big Tech Engineers Perform In Startups?**](https://www.jointaro.com/lesson/TFhKpoVuu4iKdbrAiJ8d/how-effectively-do-big-tech-engineers-perform-in-startups/)
- [**What questions to ask a CTO of a startup?**](https://www.jointaro.com/question/R4FGhmGlZOQK7Lb1YAlt/what-questions-to-ask-a-cto-of-a-startup/)

Peregrine is hiring Senior Engineers in the SF/DC area (or open to relocation) who have 4+ years of experience. Taro members can use this link to get expedited feedback: [**https://www.peregrine.io/taro**](https://www.peregrine.io/taro)

- [**Connect with Ben on LinkedIn**](https://www.linkedin.com/in/brudolph/)
- [**Learn more about Peregrine Technologies**](https://www.peregrine.io/)

Asking Great Questions [Part 24] - Give More Than You Take

The counterpart to asking a question is answering a question, but it's not exactly right to call them opposites as they actually go hand-in-hand! This lesson teaches you:

- How engineers fail to attract and even repel the best engineers to help them
- What you should do to make altruistic, high-performing engineers (i.e. the people you really want answering your questions) want to help you
- Why answering others' questions is one of the best ways to get great people to answer your own questions
- A very tactical self-serving benefit to answering questions and teaching others

Asking Great Questions [Part 22] - Learn To Fish

Getting the answer to your question isn't enough: If you want to respect the person who helped you, make sure to follow through on the end-to-end learning. This lesson teaches you:

- A common mistake engineers make when getting an answer that's too shallow
- What engineers should do to follow-up on an answer and get full value
- Why it's better to potentially annoy your helper with more questions now instead of later
- The difference between knowledge and mastery, why the latter is so critical for your career, and how asking great questions is intrinsically tied to mastery-building

[Become A Go-To Person 4/18] The Benefits Of Being The Go-To Person

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

Get a discount on Jordan's newsletter here: <https://read.highgrowthengineer.com/taro>

Maximize Your Productivity As A Software Engineer [Part 16] - Mentor And Delegate

Many software engineers are naturally lone wolves due to their introverted nature. While this can work out as a junior or mid-level engineer, it quickly becomes unsustainable as you reach senior/staff levels and beyond due to the immense workload. This lesson teaches you:

- Why being a lone wolf is terrible for your productivity
- The importance of uplifting others around you when it comes to getting stuff done
- One of the core virtues the best engineers have, which is particularly needed for mentorship

Here's Alex's Meta mentorship case study: [\[Case Study\] Mentoring Junior SWEs \[E3\] to Senior \[E5\] In Just 2.5 Years At Meta](https://www.jointaro.com/lesson/EX9563YnxcJb62cCmetg/case-study-mentoring-junior-swes-e3-to-senior-e5-in-just-25-years-at-meta/?playlistId=oLssVMdTJ9NtX5SX1fek)

Maximize Your Productivity As A Software Engineer [Part 11] - Not Every Meeting Needs You

Meetings are everywhere at tech companies, especially massive ones like FAANG. The unfortunate reality is that so many of these meetings are wasteful, especially for more junior engineers. This lesson teaches you:

- The huge mistake many n00b engineers make with meetings
- The most powerful tactic you can use to take control of your calendar
- How to figure out which meetings you can skip
- Tactics to safely delete meetings from your calendar

How To Be An Effective Tech Lead [Part 2] - Why Most Tech Leads Suck

There are far more bad tech leads than good tech leads. But why is that? This lesson teaches you:

- How tech leads struggle when they have bad intentions
- How tech leads struggle when they have good intentions

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.