If you’re up for a product manager interview at a big tech company like Google, Meta, Apple, Anthropic, or OpenAI, expect product metrics questions as part of your interview loop.

Product metrics questions ask you to define a metric or find the root cause of a change in metrics. Interviewers expect you to know how to identify the right metrics to track, measure, and analyze to assess a product’s success.

These questions aren't easy. But the good news is that if you know how to approach them, they can become fairly straightforward to answer. 

Below, we'll give you everything you need to prepare for metric questions: an answer framework, expert tips, example answers, and questions to practice with.

Here’s an overview of what we will cover:

Click here to practice 1-on-1 with FAANG ex-interviewers

1. What is a product metrics interview question? ↑

Product metric interview questions test your ability to perform data analysis and select key metrics that matter most to the success of a product. You’ll encounter this type of question at an analytical thinking / product analysis round at a big tech company like Meta or Google. They can sometimes occur as follow-up questions to product sense interviews as well.

IMAGE: What is a product metrics interview question?

There are two types of metric questions: metric definition questions and metric change questions.

Metric definition questions focus on your ability to define metrics that provide clarity on the health of a product or feature (e.g., impressions, clicks, return on ad spend, etc.). For example: “What metrics would you use to determine success for Facebook Sponsored Posts?” 

Metric change questions test if you know what to do when a key product metric (e.g., traffic, revenue, engagement, etc.) is going up or down for no apparent reason. For example, “Facebook’s Feed engagement is down 10%. How would you report this issue to your superior?” 

There are many different reasons why this decrease could be happening, and your interviewer will want to see you take a bulletproof approach to find the root cause of the issue.

If you're applying for an AI-focused PM role, it's likely you'll get a metrics question about an AI product. When answering, it's important to note that AI products require additional metrics on top of what you'd usually measure in a standard product. You need to distinguish between technical metrics and product metrics and build in countermetrics or guardrails for responsible AI usage. More on AI product metrics here.

Either way, your interviewer will want to hear you select the most important metrics using a rigorous process. 

Coaches who contributed to this guide

Profile picture for Dessy K.
Dessy K.
Product manager
Management consultant
Manager of PMs
+ 3 other
+ 3 others
United States, Singapore
5.0 (14 reviews)
58 clients (18% rebook rate)
Profile picture for Gal E.
Gal E.
SuperCoach
Product manager
Founder / Entrepreneur
+ 1 other
Israel
5.0 (26 reviews)
108 clients (37% rebook rate)
Top 10% by job offer rate
Profile picture for Suvagata R.
Suvagata R.
SuperCoach
Product manager
Manager of PMs
Program manager
+ 1 other
Europe
5.0 (74 reviews)
190 clients (38% rebook rate)
Top 5% by job offer rate
Profile picture for Khalid A.
Khalid A.
Product manager
Manager of PMs
+ 2 others
North America
5.0 (9 reviews)
24 clients (16% rebook rate)
Browse more expert PM interviewers

2. How to answer metrics interview questions (frameworks)↑

When answering product metrics questions, it’s important to demonstrate that you take a structured approach to decision-making. The best way to do so is to use a framework to communicate your answer.

In this section, we’ll walk you through two frameworks that you can use in your interview:

2.1 Metric definition questions: GAME method

Metric definition question example

“What metrics would you use to determine success for Facebook Feed?”

We recommend using the GAME method to answer metric definition questions. Let’s walk through each of the four steps one by one:

  1. Goals
  2. Actions
  3. Metrics
  4. Evaluations

1. Goals: First, you should start by making sure you understand the product properly and agree with your interviewer on specific user and business objectives. 

Agreeing on the goals upfront is extremely important because what you measure will change entirely depending on what you’re trying to achieve with the product.

For instance, imagine your interviewer has asked you, “What metrics would you use to measure the success of Meta’s Facebook Feed?” The Feed is one of Facebook’s main features and it fulfills many objectives for the business. 

It’s a primary driver of user engagement, a strong revenue generator, and the main place where Facebook can test new personalization features. So, how do you determine what the most important objective is?

There’s no single right answer to this question but you could begin by saying, "My understanding is that there are several use cases for the Feed including engaging users, generating ad revenue, and testing new personalization features. To stay healthy, Facebook needs strong user engagement, so I would assume that this is the primary business goal. Is that what you have in mind, too?"

