What People Get Wrong About The Manager To Software Engineer Relationship

In this lesson, we discuss the common mistake that senior engineers commit, which is that they continue to assume that the manager is an authority figure.

This is often the case, but doesn't have to be. David talks about a case in his past job where an IC on the team was more senior than him as the manager. And the IC engineer was objectively more important to the team, indicating the value of this senior-level person not only to getting work done, but also setting direction and giving feedback to others.

Senior engineers should view the relationship with the manager as a partnership rather than a person for whom they must *follow orders*. **The tech lead and manager have different but overlapping responsibilities in helping the team succeed**. Realizing this unlocks a more fruitful collaboration.

Remember, managers will frequently have blind spots that a tech lead can point out. These insights and observations may manifest in actually pushing back on the manager's plans or strategy. This is a role that senior engineers should embrace.

- More from David: <https://www.jointaro.com/topic/david-pan/>
- [Onboarding as a Tech Lead at Robinhood in 1 Month](https://www.jointaro.com/lesson/X8vpfJooDpsX915ouC00/case-study-becoming-a-tech-lead-again-in-just-1-month-after-joining-robinhood-from-meta/)
- [The EM "Partner In Crime": The Tech Lead](https://www.jointaro.com/lesson/uZQZlS6tdXbztajM0tqa/the-em-partner-in-crime-the-tech-lead/)

DSA Interview Step Finale: Analyze Your Solution

You should proactively go over the time requirements, space requirements, and edge cases of your coding solution once you're finished coding.

Related resources:
- [[Taro Top 10] Effective Interview Prep](https://www.jointaro.com/playlist/HLBYxJI7D1j8STolrwum/)
- [[Taro Top 10] Finding A Tech Job](https://www.jointaro.com/playlist/E6R0wVJ5EyCfVnVrlfno/)

The Amazing Non-Money Benefits Of Working At Big Tech

The Resource You Need For Promotion That Few Understand

Which of the following is the resource needed for promotion that many engineers don't understand or even realize exists, particularly more junior ones?

True or false: When you are onboarding as a software engineer, the one and only thing that matters is your ability to understand the codebase and extend it.

Why is social capital important for senior engineers?

Why Time Is The Most Important Resource In The Tech Industry

Which one of these is a crucial skill working in a top tech company?

True or false: Time is an overpowered, often underappreciated resource.

20 Years Of Fighting Procrastination [Part 15] - Conclusion

Congratulations on making it to the end of the course! While watching great content like this feels good - It doesn't actually mean anything unless you put the learnings into practice. With that being said, here's some ideas for "homework" for you:

- Start sleeping consistently every day, even on weekends
- If you have a task or project that will take at least 1 week, decompose it into at least 3 different sub-tasks
- Set up a meeting with yourself on a regular basis to reflect on your productivity
- Go through your calendar, audit all the meetings, and kill as many as you can

If you want to learn how Rahul's cofounder Alex made $750,000 per year at Robinhood working \~35 hour weeks, you can go to the next level and take his much deeper and more concrete productivity course here: [Maximize Your Productivity As A Software Engineer](https://www.jointaro.com/course/maximize-your-productivity-as-a-software-engineer/)

DSA Crash Course [Part 19] - Recursion Warm Up Lecture

In this lecture, Alvin explains some basic recursive function examples.

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

Master The DSA Interview [Part 8] - Clarify The Problem

Don't just start coding when you get a data structures and algorithms problem in an interview. This lesson teaches you:

- The first thing you should do when getting a data structures and algorithm problem, which is critical for setting you up for success
- Why dealing with ambiguity is so important as an engineer
- The overall question categories you should pull from when clarifying a problem
- How exactly to clarify a data structures and algorithms problem, shown with an in-depth example

Break Into Tech And Become A Software Engineer [Part 4] - Why Foundation Is Crucial

In this lesson, Brian emphasizes the importance of building a strong technical foundation in order to succeed long-term in the tech industry.

This lesson covers:

- The risks of becoming a "framework developer" without understanding core programming concepts, which can jeopardize career stability
- Brian’s personal experience of having to attend two bootcamps to fill in gaps in foundational knowledge, despite already being in the industry
- The importance of understanding the underlying technologies, not just frameworks, to boost both career growth and confidence

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

Top System Design Interview Mistakes [Part 14] - Don't Save the Hardest for Last

In this lesson, we focus on the importance of addressing the most challenging aspects of a system design problem early on:

- We often make the mistake of delaying the hardest parts of the problem. While starting with simpler tasks might seem productive, it can lead to incorrect design choices and suggest we're unaware of the core challenges

- We should immediately focus on the most complex parts of the problem. Tackling these challenges first demonstrates our understanding and prevents us from getting sidetracked by less critical aspects

- In our interview example, we show how the candidate misses the core problem behind the messaging app, tackling the simpler pieces instead

- Effective problem solving involves working through strategies for the hardest issues, like the message-to-notification fan-out, and evaluating their pros and cons

- By focusing on the toughest problem first, we show strong judgment and prioritization skills. This approach ensures that we manage our time well and address the most critical aspects of the design effectively

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>

Top System Design Interview Mistakes [Part 6] - Freezing on the Spot

In system design interviews, clear communication is crucial. Many candidates struggle not because they lack knowledge, but because they fail to express their ideas effectively. This video highlights a common issue: Freezing under pressure.

- Instead of freezing when faced with a complex problem, keep the conversation going by asking clarifying questions. This not only helps you gather necessary information but also engages the interviewer.
- If unsure what to ask, focus on understanding the system’s functionality. Questions about the product’s purpose and user journey can guide your design process.
- Involving the interviewer through questions shows your experience and keeps the interview on track.

In short, don’t let nerves stop you—ask questions to maintain momentum and communicate effectively.

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>

Maximize Your Productivity As A Software Engineer [Part 21] - Verify Your Foundation

Work and life are deeply interconnected, despite how much we want this to not be the case. If your personal foundation isn't there, it's hard to get anything done working a mentally-intensive job like software engineer. This lesson teaches you:

- How it's possible to implement literally all the advice from this course and still not be productive
- What to do if you're stuck in a productivity rut that you just can't get out of
- The ingredients behind a healthy personal foundation

Learn more about how to have good work-life balance here: [\[Taro Top 10\] Work-Life Balance](https://www.jointaro.com/playlist/JNCZ1vbRF3NwsOQCqblt/)

Maximize Your Productivity As A Software Engineer [Part 5] - Focus On The System

Many software engineers simply tell themselves *"I'll do better next time"* when they have an unproductive period - This almost never works. This lesson teaches you:

- Why relying on sheer willpower to be productive is a terrible idea and what you should do instead
- What it means to have a true system around your productivity
- The objectives of a productivity system

Maximizing a Severance Package 9/9 - Summary

Watch Ethan's other course on Taro about [Managing Up](https://www.jointaro.com/course/managing-up-build-effective-relationships-with-your-boss/) and [The Growth And Promotion Recipe](https://www.jointaro.com/course/the-growth-and-promotion-recipe-magic-loop/)

Follow ups:

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

Write A Stellar Resume As A Software Engineer [Part 17] - Projects

In this day and age, 99% of software engineers have a "Projects" section on their resume. Of those engineers, 90%+ of them won't get any benefit from their "Projects" section when it comes to their resume passing the recruiter screen and getting them an interview. This lesson teaches you:

- Why projects are at a natural disadvantage compared to work experience on your resume
- What it takes to make a personal project actually impressive on your resume
- The proper link to include to show your project
- How to make a project GitHub actually have the chance to impress a recruiter and get you an interview

To get more users on your side project: ["\[Side Project\] How to get more users + interviews?"](https://www.jointaro.com/question/Z456XTkusKszxcHjVfYA/side-project-how-to-get-more-users-interviews/)

Onboarding Tips Within Larger Companies

In a large company, you should expect a more formal onboarding process. However, don’t let this be an excuse to move slowly. Your goal is (still) to set up your environment and land code within a week.

Big companies will have many teams which may have slightly competing priorities. That means you need to invest in relationships and understand how the work connects between teams. Disperse and collect knowledge from around the company.

Spend some time understanding the unique terminology and culture of the company. Companies like Amazon, Meta, Google, Microsoft are large enough that they have their own set of acronyms, languages, and cultures!

Figuring Out What Matters In A Codebase

In a large codebase, the code will follow the Pareto Principle (the 80/20 rule): 20% of the components account for 80% of the impact. So your goal as the engineer is to spend most of your time on the 20% of code that matters to the business and matters to your coworkers.

How do you figure out where that 20% comes from?

- Talk to people
- Use blames to find hotspots
- Look for patterns in code reviews
- Look at past alerts and what triggered them

Mid-Level Engineer (L4) Describes Most Important Skill - Dipika Tiwari

Dipika is a mid-level engineer at Qualcomm.

- **Most important skill**: efficient log analysis. Being able to quickly make sense of the bug report and provide actionable next steps is critical for productivity and trust. 
- **Advice**: keep notes as you ramp up, since that information will likely be useful later on.

Here's the full playlist asking engineers what the most important skill is for their level: [Asking 7 Levels Of Engineers The Most Important Skill](https://www.jointaro.com/playlist/J9Io5lDGaYUpI8vGrUyI/)

Helpful links:
- [How Neetcode Got Promoted From L3 to L4 (Mid-Level) Engineer At Google - Tips + Insights](https://www.jointaro.com/lesson/mP1jyI09NsCHDsi5yTEX/how-neetcode-got-promoted-from-l3-to-l4-mid-level-engineer-at-google-tips-insights/)
- Taro's top 10 to get promoted from [entry-level to mid-level engineer](https://www.jointaro.com/playlist/iBKHYpkjd0BRWWLKQG2j/)
- Taro's top 10 to get promoted from [mid-level to senior engineer](https://www.jointaro.com/playlist/AUMiBTvYUv0gcOzuu26V/)
- [Dipika on LinkedIn](https://www.linkedin.com/in/dipika-tiwari/)

At Big Tech, You're Just A Cog In The Machine

Many people idolize FAANG companies, because they own these amazing products that everyone uses. However, working on these products is rarely as glamorous as people think: The experience is often worse the more successful the product is.

Here are the core points from the video:

- **Your ownership will probably be super tiny** - This is especially true at non-senior levels (junior and mid-level). Big Tech companies have thousands of amazing, ultra-productive engineers, and there's only so much ownership to go around. It's not uncommon for a Big Tech engineer to make $200k+ per year mainly working on a single button.
- **The work is very incremental** - Since Big Tech's product suite is so mature, it's very hard to find 0 to 1 work there, which people generally find to be more exciting. Almost all "shipped" code is wrapped in an experiment at Big Tech, and a lot of these experiments will fail.
- **It can be hard to feel fulfilled** - It's not the most exciting to own a single widget within a feature within a broader service within the overall product, and it's definitely not something that's cool to share when people ask you what you do.

Related resources:

- ["What's the difference between Big Tech and startups in terms of learning and growth?"](https://www.jointaro.com/question/KWXIrFIR1EIJsvdOdo7u/whats-the-difference-between-big-tech-and-startups-in-terms-of-learning-and-growth/)
- ["What does it mean to not have enough scope to be promoted?"](https://www.jointaro.com/question/bJuagPwOEEy5vkcXKkqh/what-does-it-mean-to-not-have-enough-scope-to-be-promoted/)

"What does your day to day look like?" - 8/19/2022

- *In short, it varies a **lot**.* Startups are extremely unpredictable, and the biggest problem facing the company will change every month or even every week.
- However, there are 2 constants:
  - **Talking with new Taro Premium members** - We chat 30 minutes with every new member to get to know them, make sure they're set up properly within the community, and understand their job and career goals. These meetings add up, and we have a decent amount of them every day.
  - **Talking with Rahul** - There's always a ton going on, and we always have a bunch of ideas on how to evolve Taro, so we need a lot of time to talk each day, usually 45 minutes to 1 hour. According to YC, cofounders falling out is the #1 reason startups fail, so we really want to make sure that doesn't happen.
- We try to get a decent amount of code in every week, but it's hard to find time for it and the company's top priorities are often times not build related.
  - On a side note, the highest build priority for us right now is to really make the Taro web app silky smooth.
- We are fundraising right now, so that's dominating our lives.
- We have a lot of meetings in general as networking is crucial for startups.

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.