Nail Your Promotion As A Software Engineer [Part 30] - Be Patient

It can be frustrating waiting so long to get promoted as a software engineer. You've been working so hard for so long, and you still don't have that fancier title. This lesson teaches you:

- Why getting promoted is so hard
- The right mentality to always have as you're going through the promotion process
- A clear framework you can use to determine if you are truly getting better as an engineer

Nail Your Promotion As A Software Engineer [Part 20] - Quality Of Delivery

Anything worth doing is worth doing right, and this applies to software engineers as well. This lesson teaches you:

- Why quality of delivery is such an important project axis when it comes to promotion, especially to senior levels and beyond
- The immense value of smooth delivery when it comes to your perception among engineering leadership
- Concrete angles to consider when maximizing your quality of delivery

Nail Your Promotion As A Software Engineer [Part 8] - Avoid Level Overload

Not all teams are created equal when it comes to promotion opportunity, far from it in fact. Don't sleep on this crucial angle when it comes to planning out your promotion plan as a software engineer. This lesson teaches you:

- The 2 types of level overload to avoid and which one is worse
- How to a team that has a healthy mix of levels vs. one that doesn't
- Why level overload is bad, particularly when there's a lot of engineers at the same level you are

How To Avoid PIPs: The Ultimate Guide To Navigating A PIP

**Prevention is the best cure**, so let’s talk about what steps you should take to avoid a PIP. The #1 thing you can do is get high-quality feedback from the people you work with. The issue is that most tech workers are horrible at asking for feedback in a way that actually gets them something substantive.

Your guiding principle should be to **make it easy to receive feedback, especially constructive feedback.**

Here’s a system you should employ to get high-quality feedback: 

- Schedule dedicated “feedback 1:1s” with key people: manager, XFN partners
- Write down what they say
- Follow up: short-term and long-term

A PIP should **never** be a surprise, and yet it often Is. This system will prevent you from being negatively surprised. With a manager, you ask how you’re trending and discuss a hypothetical rating, broken down by the axes of evaluation at your company.

We also cover two examples of proactively addressing concerns with your manager.

Amazon VP Shares Why Reorgs Happen And Why The True Reason Is ALWAYS Hidden

