skip to content

How do you normalize two job offers made in cities with very different living costs?

level: seniorimportance: nice to knowfreq 33%

answer

  1. Correct first, compare second
  2. Only the part you spend scales
  3. Housing dominates the difference
  4. Compare each package to its own local band
  5. Moving costs get their own line

basics

~10 s

Put both packages on one footing before comparing: apply a cost correction to the portion you would actually spend, compare each package against its own local band, and count one-time moving costs separately.

solid answer

~50 s

Do the correction before the comparison, not after, or the larger raw number will have already anchored you. Three moves. First, split each package into what you would spend locally and what you would save or hold — only the spending part scales with local costs, so apply the correction there rather than to the whole figure. Second, compare each package against its own local market band for the level, since "upper part of the band here" is more meaningful than a cross-city figure. Third, treat one-time costs — moving, a lease break, a period of double housing — as their own line rather than smearing them across the package. Also ask, in writing, how the employer handles pay if you relocate later; location-pay policies differ between employers and can change. Take-home also depends on local taxes and benefits, which vary by jurisdiction — check your own situation rather than assuming.

go deeper

for a junior

Know that packages in different cities are not comparable as printed, and that housing is usually the biggest single driver of the difference.

for a middle

Explain the mechanics: correct the portion you would spend locally, leave saved and one-time components uncorrected, and compare what remains.

for a senior

Show the judgement: build a housing estimate for your own life, test whether the conclusion survives a wrong estimate, and confirm relocation-pay terms in writing.

for a principal

Own the non-financial half of a move — support networks, a partner's work, reversibility — and say what corrected pay gap would make you accept those costs.

## The problem Two packages quoted in two markets are not comparable as printed. The larger figure may buy less. Worse, whichever figure you read first sets an anchor, and corrections applied afterwards tend to be argued down. So the correction belongs **before** the comparison — in offer-evaluation terms, the pay row of the scorecard is corrected first and scored second. ## Correcting the right part A common error is to divide the whole package by a single cost index. Costs scale the money you spend locally — housing above all, then transport, childcare, food, services. They do not scale money you save or hold, and one-time components behave differently again. A workable method: 1. Estimate what you would actually **spend** in each city at the life you intend to live there. Housing dominates, so start there. 2. Apply the cost difference to that spending portion only. 3. What remains is the part each package leaves you at the end of a year. Compare *that*, plus the non-cash components, rather than the headline figures. This is why practitioners often say the useful comparison is the surplus, not the salary: two packages can differ by a wide margin on paper and leave you in nearly the same position once housing is paid. ## An illustrative comparison Take two platform-engineering offers at the same level. The figures here are illustrative only — invented for the arithmetic, not market data, and not a benchmark for any market or level; substitute your own numbers. - Offer A's package is about 11% larger than Offer B's. - A comparable basket in A's city — housing weighted heaviest — runs roughly 27% above B's. - Applying the correction to the spending portion first, A's 11% advantage inverts: the same life costs more than the extra pay covers, and B leaves more at the end of the year. The direction of that result is the point, not the digits. An 11-point pay advantage does not survive a 27-point cost gap on the part of the package you spend. ## The caveats that keep this honest - **Indices are rough.** Cost-of-living indices use a basket that may not match your life. Someone who rents a small place near work and someone who needs school-age space in a specific district face very different gaps in the same two cities. Build your own housing estimate before trusting a general index. - **Not everything scales.** Components paid once, and any component whose value depends on the company rather than the city, do not move with local costs. - **Take-home varies by jurisdiction.** Local taxes, mandatory contributions and what benefits cost you out of pocket all differ by place and change over time. State that as a variable to check for your own situation rather than modelling it as a fixed rule. - **Location-pay policy differs by employer, and can change.** Many companies set pay by work location; many do not; some pay by a broad zone. If remote work or a later move is plausible for you, ask in writing what happens to pay if you relocate, and treat a verbal reassurance as unscored. ## The parts that are not money A cost correction covers the arithmetic and misses the rest of the move: distance from family and support networks, whether your partner can find work there, the commute you would actually do, and the cost of reversing the decision if the job does not work out. Those belong in the life-fit row of your scorecard, weighted before you saw either package. A move that scores well on corrected pay and badly on life fit is a real trade — make it explicitly rather than discovering it in month four. ## Rehearsing the comparison This is a good comparison to walk through out loud with a mock-interview partner, because the arithmetic is easy to hide behind. Have them ask what the correction was applied to, where the housing estimate came from, and what happens to the conclusion if the estimate is off by a quarter. If the answer flips under that pressure, the two offers are effectively tied on pay and the decision belongs to the other rows.

  • Why not simply divide each package by a published cost-of-living index?
    Because the index scales the whole figure, and only the part you spend locally actually moves with local costs. Money you save, and one-time components, do not. Index baskets also may not match your life — housing needs differ enormously between people in the same two cities. Build your own housing estimate, apply the correction to spending, and compare what is left.
  • What would you want confirmed in writing before you weigh a location-adjusted offer?
    How pay is set by work location, and what happens to it if you relocate later or the team's remote policy changes. Employer policies on this vary and are revised over time, so a verbal reassurance is not something you can score. If it is not written down, weigh the package as it stands today rather than the version you hope for.
  • Which costs of moving cities are easiest to leave out of a comparison?
    The one-time and non-financial ones: the move itself, a lease broken or a period paying for two homes, and the cost of reversing the decision if the role disappoints. Alongside those sit distance from support networks and whether a partner can work there. Give them their own line and their own row rather than smearing them into the package.

saying these in an interview costs you the question

  • Comparing raw package figures across two markets without any correction
  • Applying a cost index to the whole package instead of the spending portion
  • Trusting a general index without checking housing for your own situation
  • Assuming location-based pay policy is the same at every employer
  • Stating a take-home or tax outcome as if it were the same everywhere
  • Leaving moving costs and distance from family out of the comparison entirely

context