2. Actions: Next, you should think about all the actions users can take in the product. Listing each action will help you focus on available metrics and avoid those that aren’t trackable.

The easiest way to do this is to think about what it really means for a user to be “engaged.” You should aim to list every relevant action (e.g. creating a post, viewing a post, commenting, liking, sharing, etc.). 

However, it’s also a good idea to avoid going into too much detail. For example, simply list “liking” as a category of action instead of “liking a friend’s post, liking a group’s post, liking an event, liking a comment, etc.”

Next, you need to prioritize your list of actions. Remember to use the goals you established in the previous step to explain your thinking. 

For instance, you might say something like, “There are a number of user actions which reflect engagement but I think the three most important ones are likely to be posting, commenting, and sharing.”

3. Metrics: Once you have a prioritized list of actions, it’s time to define associated metrics for each one. In this step it’s important that you define the metrics you will measure with precision.

Let’s imagine that in our previous step, after discussing with your interviewer, you prioritized the “comment” and “share” actions. Talking about “comments” and “shares” isn’t sufficient as there are many different ways in which you can track these actions.

In order to measure engagement based on these actions, here are some metrics that would make sense to track:

  • "Comment" metrics
    • Comments per thousand sessions
    • Comments per thousand posts seen
    • Comments per thousand posts clicked
  • "Share" metrics
    • Shares per thousand sessions
    • Shares per thousand posts seen
    • Shares per thousand posts clicked

4. Evaluations: After defining metrics, you should conclude the discussion by answering the initial question with the metrics you recommend. Finally, evaluate the metrics you have selected by highlighting trade-offs and limitations.

For the Facebook Feed example, you could summarize by saying something like, “So, in order to increase Feed engagement, I would first look at comments and shares per thousand sessions. These metrics would give us an idea of meaningful engagement for the average user.”

The last key step is to show that you understand the strengths and weaknesses of your recommended metrics.

So you could wrap up your answer by saying something like:

“We should keep in mind that not all commenting and sharing is positive. Perhaps we should monitor the sentiment of these actions to make sure we're creating a positive experience overall. Also, commenting and sharing represent deep engagement. If we are interested in shallower engagement we might need to consider other metrics (e.g. number of sessions per user per day, number of likes per user, etc.) to measure engagement for users who don't comment or share but still use the product frequently.”

2.2 Metric change questions: DEC method

Metric change question example

“Facebook Feed engagement is down 10%. How would you report this issue to your superior?”

We developed the DEC method below to help you give a clear and thorough answer to metric change questions. Let’s walk through each of the three steps one by one:

  1. Define the metric change.
  2. Explore possible root causes of the change.
  3. Conclude.

1. Define the metric change: Many candidates skip this step and start listing ideas in an unstructured way. This is a big red flag for interviewers. Before starting to answer the question you need to define the metric change in detail. This often entails asking for three pieces of information:

  • The exact definition of the metric we’re talking about
  • The time period over which the metric has changed
  • The characteristics of the user segment impacted by the change (e.g. device type, country, etc.)

Let’s imagine your interviewer asks, “Facebook Feed engagement is down 10%. How would you report this issue to leadership?” 

To clarify your understanding, you might then ask something like, “What exactly do we mean by engagement here? Is that a direct measurement like the number of sessions, or a combination of more detailed metrics (e.g. likes + comments + shares per user, etc.)? And over what time period has that change occurred? Finally, do we know if all users are impacted or only a particular segment?”

Here let’s imagine your interviewer tells you that the number of Feed sessions for all users has gone down 10% since yesterday. 

Only after you’ve clarified this information should you start exploring possible root causes.

2. Explore possible root causes: Interviewers want to see that you’re thinking of every possible problem that could cause the metric change you are investigating. 

To ensure you’re thinking comprehensively and communicating clearly, you should:

  • Create a MECE framework for possible root causes.
  • Brainstorm potential root causes of the problem within this framework.
  • Discuss the different root causes identified with the interviewer.

For our drop in engagement example, you could split your investigation between internal and external factors:

  • Internal factors: possible problems internal to Facebook that can explain the drop in sessions
  • External factors: possible problems external to Facebook that can explain the drop in sessions

Note that the framework above is MECE or Mutually Exclusive and Collectively Exhaustive. The root cause of the problem has to be internal OR external, as there is no other option.

