Published Pay Bands

What we pay

Every band, every level, published and not negotiable

The number on the advert is the number you get. Nobody here is paid more because they pushed harder in the offer call.

LevelScopeBandPeople here

L1

Joining

Works on a defined piece with review. First six months are meant to be slow.

Band£52,000

People here2

L2

Established

Owns a feature area end to end, including the support burden it creates.

Band£68,000

People here6

L3

Senior

Owns a system, says no in writing, and is trusted on a migration call alone.

Band£92,000 – £108,000

People here7

L4

Principal

Sets direction for an area across the product and carries the consequences of it.

Band£124,000

People here1

The rules around it

  • One band per level, with a range only where the level genuinely spans two jobs.
  • Reviewed against market every January and moved up, never down.
  • Location does not change the band. Bristol and Galway are paid identically.
  • No bonus scheme, no commission, and no discretionary uplift anyone has to ask for.
  • Everyone can see everyone else's level. Not the individual numbers, but the band they sit in.

Know the number before you apply

Every open role carries its band in the advert, so you can decide whether a conversation is worth your evening before you have it.

About this block

Published Pay BandsPRO

A pay transparency table whose track pills swap the band column while the levels, their scope, and the headcount at each stay in place, closing on the written rules that govern the numbers beside a soft panel carrying the call to action.

Careers55: Published Pay Bands

A pay transparency table whose track pills swap the band column while the levels, their scope and the headcount at each stay in place, closing on the written rules that govern the numbers beside a soft panel carrying the call to action.

Upgrade to Pro

Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.

Upgrade Now

Installation

Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.

Radix flavor

bash
npx shadcn add "https://ui.beste.co/r/careers55?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

bash
npx shadcn add "https://ui.beste.co/r-base/careers55?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/careers55.tsx plus the badge23 and button21 components it uses for the eyebrow and the action.

Quick start

The installed file exports careers55Demo alongside the block: the exact props behind the preview above. Spread it to get a working table in one line.

tsx
import { Careers55, careers55Demo } from "@/components/beste/block/careers55";

export default function PayPage() {
  return <Careers55 {...careers55Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

tsx
import { Careers55 } from "@/components/beste/block/careers55";

export default function PayPage() {
  return (
    <Careers55
      badge={{ label: "What we pay" }}
      heading="Every band, every level, published and not negotiable"
      description="The number on the advert is the number you get."
      tracks={["Engineering", "Operations"]}
      columns={["Level", "Scope", "Band", "People here"]}
      levels={[
        {
          level: "L1",
          title: "Joining",
          scope: "Works on a defined piece with review.",
          bands: { Engineering: "£52,000", Operations: "£38,000" },
          people: "2",
        },
        {
          level: "L3",
          title: "Senior",
          scope: "Owns a system and is trusted on a migration call alone.",
          bands: { Engineering: "£92,000 to £108,000", Operations: "£58,000 to £66,000" },
          people: "7",
        },
      ]}
      rulesTitle="The rules around it"
      rules={[
        "One band per level, with a range only where the level spans two jobs.",
        "Location does not change the band.",
      ]}
      ctaTitle="Know the number before you apply"
      ctaBody="Every open role carries its band in the advert."
      button={{ label: "See open roles", href: "/careers" }}
    />
  );
}

Props

PropTypeDefaultDescription
badge{ label: string }Eyebrow above the hairline rule, rendered through Badge23
headingstringSection heading in the left column of the header
descriptionstringSupporting paragraph, right-aligned from md up
tracksstring[][]Track pills, the first one starts selected
columnsstring[][]Column headings, also reused as mobile row labels
levelsLevel[][]Table rows, each carrying a band per track
rulesTitlestringHeading above the written rules
rulesstring[][]The policy that governs the numbers
ctaTitlestringHeading in the closing panel
ctaBodystringParagraph in the closing panel
button{ label: string; href: string }Action in the closing panel
classNamestringExtra classes for the outer section
ts
type ActionLink = {
  label: string;
  href: string;
};

type Level = {
  level: string;
  title: string;
  scope: string;
  bands: Record<string, string>;
  people: string;
};

Behavior notes

  • bands is keyed by track name, so every entry in tracks needs a matching key on every level. A missing key renders an em dash rather than breaking the row.
  • Only the band column changes when the track switches. Level, scope and headcount are shared, which is the point: the tracks are two pay scales over one ladder, not two different ladders.
  • The column header row is hidden md:grid, so on mobile the labels come from columns[2] and columns[3] rendered inline inside the band and headcount cells instead. Passing fewer than four column labels leaves those mobile labels blank.
  • Because the header row is hidden on mobile, its margin would collapse there. The rows container carries mt-8 md:mt-0 to compensate, so the spacing above the table is correct at both widths.
  • Rows use border-b rather than border-t, matching the header's border-b, so the rules read as one continuous table.
  • Figures use tabular-nums in both the band and headcount columns, so they stay optically aligned across different digit counts.
  • The track pills are real button elements with aria-pressed and explicit cursor-pointer, since Tailwind v4 buttons default to cursor: default.
  • The closing panel is flex flex-col justify-center, so its content stays vertically centered against the rules list beside it however long that list runs.

More Careers blocks

View all Careers
PRO

careers35

Salary Bands Table

Transparent salary bands with level, role, visual range bars, and equity details. Pay transparency table with responsive card fallback.

PRO

careers57

Open Roles With Published Bands

A short roles list where the pay band sits on the row rather than behind an application, with a written empty state for when nothing is open and a speculative line underneath.

PRO

careers52

Single Role Detail

A job description laid out as a reading column with checked responsibility lists and a candid caveat panel, against a sticky rail carrying the published salary band, level, and location alongside the apply action.

FREE

careers51

Filterable Open Roles List

A light editorial careers section with a monospace eyebrow over a hairline rule, a two-column heading, and a sticky culture photo with a gradient caption beside team filter pills and hairline job rows showing location, contract type, and a hover arrow.

PRO

careers21

Compensation & Total Rewards

Transparent compensation philosophy with salary, equity, bonus, and perks cards. Shows total rewards approach with highlighted details.

PRO

careers6

Tab-Filtered Job Board

Tabbed job board with department filters using shadcn Tabs component. Browse positions by team with location and type details.