How to Build a Hiring Page That Actually Attracts Candidates

A hiring page is the single most leveraged piece of recruiting collateral you will ever write. One URL, shared once, that does the job of a recruiter, a brochure, an application form, and a brand statement at the same time. When it works, you wake up to a queue of qualified applicants. When it does not, you keep posting on LinkedIn wondering why nobody good is applying.

Most hiring pages do not work — not because of taste, but because of structure. The page asks for the wrong things in the wrong order, hides the information candidates came to find, and ends with a form that feels like filing taxes. This is a guide to building one that does the opposite. Eight elements, each with a specific job, each with a specific failure mode.

What a hiring page actually has to do

Before structure, intent. A hiring page has three jobs, and they happen in this order:

1. Convince the candidate the role is real and worth their time. The first 10 seconds.
2. Give them enough information to self-select in or out so you do not waste your time interviewing the wrong people. The next 60 seconds.
3. Make applying frictionless for the people who decided yes. The last 30 seconds.

Every element on a hiring page should serve one of those three jobs. If something does not, cut it. Most pages fail by burying job #1 under company-boilerplate, skipping job #2 entirely, and then asking for a 20-field form at job #3. Reverse the priorities and the page starts working.

1. A role title that names the actual role

The most important line on the page is the H1, and the most common mistake is writing it like an internal HR ticket.

Bad: "Marketing Specialist II — Remote (Full-Time, US/Canada, $80K–$110K, 401K Eligible)"
Good: "Growth Marketer — first marketing hire at a 7-person SaaS"

The good version tells a candidate three things in eight words: what the role is, where it sits in the company, and what stage the company is at. A senior marketer reading the bad version cannot tell if this is a real role or a content-mill content marketer position; a senior marketer reading the good version knows immediately whether to keep reading.

Rule of thumb: write the title for the candidate's mental model, not your HR taxonomy. The leveled job title goes in the offer letter; the H1 goes on the page.

2. A one-paragraph hook that says why the role exists

Every hiring page needs one paragraph, in the first 200 pixels, that answers "why does this role exist right now?" That paragraph is the difference between a page that converts and a page that gets bookmarked and forgotten.

Three sentences is enough:

> We are a 7-person team that just crossed $1M ARR with zero marketing hires. Our growth has come entirely from founder-led content and word of mouth, and we have run out of hours in the week to do it ourselves. We are hiring a first marketer to own the next 10x of growth — channels, content, distribution, and the stack.

That paragraph does what a generic "About us" never can: it tells the candidate why the company is hiring now, what success looks like, and how the role sits inside the team. It also functions as a self-selection filter — a candidate who wants a Series-B marketing org with 12 reports and a Salesforce instance reads this and bounces, which is exactly what you want.

3. The "what you will actually do" list — not a job-spec dump

The middle of the page is where most hiring pages collapse. They turn into a bullet list of generic responsibilities ("Own the marketing function," "Drive growth across paid and organic channels") that could apply to any company in any industry. Candidates skim past it.

The fix is to be brutally specific about the work itself. Replace generic responsibilities with concrete first-90-day deliverables.

Generic:
- Own the marketing function
- Drive growth across paid and organic channels
- Collaborate with cross-functional teams

Specific:
- Ship 2 SEO landing pages a week, starting week 2
- Take over our LinkedIn account (8K followers) and grow it to 25K by quarter-end
- Run our first paid experiments on Reddit and X — budget $2K/mo to start
- Stand up basic analytics so we can see channel ROI inside a month

A candidate reading the specific version can immediately decide whether they want that job. A candidate reading the generic version learns nothing.

4. A "who you are" section that filters, not flatters

The "what we are looking for" list is the second-most-skipped section after company boilerplate. It usually reads like a checklist of vague virtues ("strategic thinker," "data-driven," "passionate self-starter") that filters nobody out.

Two changes fix this:

• Lead with the must-haves, not the nice-to-haves. Three must-haves is the right number. If you can say "we will hire someone who has these three things and no others," you are writing a real list.
• Be honest about the must-not-haves. "We are not the right fit for someone who needs a defined playbook." "We are not the right fit for someone who wants direct reports in year one." Those lines repel the wrong applicants more effectively than any qualifier list attracts the right ones.

A good "who you are" section makes about 60% of casual readers self-select out. That is the design goal. If 100% of readers think they could do the job, your filter is broken.

5. Compensation, transparently

The single biggest single-element conversion lift on a hiring page is showing the salary band. Pages that publish comp convert at roughly 2x the rate of pages that do not. There is no industry where this is not true.

The mechanics matter:

• Show a range, not a number. A band signals you are open to leveling the offer to the candidate's experience. A single number signals you have already decided.
• Show the band in the first viewport. Either next to the title, in the hook paragraph, or in the right-rail sidebar. Burying it at the bottom is functionally equivalent to hiding it.
• Include equity if early-stage. "Cash band: $140K–$180K, equity: 0.4%–1.2%, vesting standard." The candidate is going to ask anyway; pre-empting it builds trust.