Once you’ve created your framework you need to brainstorm ideas and possible causes within each of the areas you identified. For example here you could populate your framework with the following points:

  • Internal factors:
    • Data accuracy (e.g. This metric change was measured incorrectly)
    • We broke the product (e.g. Someone in the organization made a change that broke the Newsfeed)
    • We made the product worse (e.g. The quality of content in the Feed has degraded)
    • Other internal factors
  • External factors:
    • User habits (e.g. User changed habits overnight for some reason, like a protest)
    • Referrers (e.g. Google had an outage)
    • Competition (e.g. TikTok released a new feature that captured a portion of our normal Feed traffic)
    • Other external factors

The interviewer will most likely ask you to talk about some of your proposed root causes, which is perfectly normal. Listen carefully to what they say, as they will often provide clues that will point you in the right direction.

3. Conclude: Finally, you should conclude by summarizing your findings related to the initial question you were asked.

Let’s imagine that you discovered Facebook suffered an outage which caused the drop in sessions.

In this case, you might summarize by saying something like, “Based on what we’ve talked about, I would explain to leadership that Feed sessions dropped 10% since yesterday because of a major outage this morning. I would also make it clear that we came to this conclusion by ensuring it could not be any other cause, and double-checked that the duration of the outage aligns with the 10% drop.”

Now that you've seen our recommended answer frameworks, let's look at a written example answer, plus two more by experts.

2.3 Example metrics question with answer ↑

Let's now look at a written answer to a common metrics question:

Example question:

YouTube traffic went down 5% — how would you report this issue to the executive team?

Let's use the IGotAnOffer DEC method described above.

Step one: Define the metric change

First, we want to completely understand the question and define the metric, as “traffic” is a bit vague. 

Here are some questions that immediately come to mind and will help confirm our understanding:

  • What exactly do we mean by traffic here? Website visits, plays on videos, or time spent watching? etc.
  • Is this impacting all user segments? Or maybe only a particular device type, country, or browser? etc.
  • When did the dip start and how long did it last?

For the rest of this example let’s imagine the interviewer tells us that the average time spent watching per session is down 5% month-over-month worldwide on mobile only.

Step two: Explore possible root causes

Now that we know the exact problem we can create a framework to identify the root-cause of the time spent watching per session decrease:

  • Internal factors: possible problems internal to YouTube that can explain the drop in average time spent watching per session
  • External factors: possible problems external to YouTube that can explain the drop in average time spent watching per session

Within this Internal / External framework, let’s brainstorm different root causes that could drive down the average time spent watching per session:

  • Internal factors:
    • Data accuracy (e.g. We should confirm our reporting tool is working as expected)
    • Context (e.g. This could be an expected seasonal drop)
    • Access to the product (e.g. We might have had a major outage)
    • Product changes (e.g. We could have shipped some code that introduced a bug)
    • Product quality (e.g. Recent content might have been bad enough to drive away traffic)
  • External factors:
    • User habits (e.g. Video consumption is down across the industry)
    • Referrers (e.g. Facebook made a change to limit linking to YouTube videos)
    • Competition (e.g. Instagram TV released a new feature that captured our users)
    • Society (e.g. There are fewer active users because of civil unrest in a country that typically drives a lot of traffic)

We can also dive deeper into some of the root causes. Here’s an example of how the conversation could go.

  • Data accuracy: Have we checked this dip compared to a similar metric — for example, time on page? Is there anything else indicating that our reporting tool might be broken?

Let’s imagine the interviewer confirms that we’re seeing a similar dip with time on page that leads us to believe the data is accurate. They also confirm that we’ve double-checked that our reporting is working as expected.

  • Context: Is there any history of a similar dip? We’re close to major holidays, perhaps that could lead to less product usage overall.

The interviewer lets us know the only time we’ve seen a drop of more than 1% this time of year was due to major outages, but we have had 100% uptime in the past few months. This information also addresses our next factor, as access to the product hasn’t been disrupted.

  • Product changes: Is it possible we shipped some code that introduced a bug? Or, did we release any significant feature changes?

Let’s imagine the interviewer says that the user interface for the video player was recently changed on mobile. We would then ask questions to explore this such as, “What exactly was changed in the UI and was any drop to be expected as a result?”

