Career Path · Chapter 4

How to Evaluate a Job Offer Before You Accept

A framework for assessing a job offer beyond the salary — covering company health, culture, role quality, total compensation, and the red flags most candidates miss.

10 min read

The hiring process is designed to help companies evaluate candidates. There is no equivalent structure helping candidates evaluate companies. By the time you receive an offer, you have been through rounds of interviews, you are emotionally invested, and the pressure to decide quickly is real. Most people at this stage are asking "should I take it?" when the more useful question is "have I gathered enough information to decide?"

This guide gives you that framework.


Why Offer Evaluation Gets Skipped

Several forces conspire against careful offer evaluation:

Emotional investment. By the time you have an offer, you have spent weeks in the process. You want it to work. That desire to want it to work can cause you to give benefit of the doubt to information that should give you pause.

Scarcity pressure. If this is the only offer you have — or if you have been searching for a long time — the offer feels more valuable than its actual merit. Job scarcity inflates the apparent attractiveness of whatever is available.

Time pressure. Most companies give candidates five to seven business days to decide. That is not much time. Without a pre-existing framework, it is easy to spend that time on surface-level comparison rather than meaningful diligence.

Social validation. Friends and family will often say "that is a great company" or "that salary is good" based on information that is much less complete than what you have access to. Their validation feels reassuring and can substitute for real analysis.

None of these forces are useful. Building an evaluation framework in advance — before you have an offer, before you are emotionally engaged — is how you make this decision well.


The Four Things That Determine Whether a Role Is Actually Good

Before getting into the specific questions, it helps to name what you are actually evaluating. Every job offer is a bundle of four things, each of which can be independently good or bad:

1. The role itself — Is the actual work meaningful, stretching, and aligned with where you want to go? Will you be building skills that matter for your long-term trajectory?

2. The compensation — Is the total package (not just base salary) competitive for the market, the industry, and your level? Are there hidden costs (required travel, long hours, lifestyle inflation in a high-cost city) that erode the apparent number?

3. The company — Is the organisation financially stable, culturally healthy, and likely to exist in a recognisable form in three years? Does it have the trajectory you want to be part of?

4. The people — Are your manager and immediate team people you can learn from, work alongside effectively, and trust to advocate for you?

A role that scores poorly on any one of these four dimensions is a problem. A role that scores poorly on two or more is a mistake, however strong the other factors look.


Evaluating the Role

Ask your future manager these questions before accepting — in the final interview round or during the offer deliberation period:

  • "What does success look like in this role in the first 90 days?" If they cannot answer this concretely, the role may lack clear scope or ownership.
  • "What happened to the last person in this role?" Promoted, left for a better opportunity, managed out, or the role is new — all tell you something different.
  • "What are the biggest unsolved problems in this function right now?" This tells you what you are actually walking into.
  • "How would you describe the typical week for someone in this role?" The reality of how time is spent often differs from the job description.
  • "What opportunities are there to grow into more responsibility over time?" A role with no growth path is a plateau, not a stepping stone.

The answers matter less than the quality of the thinking behind them. A manager who has thought carefully about what they need, what the role requires, and how success will be measured is a manager worth working for.


Evaluating the Company

Company evaluation requires going beyond the polished interview experience and finding information from sources the company does not control.

Financial health indicators:

For public companies, revenue growth, profitability, and cash position are in quarterly filings. For private companies, indicators include:

  • Recent funding — when was the last round, how large, and who led it? (Crunchbase)
  • Headcount trend — is the company growing or has it been laying off? (LinkedIn headcount over time)
  • Product trajectory — is the core product gaining or losing traction? (app store reviews, G2 scores, customer sentiment on Reddit or Hacker News)
  • Revenue signals — media coverage mentioning revenue, customer counts, or growth rates

A startup with no clear path to profitability and eighteen months of runway is a different risk profile from a Series C company growing 40% year-over-year. Neither is inherently better — but you should know which one you are joining.

Culture and management quality:

  • Glassdoor reviews filtered by role and recency. Look for patterns, not individual reviews. Are there consistent themes about management, work-life balance, or growth opportunities? Do leadership ratings trend positive or negative?
  • LinkedIn tenure data. Search for people who have recently left the company or the specific team. Short tenures (under 18 months) across multiple people on the same team is a yellow flag. Very short average tenure across the whole company is a red flag.
  • Talk to people who work there. If you know anyone inside the company — or can find recent employees through LinkedIn — a 20-minute conversation will tell you more than any amount of public research.

