Skip to content
Back to Blog

Mar 24, 20265 min read

Salary-first cards: putting the price tag where your eye already is

Redesigning the list row around compensation. Why the number deserves the top-left slot, and what it means for jobs that hide pay.


Card hierarchy is a signal about what matters. When salary is a 12px gray pill below the title, you're telling the user "this is ancillary." When salary is the first thing on the card — bigger, bolder, colored — you're saying "this is the lede." We think it is.

"The first number you read should be the one you'd repeat to a friend describing the job."

Three salary treatments, one honest one

  • Specific band ($120k–$165k) — rendered full-size, color-coded green / amber / red by tier.
  • Single number ($140k) — same treatment; the card doesn't pretend a range exists.
  • Undisclosed — muted "Salary not listed" in --l-text-4. We deliberately don't invent a range from scraped peers; a guess would be worse than silence.

Why we color-code

Green / amber / red isn't a judgment of the role — it's a glanceable cue about where the comp sits relative to the national distribution for the role family. A $60k offer for a senior SRE reads red because it's below the 10th percentile for that band, not because $60k is a bad salary in isolation. You can turn this off in preferences; some users find the color pressure inappropriate for their market.