After discussing with the interviewer, we learn that the UI change involved making the “Send video to device” button two times larger, and reducing the “Full screen” button by half its original size. The interviewer also explains that the “Send video to device” button can be used to play a video that’s on your mobile phone on another device such as a Chromecast, Roku, SmartTV, etc.

This is interesting, but we need to investigate further. At this point, we could form a hypothesis and say something like, “Have we noticed a change in the frequency at which the ‘Send video to device’ and ‘Full screen’ buttons are being used on mobile? Maybe mobile users are having a harder time tapping the ‘Full screen’ button now that it’s smaller, and are tapping the ‘Send video to device’ button by accident because it’s too big? Tapping ‘Send video to device’ would end the session and therefore decrease the average time per session. And if the smaller ‘Full screen’ button is harder to tap, it might frustrate some users and lead them to end their session early.”

Let’s imagine that the interviewer confirms that this is likely one of the drivers of the decrease. Before making any final conclusion, we would continue exploring the remaining elements (i.e. product quality and external factors) to confirm that they aren’t also a driver of the change we are observing. Let’s imagine we quickly discuss this with our interviewer, and they confirm there’s nothing significant to report related to those remaining possible factors.

Step three: Discuss and conclude

Now that we’ve stepped through our framework, we would conclude by saying something like, “Based on what we’ve talked about, I would explain to the executive team that our time spent watching per session has dropped by 5% month-over-month on mobile because of a change in the video player UI, which has negatively affected the user experience. Mobile users are having a hard time tapping the new, smaller ‘Full screen’ button and are ending their session prematurely. They are also now more often tapping the larger ‘Send video to device’ button unintentionally which also ends their session early.”

Finally, we could enrich our answer by saying something such as, “We’ve also double-checked that no other drivers were causing this engagement dip. A good next step here would probably be to revert the UI changes, think through why we made these changes in the first place, and brainstorm how we can achieve the goals we were aiming for in a different way.”

2.4 Sample product metric interview questions with answers by experts↑

Another great way to learn how to use frameworks is by watching experts implement them in a product metrics mock interview. 

Below are two videos with PM coaches Suvagata (ex-Meta PM) and Gal (ex-Google PM), tackling product metrics questions. The first one is for a standard product and the next, for an AI product. Try to answer the prompt yourself, and then watch afterwards to see which areas you need to improve.

“If you were the head of product at Airbnb, what metrics would you look at to determine success over a 2-year horizon?”

 

"What goal would you set for an AI-only social network that OpenAI is building?"

 

Here are a few more expert mock interviews we recommend watching:

  1. Pick YouTube Success Metrics (by IGotAnOffer)
  2. How would you measure engagement for Netflix (by IGotAnOffer)
  3. What metric goal would you set for Airbnb (by Dianna Yau)
  4. How would you measure the success of the Facebook Dating product? (by Product Alliance)

3. Example metrics interview questions (by company) ↑

Here is a list of metric questions that were asked in PM interviews at Meta, Apple, Netflix, Google, Anthropic, and OpenAI, according to data from Glassdoor and other candidate reports online:

Meta product metric questions

Metric definition

  • Define success metrics for Facebook Marketplace. 
  • Imagine you are the PM of the Facebook Feed — how would you measure retention?
  • What metrics would you use to measure the success of Facebook’s “Save Item” feature?
  • How would you determine post ranking in the Facebook Feed?
  • Tell me what metrics you would look at as a product manager for Instagram ads.

Metric change

  • There's been a 15% drop in usage of Facebook Groups — how do you fix it?
  • The usage of Facebook Event’s “Yes I’m going” dropped 30% overnight — which data would you look at to try to isolate the issue?
  • You are the PM of Facebook 3rd Party Login, and you see your numbers are declining 2% week-on-week — what do you do?

Click here to learn more about the entire Meta PM interview process.

Apple product metric questions

Metric definition

  • How would you measure the success of Apple's Worldwide Developers’ Conference (WWDC) event?
  • How would you measure the success of the iPad Pro?

Metric change

  • You’re an Apple product manager for Apple Maps. What will you do to regain market share?

Click here to learn more about the entire Apple PM interview process.

Netflix product metric questions

Metric definition

  • What are the things that Netflix should measure and analyze on a daily basis?
  • Define metrics for Netflix Podcasts.
  • How would you measure the success of the Netflix recommendation engine?
  • What are the key metrics to be captured for a streaming service product?
  • How would you measure engagement for Netflix?

