How Should You Design a Careers Page for a Small Team?

What should a careers page look like when your company only has a dozen people?

It should look honest and specific, not like a scaled-down version of a big company's careers site. Lead with what the work is, who the candidate would work with, and how the hiring process runs. Small teams win candidates on clarity and access to real people, so design the page around both.

Most small B2B companies treat the careers page as an afterthought. It is either missing, a single line about always looking for great people, or a copied layout with stock photos, a values grid, and an empty jobs board. None of that helps a good candidate decide whether to apply.

A careers page for a small team has a different job. There is no employer brand yet, no famous perks, and often only one or two open roles. What you do have is something big companies cannot offer: a candidate can see exactly who they would work with and what they would own. The design should make that visible.

Why does a small company need a careers page at all?

Because candidates check it even when they found the role elsewhere. A missing or empty careers page makes a small company look less stable than it is. A clear one answers early questions, filters out poor fits, and gives the hiring manager a link to send instead of rewriting the same pitch every time.

There is also a go-to-market angle people miss. Your careers page is read by more than candidates. Investors look at it to see where you are investing. Competitors look at it to guess your plans. Sellers read open roles as buying signals, which is a tactic I described in how to build an outbound list from job postings. Design with that audience in mind and do not publish anything you would not want a competitor to read.

Finally, the page is a quiet trust signal for buyers. A prospect evaluating a small vendor sometimes looks at the careers page to judge whether the company is growing or struggling. An active, well-kept page helps.

What should go at the top of the page?

Open with one plain sentence about what the company does and one about what working there is like, then a direct link to open roles. Skip the slogan. A candidate should know within seconds what the product is, how big the team is, and whether anything is open right now.

The open roles link matters more than any hero image. If roles exist, show them near the top with title, team, and location type, such as remote or in-office. If none are open, say so plainly and offer a way to stay in touch. An empty jobs widget with no message reads like a broken page.

I would also put the team size near the top. A line like "a team of twelve, mostly engineers" is the kind of detail that helps the right candidate lean in and the wrong one move on. Some people want a small team. Some do not. Let them decide early.

How should you show the team?

Show the actual people a new hire would work with, with names, roles, and a line about what each person owns. Real photos beat polished stock imagery every time. For a small company, the team section is the strongest selling point on the page, so give it room and keep it current.

I covered the design details of team sections in how to design a team section that builds trust, and the same principles apply here with one twist. On a careers page, the line under each person should say what working with them is like, not just their title. "Owns the onboarding flow and reviews every design change" tells a candidate far more than "Product Designer".

Keep it current. A careers page that still shows someone who left six months ago undermines everything else on it. If you build the team section from a CMS collection, removing a person is one edit, which makes this much easier to maintain.

How should each job posting be structured?

Each role should answer, in order: what the person will do in their first months, what they will own, who they will work with, what skills matter and which are optional, how pay and location work, and what the hiring steps are. Write it as plain prose with clear section headings, not a wall of bullet points.

The first-months section is the most useful and the most often skipped. Candidates want to picture the work. "In your first quarter, you will rebuild the trial onboarding emails and own the activation metric" is concrete. "You will drive growth initiatives" is not.

Separate required skills from nice-to-have skills honestly. Long lists of requirements discourage strong candidates who match most but not all of them. If a skill is truly optional, say so. If you can share a pay range, share it. Where pay transparency rules apply, check your local requirements before publishing.

Should you build the careers page in a CMS?

Yes, if you hire more than once or twice a year. A CMS collection for roles lets anyone on the team add, close, or update a posting without touching the page design. It also keeps every posting in a consistent structure, which makes each one easier to read and easier for machines to parse.

On Webflow, a roles collection with fields for title, team, location type, summary, first-months description, and status covers most needs. A template page then renders every role the same way. When a role closes, change the status rather than deleting it, so you keep a history of what you hired for.

Structured data is worth adding too. JobPosting schema describes each role in a format search engines can read, and I walked through one setup in how to add JobPosting schema to a Webflow CMS. Check search engine documentation for current requirements, because job listing features change more often than most schema types.

How do you make the application step easy?

Keep the form short: name, email, a link to a profile or portfolio, and one open question about why this role. Tell candidates what happens after they apply and how long it usually takes to hear back. Then actually reply to everyone, even with a short no.

Long application forms filter out the people with the most options, which are often the people you want most. Ask for the minimum needed to decide whether to have a first conversation. Everything else can come later.

The reply promise is where small teams can beat big ones. A candidate who gets a thoughtful response within a week remembers it. Put the expected timeline on the page and route applications somewhere a person checks, whether that is a simple applicant tracking tool or a shared inbox with a clear owner.

What mistakes make a small company's careers page look worse?

The common ones are stale postings, generic values lists, stock photos, missing pay information, vague role descriptions, and no explanation of the hiring process. Each one makes a small company look less organized than it probably is, and organization is exactly what candidates are trying to judge.

The values grid deserves a special mention. Six icons with words like "Integrity" and "Innovation" say nothing because every company claims the same six words. If you want to show culture, describe one real practice instead, like how decisions get made or how feedback works. One true sentence beats six abstract nouns.

Also watch for language that excludes people without meaning to. Phrases like "work hard, play hard" or "rockstar" put off many strong candidates. Plain descriptions of the work and the team are both more inclusive and more convincing.

What should you do next?

Rewrite the top of your careers page in two plain sentences and link straight to open roles. Replace stock imagery with real team photos and one line about what each person owns. Restructure each posting around the first months of work, add a short application form, and publish your reply timeline.

Careers pages are rarely treated as design work, but the same principles that make a pricing page or an About page convert apply here: say the specific thing, show real people, and remove friction from the next step.

If your careers page is missing, stale, or copied from a template that does not fit a small team, reach out. I am happy to help you structure it in Webflow so it stays easy to update.