Founders worry that publishing comp will mean overpaying or underpaying. In practice, publishing the band you would offer privately costs you nothing and converts more candidates. The page that hides comp gets fewer applicants and the same private negotiations.

6. A short, structured application form

The form is where 40–60% of interested candidates drop off. The fix is not "ask less" — it is "ask the right things, in the right order."

The minimum:

• Name, email (always)
• One link — the candidate's portfolio, GitHub, LinkedIn, Twitter, or website. One field, not five.
• Two short questions that match the role's specific deliverables. Not "tell us about yourself" — "tell us about a marketing channel you have grown from zero to material revenue."
• One optional video/voice answer for roles where personality matters (creator hires, customer-facing roles, founder roles)
• One optional file upload for portfolio-first hires (designers, video editors, engineers with side projects)

What does not belong on the form:

• A long-form cover letter field. Nobody reads them and the best candidates skip them.
• Demographic checkboxes (handle these on a separate, optional, post-submission page if you must).
• Anything that requires the candidate to write a paragraph that you will not read.

A well-designed form takes a candidate 4–7 minutes to fill out. A badly designed one takes 25 and 60% of strong applicants never submit. The form length is the single biggest lever between an interested reader and a submitted application.

7. A trust signal — small, real, specific

Candidates evaluating a small-company role read the hiring page partly as a due-diligence document. They are asking: is this company real, is the team competent, is this a good place to work?

Three small additions answer the question without turning the page into a marketing brochure:

• One line of social proof. "Backed by Combinator, Sequoia, and 12 angel investors" or "Profitable since 2024, 8,000 customers." One line. Not a paragraph.
• Two team-member photos with names and roles. A real face beats a logo wall.
• A "what we are not" line. "We are not a remote-first company — we expect quarterly travel to our office in Lisbon." "We are not a venture-funded company — we are profitable and intend to stay independent." Specificity converts. Vagueness repels.

Trust is built by what you are willing to say honestly. Pages that publish constraints honestly convert more applicants, not fewer, because the candidates who self-select in are the ones who fit.

8. A clear next step — visible from any scroll position

The Apply button is the final element and the most-failed. The common failures:

• The button is at the bottom of a 3,000-word page and there is no second one halfway up.
• The button says "Submit" or "Send" instead of "Apply for this role."
• The button is grey, low-contrast, and visually subordinate to the page's purple "Subscribe to our newsletter" button.

The fixes are trivial: keep the Apply button in the floating header or right-rail sidebar so it is visible at any scroll position; label it for the action it performs; make it the highest-contrast UI element on the page. The branded hire-page tools handle this by default; the hand-rolled hiring pages built in Webflow or Notion usually do not.

What a hiring page is NOT

Three things hiring pages should not be, even though most of them try:

• A company history. Save it for /about. A hiring page is not an investor pitch.
• A values manifesto. "We believe in radical candor and high agency" reads as either generic or unverifiable. Show, do not tell, by being specific about the work.
• A funnel for unrelated marketing. No newsletter signups, no "schedule a demo" CTAs, no chat widget. The page has one job. Let it do its job.

How to actually build one

The fastest path:

1. Open the hiring page builder of your choice. (hire.page ships with the structure above as the default template.)
2. Write the H1 and the hook paragraph first. If you cannot finish those in 20 minutes, the role is not clear enough to post yet.
3. Fill in deliverables, who-you-are, and comp. Keep all three short.
4. Build the form to the minimum-spec above.
5. Pick a custom domain — hire.yourcompany.com converts better than a /careers subroute on the main site. Branded URLs read as more serious.
6. Ship. Share the one link everywhere. Stop pasting the role into 12 different platform-specific forms.

If you want to skip step 2 entirely, every role-specific template on hire.page ships with a publish-ready JD that you can edit instead of writing from scratch — see the Founding Engineer template, the Product Designer template, or the full hiring page template gallery.

The hiring page is the centerpiece of the recruiting motion. The candidates who land on it decide, in 90 seconds, whether your role is worth applying for. The work above is what those 90 seconds cost. The candidates you attract for the next year of hiring are the return.

If you are still posting "DM me your reel" or routing applicants into a spreadsheet, the upgrade path is short — see why hiring from DMs is costing you and the 5 signs your hiring spreadsheet has stopped working. The hiring page is the thing both posts point you toward.

For more concrete examples of what working pages look like in the wild, see 10 careers page examples that convert. And for the element-by-element spec, 7 must-have elements of a great hiring page in 2026 is the companion to this one.

---

Build the hiring page that does this out of the box. hire.page ships with the eight-element structure above as the default — Notion-style editor for the role, structured application form, custom domain, branded design. Free plan; paid plans from $29/mo.