Metric change

  • A metric for a video streaming service dropped by 80%. What do you do?

Click here to learn more about the Netflix PM interview process.

Google product metric questions

Metric definition

  • What is the most important metric for Google Docs, and why? 
  • How would you measure the success of Google Photos?
  • What do you think is the most important metric to track in Google Search, and why?
  • Define the metrics for YouTube Search.
  • How would you measure the success of the new YouTube Player UI?

Metric change

  • You are looking at YouTube’s Daily Active User data worldwide and notice a 10% jump compared to yesterday in Indonesia — what happened?
  • Engagement is going down by 10% month on month for your product. What data /metrics would you look at? 
  • What are 10 important metrics for Spotify under the engagement category? Which one would you improve? Why?

Click here to learn more about the entire Google PM interview process.

Anthropic product metric questions

  • How would you measure success for Claude on a coding task?
  • What KPIs would you track for Claude.ai's monthly active users?
  • How would you define and measure success for a new Claude API feature targeting enterprise developers?
  • How would you know if a Claude feature is actually improving user productivity?

Click here to learn more about the Anthropic PM interview process.

OpenAI product metric questions

  • What topline metric goal would you set for Airbnb?
  • How would you measure success for OpenAI? What if instrumentation went down?

Click here to learn more about the OpenAI PM interview process.

If you'd like to learn about the other types of questions you may face, you can also visit our ultimate guide to product manager interview questions.

4. Interview tips↑

Now that you know more about product metrics interviews and how to answer them, let’s look at some tips from our expert PM coaches on how to best tackle this question type.

4.1 Make sure you understand the prompt

"Always make sure you understand the prompt very clearly," Suvagata (ex-Meta, Amazon PM) says. Ask questions, and verify your assumptions with your interviewer before you start answering the prompt.

This also helps you mentally plan out your answer.

4.2 Start with the user and go holistic

Suvagata says it’s a good practice to start with the users first and why it’s a good problem to solve from their perspective. 

And then once you’ve established why it is indeed a worthy problem to solve for users, then connect that with why it’s also good for the company in terms of its core mission and economically as well.

To map the user journey, Dessy (ex-TikTok Head of Product) recommends using the funnel approach. 

"Imagine a funnel in your mind by following that user journey, and have 1-2 metrics for each user step. This ensures you think through the metrics systematically and not randomly."

4.3 Brainstorm metrics before narrowing down

List down as many possible metrics you can think of based on the business model. Different companies will prioritize different metrics, but you should have a solid grasp of the core activation metrics like adoption, engagement, quality, and retention.

"Show that you understand that there are lots of metrics you can measure, but it's important to figure out what the most important metric is," Suvagata says.

4.4 Differentiate between input and output metrics

When choosing metrics, consider whether they are input metrics (things you control) or output metrics (results reported to leadership). Khalid (ex-Meta, DoorDash PM) explains:

"If you’re running an ads team focused on improving ad interfaces and your goal is increasing revenue, ‘revenue’ is an output metric. But an input metric like ‘advertiser growth’ may be a better focus for your team’s efforts."

4.5 Understand the nuances of picking your metrics

Before choosing a North Star Metric (NSM), be sure to figure out what the most important action is that a user does in the user journey. 

From there, come up with a list of possible NSMs and then evaluate their pros and cons as well as their trade-offs. Khalid  says, "The aim isn’t to find a perfect metric, but a good enough metric that encapsulates the business/user goal while being aware of its potential downside."

4.6 Anchor your decision on the company’s core mission

Always go back to what the company is trying to achieve, whether you’re answering a metric definition or metric change. This is especially useful if you’re asked a trade-off question about cannibalization, which many candidates report getting a lot in recent interviews.

4.7 Consider different stakeholders’ perspectives

Products serve multiple types of users, and each group will have different key metrics.

"In an eCommerce business, consider different metric sets for each type of user: Buyers (e.g., new buyers, active users, spend per user), Sellers (e.g., active sellers, active listings), and the Company itself (e.g., revenue, profitability),"  says Dessy.

The same logic applies to other industries, such as ads, where users, advertisers, influencers, and the company all have distinct success metrics.

4.8 Think out loud and justify your choices

Lastly, always walk your interviewer through your thought process. Explain why you are choosing specific metrics, how they relate to business goals, and any trade-offs involved. Clear reasoning is just as important as the final answer.

