A Simple Trick To Make Your Meetings More Efficient

What can you do before a meeting to empower it to achieve more outcomes?

You write down an agenda for your upcoming meeting, and you realize that it is incredibly rich and complex. What else can you do to level up the meeting?

Preparing and sharing an agenda before meetings—especially manager one-on-ones—leads to more thoughtful discussions and better outcomes.

- **Pre-fill the meeting agenda early**: Add discussion topics at least a day in advance to give others time to prepare.
- **Proactively notify participants**: Ping the other attendees to let them know the agenda is ready and encourage them to review it before the meeting.
- **Avoid putting others on the spot**: Sharing discussion points beforehand prevents “deer in the headlights” moments where participants may not be ready to respond thoughtfully.
- **Encourage richer conversation**: When participants have time to reflect, meetings become more action-oriented and less reactive.

Come Up With 500k+ User Project Ideas [Part 7] - The Alex Formula

Repeated excellence is the key to any very successful tech career. Alex has accomplished this time and time again with around a dozen side projects that have 10,000+ users, and he's here now to spill the beans. This lesson teaches you:

- The exact playbook Alex uses to repeatedly build successful apps with several thousand users
- The "Honer vs. Innovator" philosophy when it comes to understanding engineer types
- Why you should (probably) stop trying to be Steve Jobs and go hard down the innovator route
- How honers are often incredibly underrated and can still achieve stellar career outcomes
- The ideal place to be on the honer &lt;-&gt; innovator spectrum when it comes to side projects

Master The DSA Interview [Part 17] - How To Pass FAANG DSA Rounds

Why is it so hard to break into FAANG? Well, it's because FAANG tends to push engineers far harder on data structures and interviews problems. This lesson teaches you:

- The score spectrum FAANG interviewers use to grade candidate
- What it means to get a "Yes" vote on a data structures and algorithms round
- What it means to get a "Strong Yes" vote on a data structures and algorithms round (very important when the market is bad)
- What a strong passing data structures and algorithms interview performance looks like, explained with an in-depth example

Master The DSA Interview [Part 10] - Run-Time Analysis

After clarifying the problem and coming up with a detailed, granular plan, coding up the solution should have been trivial. Now it's time for big O. This lesson teaches you:

- How to actually learn run-time analysis instead of memorizing the big O of every individual problem
- The structure of a strong run-time analysis for a data structures and algorithms problem
- Exactly what a quality run-time analysis looks like, explained with an in-depth example

Master The DSA Interview [Part 18] - Fishing

Many engineers think that they got rejected due to the interviewer being bad or "out to get them". While low-quality interviewers do exist (and there are a lot of them), it is often the engineer's fault by being a weak candidate. This lesson teaches you:

- Why there is often a discrepancy between what engineers believe is the cause of their data structures and algorithms interview rejection and what reality actually is
- What fishing is and how it forces interviewers into a very awkward situation that makes them seem icy to the candidate
- How to not do fishing during an interview so you can have a real chance of passing (and make the interviewer more likely to help you)
- Why asking the interviewer for a raw hint is a recipe for failure

Negotiation Course: Negotiating With A Single Offer

It is possible to negotiate with a single offer, but you are in a weaker position here since you don’t have as much leverage.

- Use "market data" to justify a higher pay, and talk about how your experience and background should justify being on the top end of that range.
- Talk about the ***potential*** of other opportunities that you could pursue but you choose not to for the sake of expediency and the fact that you like this job. "*I could get another offer, but I don't want to if I you can give me a competitive offer.*"

Two scenarios to consider:

1. If you’re currently employed, use that to your advantage. Pretend that you like your current job (maybe you actually do!) and that you have to be "pried away". Talk about what you're leaving on the table, e.g. unvested equity or bonus payouts.
2. The **Close the Deal** tactic is nice here. "For an extra $10k, you can snatch me away instantly."

Do This To Get Maximum Value From Your Manager 1 on 1s

