Negotiation Course: Don’t Overshare (Level, Passion, Timeline)

Understanding your emotional attachment to the offer is even more important than the data. Ideally, you want low emotional attachment and high data (as explained in [this Taro blog post](https://www.jointaro.com/blog/the-5-lies-that-too-many-people-believe-about-negotiating-a-job-offer/) by Rora).

For example, don't reveal that you're only talking to a single company, or that you're talking to 30 (either extreme can hurt you). Sample dialog: 

> If anything changes on my end, I’ll let you know, but for now I’m eager to learn more about your company

(There's a whole section dedicated to helpful phrases later on.)

You can share information with the recruiter, but be mindful of what and when you share. How much PTO or signing bonus you want are topics that should come up before (if it's a blocker) and after the interview, not during.

**If in doubt, don’t share it**. Just be positive and non-committal to pretty much everything the recruiter says. Answer questions with vague responses and be confident.

Grow From Junior To Mid-Level Engineer [Part 11] - Ask Great Questions

In order to grow fast as an engineer, you need to ask a lot of questions. This lesson teaches you:

- The differences between junior and mid-level engineers when it comes to asking question, particularly question quality
- What a junior engineer question looks like vs. a mid-level engineer question
- How to demonstrate technical mastery in your questions to make yourself look even better when asking for help

Master the art of question asking with our course: [Ask Great Questions That Get Great Answers Quickly](https://www.jointaro.com/course/ask-great-questions-that-get-great-answers-quickly/)

Don't Waste Your 1 on 1s. Build The Relationship

Why should you build the relationship in 1 on 1 meetings?

True or false: Small talk is okay in 1 on 1 meetings to break the ice and learn more about the other person's life outside of work.

Why are deep relationships needed in tech, especially at senior levels?

[Become A Go-To Person 9/18] The Formula For Expertise

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

Master The DSA Interview [Part 28] - Don't Forget: Other Interview Types Exist

Data structures and algorithms are a core part of the software engineering interview loop, but it's important to remember that there are other critical interview types as well, including for FAANG. This lesson teaches you:

- How many engineers who completely fail their Big Tech interview actually did well on the data structures and algorithms portion, wasting all of their LeetCode grind
- How the amount of time you spend on data structures and algorithms preparation will vary based on the types of interviews you have
- How the amount of time you spend on data structures and algorithms preparation will vary based on your level
- General attributes to use to calculate the amount of time you need to allocate to data structures and algorithms

Please ask your recruiter what's going to be on your interviews. Don't be afraid to be a bit aggressive and don't be shy. Follow the advice here: <https://www.jointaro.com/course/ace-your-tech-interview-and-get-a-job-as-a-software-engineer/talk-to-your-recruiter/>

Master the behavioral interview with this course: [Master The Behavioral Interview As A Software Engineer](https://www.jointaro.com/course/master-the-behavioral-interview-as-a-software-engineer/)

Master the system design interview with this course: [The Top Ways People Fail System Design Interviews](https://www.jointaro.com/course/the-top-ways-people-fail-system-design-interviews/)

Ask Me Anything (AMA) with a Meta and Databricks Eng Director - Ritendra Datta

[**Ritendra Datta**](https://www.linkedin.com/in/ritendradatta/) is a Senior Director of Engineering at Databricks.

Previously, he was the Head of FB Reels and Video Recommendations (Director of Engineering) at Meta, where he worked from 2019 - 2023. Prior to that, he was a Senior Staff Software Engineer and Tech Lead working at Google in Mountain View. See the [Q&A Ritendra led in the discussion forum](https://www.jointaro.com/question/FaRXsBFD3JpNtFlsmC6Q/im-ritendra-ex-metagoogle-current-senior-director-at-databricks-ama/).

In this Ask Me Anything (AMA), Ritendra answered many questions about tech leadership and career growth!

**Career Preferences in Small vs Large Companies**

Ritendra explained that he enjoys working in smaller, more self-contained companies where he can have a greater impact and more direct relationships with colleagues and superiors. He also highlighted his discomfort in large companies where there are more people than problems and where he would rather focus on technical work than fighting for scope. He ended by stating that his 'sweet spot' is in smaller companies like Databricks or the early days of Google.

**Manager Evaluation and Influence Strategies**

Ritendra discussed how to evaluate a manager and increase influence in a new company. Rahul asked for advice on evaluating a manager, and Ritendra emphasized the importance of empathy, understanding, and a focus on the employee's growth. He suggested asking existing reports about their manager's responses to failure and success, and their approach to career growth. Later, Rahul asked about increasing influence in a new company, and Ritendra advised understanding the company's pain points and focusing on solving them. He cautioned against bringing in new problems to solve, as it can be dismissed due to the existing workload. He also mentioned that introducing a new perspective can also lead to influence.

**Director's Tech Role: Problems and Strategies**

Ritendra discussed the common people problems faced by a director in a technology leading role. Ritendra highlighted the issue of conflict within an overgrown organization, where there are too many people and not enough problems, leading to fights over scope and misaligned career aspirations. He also shared his personal strategy of moving to a different part of the company where the problem is less prevalent. Rahul asked about identifying fast-growing opportunities within a company, to which Ritendra suggested evaluating visibility and impact potential. He advised focusing on areas that are important to the business outcomes but not heavily crowded, and not always following the CEO's narrative.

**Executive Presence: Leading Beyond Teams**

Ritendra shared his personal experience of receiving feedback about his lack of executive presence early in his career and his subsequent efforts to develop it. They also emphasized the importance of understanding and executing on leaders' strategies, as well as effective communication with senior leadership. The conversation touched on the importance of taking action items and follow-ups, and maintaining a balance between being assertive and respectful in discussions with senior leaders. They concluded that executive presence is not solely about intelligence or technical expertise, but also about understanding and acting on strategic directions.

**Relationship-Building and Communication Strategies**

Jordan queried how to optimize the value of one-on-one meetings, to which Ritendra expressed his preference for these meetings due to their potential for honest communication and vulnerability. He shared his personal experience of joining a new company to highlight the significance of openness in establishing deep connections with others. Ritendra cautioned against frequent complaining, recommending a balance of 70% positive communication and 30% expressing struggles.

**Managing Difficult Relationships and Career Advice**

If you have a difficult manager relationship, Ritendra suggested that one should make a judgment call on whether the manager has already given up on them and advised seeking an exit if the relationship can't be repaired. He also mentioned that negative performance reviews often lead to further negative reviews, making it less likely for a turnaround. The topic of how much senior leadership knows about struggling mid or senior-level engineers was also discussed, with Ritendra confirming that such information does spread up the reporting chain. Lastly, Rahul asked about Ritendra's relationship with money as he climbed the career ladder. Ritendra stated that beyond a certain compensation, money doesn't significantly change one's quality of life and that he values his daily happiness over a higher salary.

**AI and ML Advice From Experienced Engineer**

Ritendra advises to focus on the areas surrounding the problem at hand, follow industry experts, read Linkedin articles, and listen to podcasts for new ideas. He emphasized that companies typically focus on fundamental knowledge rather than specific details about recent developments. Ritendra also suggested the use of co-pilot tools, such as AI assisted code writing, to make lives easier and recommended learning about the psychology of engineering and technology.

Relevant links:

- See the [Q&A Ritendra led in the discussion forum](https://www.jointaro.com/question/FaRXsBFD3JpNtFlsmC6Q/im-ritendra-ex-metagoogle-current-senior-director-at-databricks-ama/).
- Check out [**Ritendra's Substack here**](https://tldr0.substack.com/) and [**Medium here**](https://tldr0.medium.com/). (He wrote about his prior [**AMA from Blind**](https://tldr0.substack.com/p/a-fascinating-q-and-a-with-meta-employees) here.)
- Check out discussions with another [**Senior Eng Leader, David Pan, here**](https://www.jointaro.com/topic/david-pan/) and [**Rachel Zhao, here**](https://www.jointaro.com/topic/rachel-zhao/).

[Timeless Career Advice] Junior to Senior Engineer (And Beyond)

Congratulations, you made it to the end of the course, **Timeless Career Advice for Software Engineers**!

Bonus documents available to you: 

- [Timeless Advice for SWE Careers \[Cheat Sheet\]](https://drive.google.com/file/d/1gzvPMib9IM1yRdz7qiTIKtcEZFIF0GyQ/view?usp=drive_link)
- [Promotion Guide \[Cheat Sheet\]](https://drive.google.com/file/d/1d8tq9EEL7ZeXKMMf4SFC9zjrOZT7-0nc/view?usp=drive_link)
- [Louie's Income Progression in Tech](https://drive.google.com/file/d/1OKtp67v8V0k52GXnQ9yYsn2n-0zb7dIQ/view?usp=drive_link)

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

Feel free to share any feedback on this course with us at [**team@jointaro.com**](mailto:team@jointaro.com).

Share + get support on the Taro forum: [**joinTaro.com/questions/create/**](http://joinTaro.com/questions/create/)

Lessons From The Top: Managing And Growing 800 People (Ethan Evans)

[**Ethan Evans**](https://www.linkedin.com/in/ethanevansvp/) is a retired Amazon VP who now teaches managers how to break into executive levels. He was at Amazon for 15 years, and he became a VP in 2013 until he left in 2020. This wide-ranging interview covers many topics:

- Ethan's career trajectory, and how he entered the management path startlingly early.
- How do you know if an IC will be a good manager or not?
- What are the common reasons why managers fail to get promoted?
- Why do re-orgs happen, and why is there so much corporate speak?
- What should you look for in a leader?
- How are the senior-most engineers evaluated?
- Why did Ethan leave Amazon to become a full-time teacher?

Ethan shares valuable insights for anyone interested in management or career development.

**Key insights:**

- **Why did Ethan choose management so early?** He was drawn to it because that was the need from his team and his managers supported his decision.
- **What skills helped Ethan ascend quickly in startups?** High-growth environments provided opportunities, but Ethan capitalized on them by actively seeking problems to solve and proposing solutions. He took initiative and wasn't afraid to ask for more responsibility.
- **What advice does Ethan have for others?** Be proactive, identify problems, and offer solutions. Don't be afraid to step up and make the ask to your leadership team. "*Do good work and hope*" is not an effective strategy.
- **Careers are long**. Ethan was a "fake" startup VP before going getting downleveled as a manager at Amazon, and it took years for him to return to a true VP role, managing a team of 800 people.

**Helpful links:**

- [\[Masterclass\] How To Work Better With Your Engineering Manager](https://www.jointaro.com/lesson/2PbJb2fuqF3iMHy57eEg/masterclass-how-to-work-better-with-your-engineering-manager/)
- [Overcome Career Stagnation (5 Common Scenarios)](https://www.jointaro.com/lesson/UvGdGyBfHn4oNCfE77KV/overcome-career-stagnation-5-common-scenarios/)
- [Asking 7 Levels Of Engineers The Most Important Skill](https://www.jointaro.com/playlist/J9Io5lDGaYUpI8vGrUyI/)
- [**How do I figure out whether I should stay as an IC engineer or explore management as an EM?**](https://www.jointaro.com/question/Y6qIop9wpOlCYUL0nGs0/how-do-i-figure-out-whether-i-should-stay-as-an-ic-engineer-or-explore-management-as-an-em/)
- [**\[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/)

Negotiation Course: Negotiating Your Current Salary

Negotiating your current comp is harder. You can no longer sell on potential, you have to show the outcome of what you have achieved. There are generally also fewer levers to adjust, usually just salary and equity refresh grants.

A few tips: 

- Time when you ask to coincide when your company normally does pay evaluations and merit increases
- Share market data or another offer

If you ask for money and reference another job, be careful about the impact it may have on your manager relationship, who may give you less scope or responsibility.

Grow From Senior To Staff Engineer [Part 12] - Become The PM Right Hand

As a staff engineer, you need to have far more influence on the direction of the product, especially if you work on a product-facing team. This lesson teaches you:

- The difference in the depth of collaboration with the product manager between a senior engineer and a staff engineer
- Why staff engineers often need to partner closely with their product manager
- Which teams place more value on the engineer &lt;-&gt; product manager relationship
- What you should do to deepen your relationship between you and your product manager

Become An Open Source Master [Part 9] - Solve A Need

When choosing an open-source project to contribute to, we should:

- **Focus on solving a need:** Choose a project that you'll benefit from and have a passion for working on.
- **Assess the project's health:** Look for signs of active maintenance, such as merged pull requests and recent activity.
- **Seek insights from others:** Talk to people who have worked on the project to get their perspectives on the community and development process.

Connect with James: 

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

Grow From Junior To Mid-Level Engineer [Part 13] - Be A Feedback Sponge

We all have blind spots, and you need feedback to see them. Getting feedback is especially important as an engineer given how information-dense the software field is. This lesson teaches you:

- Why a surprising amount of junior engineers are terrible with feedback
- Why you should almost never push back against feedback you disagree with
- How not being good with feedback can severely damage your career, explained with an in-depth example
- The differences between junior and mid-level engineers when it comes to handling feedback

For additional inspiration on truly becoming a feedback sponge, check out the words of wisdom from OpenAI ChatGPT engineer [Philip Su](https://www.linkedin.com/in/suphilip/) here: ["What's the core insight behind quick growth?"](https://www.jointaro.com/question/nJ762p255cGyuth36H6w/whats-the-core-insight-behind-quick-growth/)

DSA Crash Course [Part 46] - Tree Includes Walkthrough

In this lesson, Alvin walks through the python implementation for the *tree_includes* problem.

Code along and test your work in the following editor workspace: <https://structy.net/problems/tree-includes?language=py>

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

[Masterclass] How To Be An Amazing Interviewer In Tech

For all the core points, you can find them in the slides below. For this video summary, we're going to share our Top 5 insights from the session:
- The tension of being a great interviewer is that you need to balance getting signal of the candidate's ability while maximizing candidate experience.
  - Can you make it so that the candidate had a good time even if they failed?
- Getting signal happens when the candidate has to figure out a challenge. *This means that you need to be very careful giving hints*. If you give too many hints, you are solving the problem for them.
- **Never ever end an interview early due to poor candidate performance, especially an onsite round**. Turn the interview into a fun pair programming exercise where you build cool stuff and help them become a better engineer.
- If you're the candidate, communicate as much as possible and don't fish for hints. This gives the interviewer more opportunities to help you out. Doing the opposite can doom your chances.
- At the end of the day, the interview process is made up of people on both sides, interviewee and interviewer. Let's all make the world a little better by striving to be good interviewers!

Related resources:
-  [Presentation slides](https://docs.google.com/presentation/d/1oBNstU-3TJlPGc8Rc5K7AfUUdr7OUo1ADT3JPa4ecSk/edit?usp=sharing)
- [In-depth session on acing your DSA interview](https://link.jointaro.com/cponWycMZZfkRNBW8)
- [In-depth session on acing your system design interview](https://link.jointaro.com/FWp3fithS4xzp3dx7)

Master The DSA Interview [Part 25] - Do Mocks

Many engineers actually know all of the data structures and algorithms concepts, but they aren't able to bring that out during the live interview when it actually matters. Luckily, there's a solution for that. This lesson teaches you:

- Why there's a fundamental dynamic shift between studying data structures and algorithms and actually solving the problems in a live interview
- The many concrete differences between data structures and algorithms in study mode vs. live interview mode
- General tips on how to both give and receive a good mock interview
- What a quality data structures and algorithms interview scorecard looks like so you can create good ones when you give a mock interview

Find mock interview partners here: <https://www.jointaro.com/networking/?selectedServices=Mock+Interviews>

Grow From Senior To Staff Engineer [Part 10] - Oncall

"Oncall" is a term that strikes fear into the heart of engineers. However, it's crucial for engineers to embrace oncall as an honorable duty and a place of opportunity as they become more senior, especially as they progress to staff. This lesson teaches you:

- The differences between senior and staff engineers when it comes to their scope within oncall
- How senior and staff engineers respond differently to oncall issues

Watch Alex's oncall case study here: [\[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/)

How to Negotiate a Big Tech Offer as a Software Engineer - Pragmatic Engineer and Rahul

How does a compensation package look like for a software engineer at tech companies? How do base salary, annual bonus, equity (options, RSUs), sign-on bonuses and perks usually add up? What parts of the package can you negotiate? How can you line up multiple offers at the same time? We talk about these and more in the video. You can -- and should! -- negotiate any offer you receive from a Big Tech company. 

There are 4 primary parts to compensation in Big Tech: 
- Base salary
- Annual bonus
- Sign-on bonus
- Equity

Perks could also be considered part of the compensation package, but these are generally standardized across all employees for a company, so they're not considered for the purposes of negotiation. (Think of things like 401(k) match, free food, game rooms, etc.)

It's important to understand the different parts of compensation because you can start to shift the conversation with companies to be more cooperative rather than zero-sum. For example, some companies have strict bands for their base salary, but are more willing to negotiate on their equity. Knowing this, along with your own utility for different types of comp, can lead to a final decision where both sides are happy.

Throughout any negotiation, it's important to be respectful in your communication, and also consider factors beyond financial compensation, such as team dynamics and the hiring manager's perception. Don't rush into signing a contract without careful consideration -- negotiate terms over email to allow for proper reflection.

More resources on negotiations:
- [The #1 Rule Of Negotiation - How To Avoid Giving A Number](https://www.jointaro.com/lesson/4T3wTorG47wPzSqVmAOx/the-1-rule-of-negotiation-how-to-avoid-giving-a-number/)
- [[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/)
- [3 Quick, Powerful Negotiation Tips](https://www.jointaro.com/lesson/8VeEnbxdbPKsZbTcCFm5/3-quick-powerful-negotiation-tips/)


This is a video from [Gergely's YouTube channel](https://www.youtube.com/@mrgergelyorosz). 
- Original source: [https://youtu.be/cbngWLr7BC4](https://youtu.be/cbngWLr7BC4)
- Gergely writes the popular [Pragmatic Engineer newsletter](https://www.pragmaticengineer.com/).
- [Follow Gergely on Twitter](https://twitter.com/GergelyOrosz)

Get The Rating You Deserve [Part 7] - Build Relationships Proactively

**In this section, we'll explore the importance of building and nurturing relationships in your career.**

- **Proactive Relationship Building:** We emphasize the importance of building relationships before you need them, focusing on giving value and aligning goals.
- **Mindful Communication:** We discuss the power of effective communication, including active listening, empathy, and clear expression of needs and desires.
- **Leveraging Power for Good:** We explore how to use power to create positive change and foster strong relationships, rather than for personal gain.
- **Overcoming Pitfalls:** We identify common pitfalls in relationship building, such as impatience and a short-term focus, and provide strategies to avoid them.
- **Practical Tips:** We offer actionable advice, such as dedicating time to relationship building, seeking out opportunities to help others, and practicing empathy and understanding.

If you want to get personalized support from Yogi, you can reach out to him at [coaching@yogisharma.com](mailto:coaching@yogisharma.com) or schedule an introductory call to dive into your situation at <https://tinyurl.com/meetyogi>.

Engineer Your Ideal Tech Career [Part 14] - Defining Near-Term Goals

Moving into your last section and with inspiration from the engineers you just heard from, you can expect to start defining near-term goals that you can implement within the next week, month, or quarter, to start charging towards your ideal long-term career.

This section will include tangible advice you can implement on the job or if you are preparing for interviews.

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)

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

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.