Hiring for a small startup or a growing side project often stalls at an unglamorous step: there’s no good place to actually post the role. A generic job board listing gets lost in hundreds of others, and building a full careers page inside your marketing site feels like overkill for one open position.
This is about writing a hiring page that actually gets read, and getting it live without treating it like a full engineering project.
Why a generic listing undersells the role
A job board posting is a form with fixed fields — title, description, requirements — competing against hundreds of other identical-looking forms. It’s fine as a distribution channel, but it can’t communicate what it’s actually like to work somewhere, and for a small team, that context is often the entire pitch. Someone choosing between a startup role and a comfortable job at a bigger company isn’t deciding based on a bullet-point requirements list; they’re deciding based on whether the team and the work sound worth the risk.
A dedicated page solves that, but building it inside your main site’s CMS or component library — for one role that might be filled in a few weeks — is a lot of setup for something temporary.
What the page actually needs to say
- What the role actually is, in plain language — not a wall of buzzwords copied from a template job description.
- Why someone would want to work here specifically — the actual problem you’re solving, team size, how decisions get made. This is the part a job board listing structurally can’t convey.
- Real requirements, not a wishlist. A bloated “nice to have” list filters out qualified candidates who self-select out unnecessarily.
- A simple way to apply — an email address or a short form, not a multi-page application portal for a five-person team.
Why this doesn’t need a careers-page system
A single open role doesn’t justify a careers-page CMS, especially for a small team hiring occasionally rather than continuously. What it needs is one well-written page that reflects your actual voice, live at a real URL you can post everywhere you’re sourcing candidates. Carrd fits this well — it’s fast to put together, doesn’t look like a template pulled from a generic careers-page theme, and can come down or get replaced the moment the role is filled without leaving unused infrastructure behind.
Writing a listing people actually want to read
Lead with the problem, not the org chart
What are they actually going to spend their time solving? This is more compelling and more informative than “we’re looking for a Senior Backend Engineer to join our team,” which could describe literally any company.
Be honest about stage and risk
If it’s an early-stage project with real uncertainty, saying so plainly (rather than projecting false stability) attracts candidates who are actually comfortable with that trade-off — and repels the ones who’d be a bad fit and leave in three months once the reality sets in.
Cut the requirements list in half
Research on this is fairly consistent: long requirement lists disproportionately discourage otherwise-qualified candidates from applying at all, especially candidates who read requirements as a strict bar rather than a rough guide. List the two or three things that are genuinely non-negotiable, and leave the rest for the interview.
Deciding where to actually post it
The page itself is only half the equation — it needs traffic to be worth having. Posting the link in relevant communities (a language or framework’s Discord, a niche subreddit, a “who’s hiring” thread) tends to outperform generic job boards for small, specific roles, since the audience is already self-selected for relevance. The dedicated page means every one of those posts can link somewhere that actually represents the role well, instead of a bare board listing competing with hundreds of others.
What to skip
Skip stock photography of generic “team collaborating” shots — they add nothing and reinforce the exact templated feeling you’re trying to avoid. Skip an elaborate multi-step application form for a small team; a resume and a short note to an email address is enough friction to filter for genuine interest without becoming a barrier on its own.
Quick checklist
- Describe the actual problem the role solves, not a generic title description.
- Say honestly what stage the company or project is at.
- Cut the requirements list down to what’s genuinely non-negotiable.
- Keep the application process to one simple step.
- Build it as a standalone page you can retire the moment the role is filled.
A hiring page’s job is convincing the right person this is worth the risk. That’s a writing problem more than a design one — put the effort where it actually matters.
Tested firsthand
