Skip to content
Protocore Design Systemv1.6.9
Patterns / Careers

Careers

Open roles grouped by team with mono labels, the benefits that back them, and a split apply CTA.

CAREERS
Live · @protocore/pds
Careers

Build the settlement layer

7open roles

We're a small team making money infrastructure that's boring on purpose. Come make it more so.

Why here
01
Deep-work default

Two no-meeting days a week and asynchronous by design. The calendar serves the work.

02
Ownership, real

Meaningful equity and the autonomy to ship the thing you were hired to judge.

03
Wherever you're sharp

Remote across the EU with quarterly on-sites, or a desk in Berlin if you want one.

04
Health and headroom

Full cover, a learning budget, and 30 days off that nobody side-eyes.

When to use

A careers page has to do two jobs at once: convey what it's like to work here, and make the open roles trivially scannable. It groups roles by team under mono labels so a candidate jumps straight to their discipline, states the benefits as principles rather than a bullet dump, and ends on a fork — apply to a listed role, or pitch one that isn't. The single accent moment is the live role count.

Use it for the careers or jobs index. Company story and mission belong on the about page.

Structure

01
Page header
A PageHeader with the pitch and a SignalCount of open roles — the one reserved-accent figure on the page.
02
Grouped roles
Roles grouped by team, each under a mono Eyebrow label with a bracket count, listed as ListingRows.
03
Benefits
A two-column Grid of PrincipleTiles states what's on offer as convictions, not a checklist.
04
Apply CTA
A DualCTA forks between applying to a listed role and pitching a new one.

Key components

Open any component to read its full API and live examples.