Questions to ask in the final interview stage:

  • "How would you describe the culture of this team specifically?" (Not the company — the team.)
  • "What is something that could be better here that you wish was different?"
  • "How does the company respond when things go wrong or a project misses its targets?"
  • "Can you tell me about someone who grew significantly within the company and how that happened?"

Evaluating Total Compensation

Salary is the most visible line. It is rarely the most important one.

Component What to verify Base salary Compare to market 50th–75th percentile (Glassdoor, Levels.fyi) Annual bonus Target % and whether it has actually been paid historically Equity (RSU/options) Vesting schedule, cliff, strike price, and company valuation basis Healthcare Employee vs. employer contribution, deductible, network quality PTO and leave Days, policy on carry-over, parental leave, sick leave Remote / flexibility Policy vs. actual practice; commuting cost if office-required Learning budget Annual amount and what it covers (courses, conferences, books)

Equity deserves special attention. RSUs and options are frequently the largest single component of compensation at tech companies and startups, yet they are the component most misunderstood by candidates.

For RSUs at public companies: multiply the number of units by the current share price, divide by the vesting period, and add to your annual base. That is your total annual compensation.

For options at private companies: the exercise price, the company's most recent 409A valuation, and the current preferred share price all matter. Options are not worth the paper they are printed on unless the company is acquired or goes public at a valuation above your strike price. Be conservative in your assumptions.

The hidden costs of compensation:

  • A $20,000 salary increase in San Francisco vs. Amsterdam can easily net negative after taxes and cost of living adjustment
  • A "hybrid" role that requires four days per week in the office in a different city has a real commuting and housing cost
  • A role with unlimited PTO often provides less effective time off than one with 25 fixed days — research the culture around how much leave people actually take

Reading the Red Flags

Some warning signs are not obvious until you know to look for them. Here are the ones most commonly missed.

Vague answers to specific questions. When you ask "what does a typical week look like?" and you get generalities, or when you ask "what happened to the last person in this role?" and you get deflection, something is being avoided. Specific questions deserve specific answers from people who know the role well.

Excessive speed or pressure. "We need an answer by Friday" with less than five days to decide, pressure to skip reference checks, or urgency about a role that has been posted for six weeks — this asymmetry between their urgency and the timeline of the actual need is a red flag. It usually means either they have already lost other candidates or they want to prevent you from doing diligence.

Inconsistent information. If the recruiter, the hiring manager, and the team all describe the role slightly differently, nobody has agreed on what they need. You will likely be held accountable to whichever definition is most convenient at any given moment.

High turnover in the team. More than two people from a team of eight having left in the last twelve months is worth investigating. It is not automatically a dealbreaker — high-growth teams sometimes have high natural turnover — but you should understand why people are leaving.

Vague equity terms. Any company serious about equity as part of compensation should be able to give you the number of shares offered, the total shares outstanding (so you can calculate your percentage), the current 409A valuation, and the vesting schedule. Vague answers ("we offer competitive equity") or resistance to disclosing these details is a meaningful red flag.

Culture that only sounds good. "We are like a family here" often means unclear boundaries and an expectation of personal sacrifice. "We move fast and break things" often means poor process and little documentation. "We work hard and play harder" sometimes means consistently excessive hours. Translate the rhetoric before internalising it.


Making the Decision

Once you have gathered information across all four dimensions — role, company, compensation, people — the decision is simpler. Very few offers are uniformly excellent or uniformly bad. Most require trade-off thinking.

A useful framework: score each dimension from 1 to 5, then identify your deal-breakers in advance.

Some things are trade-offs. A role with genuinely excellent learning potential at a slightly below-market salary might be worth taking if the skills you build will compound your earning power in two years. A role with excellent compensation but a weak manager might be worth taking if you have strong self-direction and do not need active mentorship.

Other things are not trade-offs. If your gut is telling you the culture is toxic, or the company's financial runway looks like six months, or the manager gave you three different answers about what the role entails — those are not factors to weight against a good salary. They are exit criteria.

The clearest signal that an offer is wrong: imagining yourself in the role two years from now, and feeling relief rather than anticipation at the thought of it being over.

The clearest signal that an offer is right: imagining yourself in the role three months in and feeling like it is exactly the challenge you needed.


Accepting a job is one of the most consequential decisions you make. The company and the manager you choose will shape your skills, your network, your confidence, and your next opportunity. Evaluate accordingly — before the clock runs out.

Continue Reading