The manager 1 on 1 meeting is arguably the most sacred and high-leverage time you have in your career. Make sure you don't waste it by stumbling in with 0 preparation.

Here are the core points from the video:
- **Come in with a plan** - In your running meeting notes doc, write down the agenda beforehand with discussion points ordered by priority. Not only does this make your meeting more effective, it improves the perception of you from your manager's eyes as it shows that you're being more respectful of their time and you're more serious about your own growth and productivity.
- **Alert your manager of the plan 24+ hours beforehand** - This allows them to "pre-compute" the best responses to your meeting topics, so they don't get caught like a deer in the headlights with the trickier ones. It also makes it harder for your manager to cancel, especially when you have deeper, more important topics on the agenda.

Related resources:
- [[Taro Top 10] Software Engineer To Engineering Manager (IC -> M Track)](https://www.jointaro.com/playlist/oz0mnJvHHgM8NfVF7rgp/)
- [[Masterclass] What Software Engineers Should Look For In Their Engineering Manager](https://www.jointaro.com/lesson/oeY7ncZhzJ5NO6dij5e7/masterclass-what-software-engineers-should-look-for-in-their-engineering-manager/)

Write A Stellar Resume As A Software Engineer [Part 18] - Non-Technical Experience

A lot of software engineers don't have a Computer Science degree and switched into software from a non-technical background. So how can those engineers succeed with their resume? This lesson teaches you:

- What transferable skills are
- How to best frame your non-technical experience on an engineering resume, broken down with an in-depth example

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

How To Recover After You've Been Laid Off In The Tech Industry

Steven Zhang and Chris Talley are 2 incredible software engineers who have worked at Airtable, Airbnb, Meta, and more between them. They have advised hundreds of engineers who have been laid off about how to recover, and this session shares that wisdom.

Here are the core points from the video:
- **Don't blame yourself** - Getting laid off is very different from being fired. Layoffs are purposely random and made with very limited information - It is not your fault that you got cut. Being part of a layoff has no indication towards your ability as an engineer or your quality as a person. *As long as you did your best at the company and treated others well, you should be proud.*
- **Figure out your severance** - Make sure the amount and time period you're kept on payroll are correct; the latter is especially important if you're on a visa. If you have the resources, you can get a lawyer to look over it. After you figure out the package timeline, file for unemployment benefits accordingly - California in particular is pretty generous with unemployment pay. These packages can be negotiated as well: [Laid Off? Here's How to Negotiate Your Severance Package](https://www.teamrora.com/post/how-to-negotiate-severance-package-when-laid-off)
- **Organize** - If you were laid off from a Big Tech company in particular, there's a very good chance that it has an alumni community: Join it! If your company doesn't have an alumni community, make one. Communities are great for sharing resources and boosting your mental state by interacting with others in a high-solidarity environment. You can find a list of company alumni communities here: [WARNTracker - Tech Company Alumni Communities](https://www.warntracker.com/blog/company-alumni-communities)

Here's the case study Steven did about his legendary interview run in 2019: [[Case Study] How To Land 18 FAANG+ Offers With Steven Zhang (Airtable, USDR, Tableau)](https://www.jointaro.com/lesson/gGkO4pLeFq1ctRM9tSBF/case-study-how-to-land-18-faang-offers-with-steven-zhang-airtable-usdr-tableau/)

Connect with Steven and Chris on LinkedIn:
- [Steven Zhang](https://www.linkedin.com/in/stevenqzhang/)
- [Chris Talley](https://www.linkedin.com/in/christophertalley/)

Steven's and Chris's businesses + side projects:
- [WARNTracker.com](https://www.warntracker.com/) - Learn more layoff trends and find helpful resources
- [ClimateTechList.com](https://www.climatetechlist.com/)- Find jobs at companies that are meaningfully tackling climate change
- [RationalRiches.com](https://rationalriches.com/) - Free tools for real estate investors

For more resources on layoffs:
- [[Masterclass] How To Survive Tech Industry Layoffs](https://www.jointaro.com/lesson/axnVXYox5QeOneqcoyuH/masterclass-how-to-survive-tech-industry-layoffs/)
- ["What are the signs of an impending layoff in an organisation that can help an employee prepare themselves better?"](https://www.jointaro.com/question/tNOO9FtALQIRrUXSqzV1/what-are-the-signs-of-an-impending-layoff-in-an-organisation-that-can-help-an-employee-prepare-themselves-better/)
- ["How to survive potential layoffs?"](https://www.jointaro.com/question/ydZFpJz0x8wKUIfd8E1r/how-to-survive-potential-layoffs/)

Become An Engineer Influencer [Part 3] - Strategy #1: Catering to Your Strength

Master The Behavioral Interview [Part 23] - Just Be A Human

Behavioral interviews are really just an exercise in communication (a skill many software engineers struggle with). This lesson teaches you:

- The difference between being an introvert (this is fine) and shy (this is really bad for your career in tech)
- The right mindset to have when it comes to building relationships and the underlying skills necessary to ace behavioral interviews
- The secret behind getting extremely good at communication

To get better at communication, check out our course: [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)

Nail Your Promotion As A Software Engineer [Part 19] - Depth Of Contribution

Just because you got a meaty, high-impact project doesn't necessarily mean that you'll get rewarded a lot for it when it comes to your promotion case. This lesson teaches you:

- Why volume of code contribution often doesn't correlate with the depth of your contribution and the credit you receive
- How to figure out if your project contributions had lots of depth
- Concrete examples of hard tasks that have great depth and are greatly rewarded for in promotion cases

The First Step Of Debugging - Reproducing The Issue

The first thing you need to do when you get a bug is to see it happen with your very own eyes. From there, you can execute the steps necessary to identify the root cause and fix the bug. However, a lot of engineers aren't diligent enough when they try to get the repro.

This video is a clip from our debugging masterclass. You can watch it here: [[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/)

Related resources:
- [[Case Study] Revamping Oncall For 20 Instagram Engineers - Senior to Staff Project](https://www.jointaro.com/lesson/esVxIGXYC5BdgxXUkO6H/case-study-revamping-oncall-for-20-instagram-engineers-senior-to-staff-project/)
- [[Case Study] Solving A Multi-Million $$ Instagram Bug](https://www.jointaro.com/lesson/WYk4J05iBqOuPtD0CYKX/case-study-solving-a-multi-million-dollardollar-instagram-bug/)
- ["How can I become more independent and better at unblocking myself with tricky technical issues?"](https://www.jointaro.com/question/QhqQQGrDgFjZbqohpKe0/how-can-i-become-more-independent-and-better-at-unblocking-myself-with-tricky-technical-issues/)

Part 2 [RBP] Derive State When Possible

This lesson focuses on optimizing React state management for better performance and code organization.

- **Deriving State:** Learn how to calculate and derive state values directly within your component instead of storing redundant data, leading to more efficient and maintainable code.

- **Avoiding Unnecessary Re-renders:** Understand the impact of state changes on component re-renders and discover techniques to minimize them, such as using `useMemo` for expensive calculations.

- **Improving Code Clarity:** Explore how to simplify your state logic and reduce complexity by deriving state and avoiding unnecessary `useEffect` calls.

- Florian’s free web development playlist on YouTube: <https://www.youtube.com/playlist?list=PLrnPJCHvNZuDG6BWjUFVxeWyYlve_SVJO>

- Code link: <https://github.com/codinginflow/react-best-practices/blob/derive-state/src/app/page.tsx>

Job Switching Is Great For Pay But With Major Caveats

This video segment explores **job switching as a strategy to increase compensation**, acknowledging its significant financial benefits while outlining important limitations. It offers a balanced view of when and how to leverage this option effectively within a career in tech.

- **Job switching can deliver major pay increases**, especially when moving from lower-paying companies to top-tier tech firms like Facebook, Google, or Airbnb. Offers from these companies often represent a different compensation tier altogether.
- **The current tech market is highly competitive**, driven by remote work and talent shortages, which makes switching jobs particularly lucrative for engineers not already paid at “top of market” rates.
- **However, job switching comes with diminishing returns**. Frequent transitions (e.g., every 6–12 months) can raise red flags for recruiters due to high costs of hiring and onboarding, making a two-year tenure the informal minimum standard.
- **Banding limits how much pay can increase** through switching if already working at top-tier firms. For example, a mid-level engineer will only be offered a similarly banded role and compensation elsewhere.
- **Job switching doesn’t contribute to actual growth as an engineer**. Preparing for interviews (e.g., Leetcode) is time-consuming and doesn’t improve the long-term skills needed to succeed or progress to leadership roles like principal engineer.

You tried to be clear. They heard threat.

The words were fine.\
The logic was solid.\
The delivery? Unclear. At least to them.

This is the story of feedback that missed—badly—and why it had nothing to do with the message.\
You’ll walk into a moment that cost more than expected… and learn why it’s so common.

**Want to go deeper?**

- Explore more tools and courses at [**Taha’s Method**](https://www.tahasmethod.com/) — from interview prep to leadership development.

- Follow me on [**LinkedIn**](https://www.linkedin.com/in/tahahussain/) and subscribe to my weekly newsletter, [**The Conscious Leader**](https://tahahussain.substack.com/), for more lessons like these. 

- **Taro members get 30% off** my flagship course [**Top Tech Leader**](https://bit.ly/tarotopleader)*. Discount available later in the course.*

Negotiation Course: Helpful Phrases During Negotiations

The phrases covered here are applicable in various scenarios as you go through the interview process.

Negotiations require a deliberate choice of words, avoiding apologies, and showcasing your value beyond just compensation. By using these phrases, you can confidently navigate negotiations and achieve your desired outcomes.

> Interesting.

> Compensation is definitely important for me, but I care a lot about the people I work with and what I’m working on.
>
> I want to do my best work in a company that values me.

> *At this time, I’m more interested in understanding the company and people rather than the compensation.*

> *I’m sure we can work out the compensation if we think this is a mutual fit.*

> *I have a few other opportunities I’m in the process for, but if this is compelling enough I’m ready to commit.*

> That role wasn’t a great fit, so I’m exploring adjacent opportunities.

> My focus is to have tons of impact at the company and I want to take part in the success.

> This is a large decision and I want to commit fully to the job I end up choosing.
>
> I want to do right by the company I join and build the next part of my career there.

> *If you could send over the offer, I’d love to take a look in more detail.*

> *I’m chatting with my partner about the job stuff so I should be able to give you an update after that.*

Ace Your Tech Interview As A Software Engineer [Part 36] - Getting Interview Feedback

The best way to get better at software engineer interviews is to fail a bunch of software engineer interviews. But how exactly do we do that? This lesson teaches you: 

- Why you're probably not getting feedback from the company after you have failed their interview
- What you should do instead after an interview to maximize the learning that you get from the experience

Entry-Level Engineer (L3) Describes Most Important Skill - Uriel Sejas

Uriel is a new grad engineer at Slack.

- Most important skill: understand and follow patterns in the codebase. There's likely a well-defined template or approach you can follow to complete your work. 
- Advice: take time to connect with other engineers. An engineer on a different team (build system or UI framework) can share something that otherwise would have taken hours/days to figure out.

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:
- [[Masterclass] How To Write Better Code Faster As A Software Engineer](https://www.jointaro.com/lesson/iYpRj8XfyzCSaTYnce3y/masterclass-how-to-write-better-code-faster-as-a-software-engineer/)
- [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/)
- [Uriel on LinkedIn](https://www.linkedin.com/in/uriel-sejas/)

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.