5. How to prepare for product metrics questions↑

With a lot to cover, it’s best to take a systematic approach to make the most of your practice time. 

Below you’ll find links to free resources and four introductory steps that you can take to prepare for product metric interview questions.

5.1 Familiarize yourself with the key metrics

Different companies prioritize different metrics, but you should have a solid grasp of the core activation metrics like adoption, engagement, quality, retention, etc.

If your interview requires setting goals for an AI product, Gal (ex-Google Sr. PM) says it's important to note that you’re setting goals for a product built in a probabilistic world, where the system's outputs are unpredictable. Therefore, your answer should take into account metrics that say something about the quality and safety of the model's output, and not only usage.

To get you started, here are the most important AI product metrics you need to know:

Output quality metrics

In short, you want to measure whether the AI is doing its job well. You should define "accuracy" concretely: accuracy of what, measured against which ground truth, and defined by whom. Some of the behavioral signals from users that you could track: 

  • How often do they accept a suggestion?
  • How heavily do they edit a suggestion, and how often do they discard it entirely? A discarded output is a strong sign the model missed.

Hallucination rate

This should be tracked as its own metric rather than folded into general accuracy, ideally with a rate the team agrees it will not launch above. 

Trust and safety guardrails

What guardrails are put in place to prevent harmful or policy-violating outputs and behavior across different user groups, and what happens when the model is not confident (for example, routing to a human or a safe fallback)?

System guardrails (latency and cost per query)

You need to account for latency, accuracy, and cost in your AI design. Every interaction has a real cost per query, so usage is not free the way it is in a classic consumer product. 

Adoption and business outcomes 

Metrics like activation, repeat use, and retention, and the business impact a product was built for still matter. But you’ll need to read them next to the quality metrics above.

“A useful way to structure the whole answer is to put them in tiers,” Gal says. Go with safety, then quality, product, and then business, plus a north star and guardrails.

As for measuring these metrics, Gal says that it is important that you differentiate between offline and online evaluation in your answer.

  • Offline evaluation means a golden dataset (labeled examples of real tasks, with named labelers) that the model is tested against before launch and after every model update, with go/no-go thresholds.
  • Online evaluation means what you watch after launch: A/B tests, behavioral signals, and sampled human review of outputs. Success criteria should be defined before launch, not after the results come in.

5.2 Study the company you're applying to

Get acquainted with the company you’ve applied to. In many cases, the product questions you’ll be presented with will be based on real-life cases the company is facing. If you’re applying to a specific team, study up on their products, the user, etc.

Take the time to find out which products you’ll most likely be working with, based on the job description, and research them. Look up relevant press releases, product descriptions, product reviews, and other resources in order to discuss what’s most important to the role: the company’s product.

If you'd like to learn more about a specific company's PM interviews, then we'd encourage you to check out our guide for that company below :

5.3 Learn by yourself

Learning by yourself is an essential first step. We recommend you make full use of the free prep resources on this blog and also watch some mock interviews on our product management YouTube channel. That way you can see what an excellent answer looks like. 

Once you’re in command of the subject matter, you’ll want to practice answering questions. But by yourself, you can’t simulate thinking on your feet or the pressure of performing in front of a stranger. Plus, there are no unexpected follow-up questions and no feedback.

That’s why many candidates try to practice with friends or peers.

5.4 Practice with peers

If you have friends or peers who can do mock interviews with you, that's an option worth trying. It’s free, but be warned, you may come up against the following problems:

  • It’s hard to know if the feedback you get is accurate

  • They’re unlikely to have insider knowledge of interviews at your target company

  • On peer platforms, people often waste your time by not showing up

For those reasons, many candidates skip peer mock interviews and go straight to mock interviews with an expert.

5.5 Practice with ex-interviewers

In our experience, practicing real interviews with experts who can give you company-specific feedback makes a huge difference.

Find a product manager interview coach so you can:

  • Test yourself under real interview conditions

  • Get accurate feedback from a real expert

  • Build your confidence

  • Get company-specific insights

  • Learn how to tell the right stories, better.

  • Save time by focusing your preparation

Landing a job at a big tech company often results in a $50,000 per year or more increase in total compensation. In our experience, three or four coaching sessions worth ~$500 make a significant difference in your ability to land the job. That’s an ROI of 100x!