Starting point

A careers site that publishes the pay band on every role

Every one of the ten sample roles a recruiter finds in the website builder carries a published salary band and the team that owns it. Candidates filter on exactly those two fields, and most careers pages publish neither.

Careers Site website template — the home page it produces

Shown in the Signature design style — one of 15 you can switch between; your business content carries over.

The full homepage
Careers Site website design example — The full homepage
A full inner page
Careers Site website design example — A full inner page
Another full inner page
Careers Site website design example — Another full inner page

A role without a band is a role nobody applies to

The jobs collection defines eight fields, and salary is one of them — not an optional note, a field, so every role either has a band or is visibly missing one. Each role links to the team that owns it, and the five teams have pages of their own with a size and a description of what they run. A separate benefits sheet carries the long detail, and eight FAQ answers cover the hiring process a candidate is trying to read between the lines.

What the sample site comes with

A jobs collection with eight fields and ten sample roles, each with its own page, a teams collection with five entries, a benefits page, eight FAQ answers across two pages, and four pages.

Anything on that list that takes something from a visitor or reads from a live schedule — a form, a booking, a coupon code, a subscribe box, a class timetable, a listing fed by a collection — goes online with Storefront Pro. Storefront publishes the rest of the page exactly as you built it; where this template gives one of those a page of its own, that page is the one that waits for the upgrade.

What the site covers

4 pages included

What is in scope, and what stays in your own systems

Applying is an outbound URL you set per role. There is no applicant tracking, no CV upload, no scheduling and no candidate account — this is the shop window of a hiring process, not the process.

Every count and price on this page was read out of the template itself rather than written by hand, which is why the numbers match the site you actually get.

What you get when you publish it

Questions people actually ask

Why is the team on a posting a record rather than a word I type?

Because five teams ship as their own entries — Devices, Product, Field Operations, Customer Success, Finance and People — each with its own description, and every role points at one of them. That gives each team a page listing only its own openings, and the team block under the roles list reads the same source. Rewrite a team's description once and it changes everywhere it appears; adding a sixth team is a record rather than a code change, and headcounts cannot drift between two hand-kept lists.