[**Ethan Evans**](https://www.linkedin.com/in/ethanevansvp/) is a retired Amazon VP who has gone through dozens of re-orgs across his tech career.

Re-orgs (reorganizations of the team structure) happen because at least one leader views something as broken: someone is under-performing, the right teams aren't collaborating, or some other reason which you may not have visibility into as an engineer.

Once a re-org happens, an effective way to build trust is to schedule time with your new skip level manager and ask what the mission of the team is, and if your work is still aligned to that mission. Ask your manager to setup a meeting if you can't do it on your own.

Communication challenges: Public announcements about such org changes often use vague language and corporate jargon, making it difficult for individual contributors to understand the true reasons behind them. This lack of transparency can lead to further confusion and distrust.

Legal considerations: Legal constraints limit how much information leaders can publicly disclose about personnel changes. Fear of lawsuits can lead to sanitized messages that obfuscate the real reasons behind decisions.

**More to explore:**

- [\[Masterclass\] How To Work Better With Your Engineering Manager](https://www.jointaro.com/lesson/2PbJb2fuqF3iMHy57eEg/masterclass-how-to-work-better-with-your-engineering-manager/)
- [How To Effectively Leverage Skip Level 1:1s](https://www.jointaro.com/lesson/TToehFEc738PBhJcALwL/how-to-effectively-leverage-skip-level-11s/)
- [Ask Me Anything (AMA) with a Disney Eng Director - Greg Benson](https://www.jointaro.com/lesson/eHbg5nVkHn2LYJ55oOVf/ask-me-anything-ama-with-a-disney-eng-director-greg-benson/)

Was Getting A Masters While Working Worthwhile? From a Distinguished Engineer

Andrew Zhai was a Distinguished Engineer at Pinterest.

After graduating from UC Berkeley in 2013, Andrew started working at Pinterest in Computer Vision. Within a few years, he decided to do a part-time Masters degree from Stanford to build his foundational knowledge of Machine Learning and Deep Learning.

Andrew says the academic rigor and the courses helped him achieve success in industry. For the Machine Learning (ML) field in general, the field evolved quickly enough that going 'back to school' was worthwhile.

[Andrew on LinkedIn](https://www.linkedin.com/in/andrew-zhai-2796ab34/)

Related:

- [Does having a Master's mean I can expect a salary equivaent of a 2 YoE SWE?](https://www.jointaro.com/question/YSMUN3uxDmGLqKxIvmXI/does-having-a-masters-mean-i-can-expect-a-salary-equivaent-of-a-2-yoe-swe/)
- [Do I need to do masters in Computer Science to move ahead in career?](https://www.jointaro.com/question/tKuUT3ELEa1uCGBuMykX/do-i-need-to-do-masters-in-computer-science-to-move-ahead-in-career/)
- [Is an online Master's Degree in Computer Science worth it for a non-CS Bachelor's degree holder with 2 YOE?](https://www.jointaro.com/question/Qth4ohK7HbHTEC83dwIJ/is-an-online-masters-degree-in-computer-science-worth-it-for-a-non-cs-bachelors-degree-holder-with-2-yoe/)
- [Rahul's Computer Science Masters Degree from Stanford in 7 Minutes](https://www.youtube.com/watch?v=iDu6slRfLY4)

How To Land 18 FAANG+ Offers With Steven Zhang (Airtable, USDR, Tableau) [October 2023 Version]

While on the job hunt in 2019, Steven Zhang received 18 offers (out of 22 onsites), including from companies such as Airbnb, Apple, Facebook, Palantir Technologies, Pinterest, Stripe, Uber. If you're interested in learning from Steven as part of a cohort-based course about job searching, sign up here: [https://bit.ly/18offers-course](https://bit.ly/18offers-course)

In the process, he became an expert in software engineering interviews and job searching. Steven shared his thought process and methodology:
- When you have many interviews, **operationalize it, and treat it like a multi-week/month project**. Some days will feel like a slog, but that's ok and part of the process. (Steven used Airtable to coordinate all his conversations.)
- **Doing an interview prep course is completely worth it for DSA**. It may cost a few thousand dollars, but being able to land the ideal job is definitely worth it (and likely worth tens of thousands of $$). Steven used InterviewKickstart (his referral: https://bit.ly/swe-tips-ik).
- **For behavioral interviews**, Steven recommends:
    - Writing all questions you received in a Google doc
    - Recording yourself doing mock interviews with a friend and then listening to it. 
- **Steven received offers at various levels through the bands**, from L3 (junior) to L5 (senior). Your level has huge implications for your compensation.
- Negotiation tips: 
    - Negotiation should not be adversarial- think of it as doing price discovery
     - If you ask nicely, no one will rescind your offer for asking for more money.
     - Negotiation/post team matching is a way to get signal on the company itself

Relevant resources: 
- [[Masterclass] How To Ace Your Big Tech Interview - Data Structures And Algorithms](https://www.jointaro.com/lesson/V4sTACzfOh22nMVcUV3w/masterclass-how-to-ace-your-big-tech-interview-data-structures-and-algorithms/)
- [[Masterclass] How To Ace Your Big Tech Interview - System Design](https://www.jointaro.com/lesson/J3I9fTW9ulr6T9KjxpqY/masterclass-how-to-ace-your-big-tech-interview-system-design/)
- [How Alex Got Into Meta With 0 Prior Leetcode Experience](https://www.jointaro.com/lesson/ZYiTbN21FsqFxFdpwt5a/how-alex-got-into-meta-with-0-prior-leetcode-experience/)
- [Steven's original talk on Taro about receiving 18 offers](https://www.jointaro.com/lesson/gGkO4pLeFq1ctRM9tSBF/case-study-how-to-land-18-faang-offers-with-steven-zhang-airtable-usdr-tableau/)
- Steven's [viral Medium article about this experience](https://medium.com/@stevenzhang/how-i-landed-18-faang-software-engineer-offers-after-not-interviewing-for-5-years-fc0dfc957a5d).
- Connect with [Steven on LinkedIn](https://www.linkedin.com/in/stevenqzhang/)

Stop Bugs From Happening Again - The Importance Of Retrospectives

Bugs are often times like ants: They don't come alone and are often representative of many more of their own kind. After you fix any bug, retrospect on why it occurred to begin with and what the team could have done to prevent it. If the bug was very serious (e.g. a production outage), bring the team together with a formal post-mortem report and meeting.

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:
- ["What's the difference between a low performer software engineer and a high performer?"](https://www.jointaro.com/question/nMxx2EMVIlJbl1oK4SGu/whats-the-difference-between-a-low-performer-software-engineer-and-a-high-performer/)
- [[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/)
- ["How to turn a string of silly mistakes into a mature positive outcome?"](https://www.jointaro.com/question/JybGyc935lsYbM8dAo7Y/how-to-turn-a-string-of-silly-mistakes-into-a-mature-positive-outcome/)

This Is The Easiest Way To Get Better At Debugging

Before you go into any bug, it's important to write down all the relevant details into a task or ticket. Here's why:
- It makes it easier to get your bearings and start looking into the right places for debugging
- If you need to pass the bug to someone else, the knowledge transfer is much smoother as you have this artifact
- The written context will be very valuable for retrospectives

Here's the information you should put down:
- Steps to reproduce the issue
- The blast radius
- Relevant code pointers
- Priority of the bug

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] 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/)
- ["What is the effective way to understand new repository in order to make the required changes in that repo?"](https://www.jointaro.com/question/KoxB3UU2zWC9pdYU6Rx0/what-is-the-effective-way-to-understand-new-repository-in-order-to-make-the-required-changes-in-that-repo/)

To Fix Software Bugs, You Must Understand Their Blast Radius

It's not enough to be able to reproduce the bug on your own device: You need to fully understand the blast radius as well. This will help you fully understand the bug and fill out the post-mortem report afterwards.

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] 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/)
- ["What is the effective way to understand new repository in order to make the required changes in that repo?"](https://www.jointaro.com/question/KoxB3UU2zWC9pdYU6Rx0/what-is-the-effective-way-to-understand-new-repository-in-order-to-make-the-required-changes-in-that-repo/)

Autism Allyship and Identity in Tech - By Lee McKeeman & Jaswir Raghoe

[Lee McKeeman](https://www.linkedin.com/in/lmckeeman/) and [Jaswir Raghoe](https://www.linkedin.com/in/jaswir-raghoe/) give an insightful talk on Autism Allyship in the tech industry, and how one can discover the power of creating inclusive workplaces for autistic individuals while gaining valuable tips on how to be an effective ally to autistic colleagues.

Lee and Jaswir talk about how autism is a spectrum with individuals having a wide range of abilities and needs. They give a deeper understanding of general biases and assumptions about autism, and learn why it's crucial to challenge them. They expound on the importance of asking autistic individuals about their preferences and needs, while understanding the significance of respecting their boundaries. Jaswir and Lee uncover the value of patience and understanding, as well as the importance of not expecting autistic individuals to always conform to social norms.

Join us in celebrating the diversity of autistic individuals and learn how you can become an advocate for their inclusion in the workplace.

Don't miss this enlightening talk that will empower you to create a more inclusive and supportive environment for all.

Incase you missed it, also check out Lee McKeeman's previous talk about his career journey: [An Autistic Journey To Google Staff Engineer [L6] From Software Analyst](https://www.jointaro.com/lesson/nujUVma6boGJxGAQzoiX/an-autistic-journey-to-google-staff-engineer-l6-from-software-analyst-by-lee-mckeeman/)

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

[Part 3] Software Engineer Onboarding: Understand Tactical Decisions

Learn the product to make good tactical decisions.

Within the first few weeks of your onboarding, you should have have fixed a few bugs and . Now it's time to slow down a bit and do some reflection on the decision-making process and priorities of the team.

- [How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/how-to-build-deep-relationships-quickly-in-tech-12172022/)
- [The Crucial First Step To Building Relationships That Everyone Misses](https://www.jointaro.com/lesson/YPniDFNQqoHEpYHC9JEq/the-crucial-first-step-to-building-relationships-that-everyone-misses/)

This is part 3 of a 4 part series from Daniel about how to **most efficiently** and **most effectively** onboard into a new team or company. What should you spend your time doing in the first few months of joining, and how should that change based on your level? 

This masterclass covers this topic from the perspective of Daniel Tomko, a 20 year Big Tech veteran. Daniel spent 11 years at Microsoft and 8 years at Meta in various senior IC and management positions. 

- [Go to part 4 of the masterclass here](https://www.jointaro.com/lesson/JFvfEoKshdPWuiCuy3GY/part-4-software-engineer-onboarding-understand-strategic-decisions/)
- [Go back to part 1 of the masterclass here](https://www.jointaro.com/lesson/IYZRmwp33E3TBeFQFr9c/part-1-software-engineer-onboarding-embrace-your-lack-of-knowledge/)

The Most EVIL Way To End An Interview (And How Not To Do It)

Here are the core points from the video:
- It is **never** okay to end an interview early because the candidate wasn't good enough. This is immensely disrespectful, especially for an onsite interview where the candidate carved out an entire day to do it (likely taking PTO if they are currently working).
- As an interviewer, you are also representing your company. If you do this, you are hurting your company's reputation as people talk - That candidate is very likely to tell others that your company is a horrible place to interview at.
- When this scenario happens, *the proper thing to do is to switch gears and go entirely into maximizing candidate experience* (as your goal isn't collecting signal anymore). This involves:
  - Giving them hints aggressively to help them complete the problem
  - Pair programming with them and trying to teach them - Use your interview to make the candidate a better software engineer!
  - Allocating more time for them to ask questions about the company - Try to get them excited! If you do this properly, they'll want to interview with your company again at a later time. People change - They may come back in a few years and be an absolutely incredible engineer you 100% want to hire.

Related resources:
- [Full session on being an amazing interviewer](https://link.jointaro.com/NhjenQ5vERKwRPdb9) - This is where this clip was cut out from.
- [Full 1 hour+ Masterclass On Acing Your Big Tech DSA Interview](https://link.jointaro.com/VfSeuUFiXNtKa5if7)
- [Full 1.3 hour Masterclass On Acing Your Big Tech System Design Interview](https://link.jointaro.com/Tmqs62Lw7WV4qDw59)
- [How Alex Got Into Meta With 0 Prior Leetcode Experience](https://link.jointaro.com/vaNH1hjRUhmF8ibSA)

Why Big Tech Compensation Is So High - RSUs

This video explains how **Restricted Stock Units (RSUs)** work as a major part of tech compensation, especially in large tech companies. It outlines key timing mechanisms, industry trends, and the outsized impact RSUs can have on total earnings.

- **RSUs are company shares granted over time**, typically as part of a four-year compensation package. For example, an employee may be awarded 4,000 shares and receive 1,000 per year.
- **Most companies enforce a one-year cliff**, meaning no shares are received until completing the first full year. However, some companies like Google and Facebook have moved toward shorter cliffs, such as three months.
- **After the cliff, vesting usually occurs quarterly or monthly**, gradually releasing shares to the employee. This incentivizes ongoing retention.
- **Graphics help illustrate vesting schedules**, showing an initial cliff followed by incremental monthly or quarterly share distributions over the remaining years.
- **RSUs can far exceed base salary in total value**, especially at the senior level. In some cases, RSUs make up 75% or more of an individual's total compensation in big tech.

A Huge Way Companies Reward You For Joining - Signing Bonus

This video explains the role of signing bonuses in tech compensation, particularly how they’re used by companies to stay competitive and how candidates should evaluate them carefully when reviewing offers.

- **Signing bonuses are one-time cash payments** intended to sweeten a job offer and help a company stand out among competing opportunities.
- **Unlike base salary and equity, signing bonuses are not banded**, meaning they can be more flexible and generous—sometimes reaching up to $175K–$200K for top-tier roles at big tech firms.
- **Because signing bonuses are tied to retention**, they’re typically prorated over time. If the full amount is paid upfront and the employee leaves early, a portion must usually be repaid.
- **Most signing bonuses are structured around a one-year commitment**, but some companies now split them over two years, spreading risk and encouraging longer retention.
- **It's important to read the fine print**, especially around repayment terms and payout schedules, since these details can affect real take-home compensation and decision-making.

Making Every Single Meeting You Have Effective

What do you absolutely need to do with every single meeting in order to make it effective?

What is the most important question you should be asking yourself constantly during a meeting?

Setting clear goals for every meeting ensures focus, alignment, and efficiency. Rather than drifting through discussions, this mindset helps make the most of everyone's time.

- **Define the meeting goal upfront**: Whether the goal is to build a relationship, align on a decision, or explore a specific topic, clarify it before stepping into the meeting.
- **Hold the goal in mind throughout**: Actively track whether the conversation is moving toward the intended objective—even as you engage in real-time dialogue.
- **Course-correct if needed**: If the meeting strays off-topic or stalls, use the goal as a guidepost to refocus the discussion or adjust expectations.
- **Reflect afterwards**: Evaluate whether the meeting achieved its intended outcome. If not, determine what adjustments can improve the effectiveness of future meetings.
- **Build the habit**: With consistent practice, goal-oriented thinking during meetings becomes second nature, enhancing both productivity and influence.

What Is An Engineering Manager?

In this lesson, we explore what an Engineering Manager (EM) is, what they do, and how understanding their incentives helps us collaborate more effectively.

- We learn that an EM is a leadership role supporting engineers, typically managing 8–12 reports, though team sizes can vary widely.
- We understand that the EM’s primary goal is ensuring the team consistently delivers meaningful impact.
- We recognize that knowing an EM’s core incentives helps us work with them more effectively and collaborate better overall.
- We review the two major career tracks in tech: the IC (individual contributor) track and the M (management) track, which begins with the EM role.
- We note that the EM is the first layer of management, with roles like Director, VP, and CTO above them, and that most of us will report to an EM unless we reach very senior IC levels (e.g., L8/L9).

The Five Pillars of Business

In this first module, we explore the essence of individual contributor roles through the lens of core business functions. This sets the stage for understanding how management fits into the bigger picture.

- We break down IC roles across the **five pillars of business** (from Josh Kaufman): value creation, marketing, sales, value delivery, and finance—clarifying how each function contributes.
- The **essence of software engineering** is to create value by building software that solves problems for customers.
- Marketing professionals focus on **raising awareness** of that value, while salespeople focus on **exchanging value**, usually closing deals.
- Roles in value delivery, like customer support or DevOps, ensure that users receive and benefit from the value created.
- Finance professionals ensure **business sustainability**, tracking what’s working financially and what isn’t.
- This clarity of purpose—knowing what success looks like—is often **missing in management**, which leads us to part two: defining the true essence of a manager’s role.

If you want to learn more from Gilad, he shares free leadership advice daily on [LinkedIn](https://www.linkedin.com/in/giladnaor/?utm_source=taro&utm_medium=course&utm_campaign=cta) and weekly on the[ δeltas newsletter](https://posts.managementdeltas.com/?utm_source=taro&utm_medium=course&utm_campaign=cta)

Maximize Your Equity And Benefits In Tech [Part 2] - The Big Picture

Equity compensation can be a powerful but complex part of your total rewards in tech. Here are the core points from the lesson:

- Startup equity is high risk, with data showing over 60% of startups from 2018 have already shut down, and only a tiny fraction have reached IPO or unicorn status
- Multiple cognitive biases—like endowment effect, loss aversion, and optimism bias—can cloud judgment and lead to poor decisions about holding or selling stock
- Emotional and social factors, such as FOMO, herding behavior, and recency bias, often push people to mirror peers rather than make rational equity decisions
- Selling strategies can range from immediate liquidation to goal-based triggers (e.g., home down payment), percentage-based sales, or predefined holding periods
- It's crucial to plan ahead, especially around liquidity events, and work with financial professionals to optimize tax implications and align decisions with personal goals

Next steps with Andy:

- [Connect with Andy on LinkedIn](https://www.linkedin.com/in/andymoranio)
- [Leave feedback and/or sign up for Andy’s newsletter](https://subscribepage.io/taroequitycourse)
- [Schedule a consultation](http://adastrafp.com/contact-us/)

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.