How to write a job post that doesn't sound like every other job post
Most job posts read like they were written by a committee. Here's how to write one that sounds human, attracts the right candidates, and filters out the wrong ones.
You need a frontend engineer. So you Google "frontend developer job description," copy the first template you find, swap in your company name, and post it on LinkedIn. Two weeks later you have 200 applicants. None of them are right. Half don't read the requirements. The other half are so overqualified they'd be bored in a month. And the people who'd genuinely thrive at your eight-person company? They never applied.
The problem isn't your company. It's your job post.
Why your job post sounds like everyone else's
Most job description templates were designed for companies with hundreds of employees, dedicated talent acquisition teams, and legal departments reviewing every line. They produce posts with 12 requirements, four "preferred qualifications," and phrases like "cross-functional stakeholder alignment" that mean nothing to a candidate scrolling at 11 PM.
When you copy those templates, you end up describing a person who doesn't exist. "5+ years of React, 3+ years of Node.js, experience with AWS, CI/CD pipelines, GraphQL, team leadership, and a proven track record of delivering high-impact projects in a fast-paced environment." That's not a job description. That's a wish list for a senior staff engineer at a Series C startup, and you're seven people in a co-working space.
The result is predictable. Qualified candidates self-select out because they meet eight of your twelve requirements and assume they're not good enough. The candidates who do apply are the ones who ignore requirements entirely, carpet-bombing every opening with the same resume. You've built a filter, but it's filtering out the wrong people.
What a good job post for a small company looks like
Forget the template. A strong job post for a company your size has five parts, and none of them are "minimum qualifications."
What you'll do in the first 90 days
Don't list responsibilities. Describe outcomes. A candidate reading "manage the CI/CD pipeline" has no idea what their Tuesday looks like. A candidate reading "In your first month, you'll ship our new onboarding flow and set up error monitoring so we stop finding bugs from customer emails" knows exactly what they're walking into.
This section does two things: it gives the candidate a concrete picture of the work, and it signals you've thought about what this hire needs to accomplish. Both of those are rare. Both make you stand out.
What you need to already know
Three to five skills. Not twelve. Not eight. The absolute minimum someone needs on day one to do the work you described above. Everything else is a bonus.
Be honest about what's a hard requirement and what you can teach. If you need someone who knows React, say so. If you'd prefer someone who's used Tailwind but it's learnable in a week, don't put it in the requirements. Every line in this section is a gate. Make sure each one is worth losing a good candidate over.
What you'll learn here
This is your secret weapon against big companies. Google can offer $400K and a campus with free sushi. You can offer something they can't: scope, speed, and ownership. An engineer at your company ships to production in their first week. They talk to customers. They pick the tools. They see the direct impact of their decisions.
Spell it out. "You'll learn how to build a product from early users to product-market fit. You'll own features end to end, not hand off specs to another team. You'll work directly with the founders and have a voice in product direction." That's a compelling pitch for the right person, and it filters out people who need structure and process to feel comfortable.
What it's like to work here
Be honest. Not "we're a family" honest; nobody believes that, and it usually means "we'll guilt you into working weekends." Honest like: "We're eight people. Slack is our office. We do a weekly all-hands on Monday, no other standing meetings. Most of us work 9-to-6 in European time zones, but nobody tracks hours. The founders are technical and review PRs alongside everyone else."
Specifics build trust. Vague culture statements do the opposite. If a candidate reads your "about us" section and could swap in any other company's name without changing a word, rewrite it.
What you're offering
Post the salary range. Yes, you have to. In 2026, a job post without a salary range tells candidates one of two things: you're paying below market, or you haven't figured out your budget. Neither makes them want to apply.
Include equity if applicable, benefits, remote or hybrid or onsite, location constraints, and time zone expectations. Transparency here saves everyone time. The candidate who needs $180K isn't going to negotiate down to $120K, and you don't want to discover the mismatch after three rounds of interviews.
5 things to cut from your job post today
If any of these appear in your current job post, delete them. Right now.
"Fast-paced environment." Every startup says this. It communicates nothing. If you mean the workload is high, say "We ship weekly and priorities change based on customer feedback." If you mean people work long hours, be upfront about it so candidates can opt in or out.
"Self-starter." You're describing a functioning adult. Anyone who's held a job has started tasks without being told. This phrase takes up space and tells the reader nothing about what you need.
"X+ years of experience." Years are a terrible proxy for skill. A developer with two years of focused React work and five shipped side projects will outperform someone who spent six years maintaining a legacy jQuery codebase. Describe the capability you need, not the calendar time.
"Must be comfortable wearing many hats." Candidates read this as "we'll overwork you and call it culture." If the role spans multiple functions, describe them specifically. "You'll handle frontend development and own our design system" is honest. "Wearing many hats" is a red flag dressed as a perk.
"Competitive salary" without a number. If you can't name a range, you're not ready to hire. Candidates assume "competitive" means "we looked at Glassdoor and rounded down." A posted range, even a wide one ($100K-$140K depending on experience), builds more trust than any adjective.
Before and after
Here's a typical job post and what it looks like after applying the framework above.
Before
Frontend Developer
>
We are looking for a talented, self-motivated frontend developer to join our growing team. The ideal candidate will have 5+ years of experience with React, TypeScript, and modern web technologies. You should be comfortable working in a fast-paced environment, wearing many hats, and collaborating with cross-functional teams. Strong communication skills and attention to detail are a must. We offer competitive salary and benefits. Apply now!
After
Frontend engineer at Acme (8-person team, $110K-$145K, remote in EU time zones)
What you'll do in the first 90 days
Ship three features our customers have been asking for: bulk CSV import, a reporting dashboard, and email notifications. You'll own these end to end, from talking to users about what they need to deploying to production. By month three, you'll have direct relationships with a dozen customers and strong opinions about where the product should go next.
What you need to already know
- React and TypeScript (our entire frontend) - How to write code other people can read and maintain - How to ship without waiting for permission
What you'll learn here
How to build a product from 200 users to 2,000. How to make technical decisions when there's no architect to ask. How customer feedback turns into a roadmap when the team is small enough to move in a day.
What it's like here
Eight people, all remote, mostly EU time zones. Slack is our office. Monday all-hands, no other standing meetings. Both founders are engineers and review PRs alongside everyone else. We work normal hours and don't pretend crunch culture is a badge of honor.
What we're offering
$30K-$45K depending on experience. 0.2-0.5% equity. 28 days PTO. Home office budget. No whiteboard interviews; you'll do a paid take-home project instead.
The second version is longer, but candidates read every word. Because every word tells them something about the role, the team, and whether this is the right fit. The first version? They've seen it 50 times today. It blends into the noise.
Where the job post lives matters
You can write the best job post in the world, and it won't help if it lives in a Google Form linked from a tweet. The container shapes perception. A candidate clicking a bare Google Form link thinks "side project." A candidate landing on a branded careers page with your logo, a company description, and a clean application form thinks "real company that takes hiring seriously."
This matters more for small companies than big ones. Google doesn't need a careers page to attract applicants. You do. Your careers page is often the only impression a candidate has of your company before deciding to apply. It's doing the work of your brand, your office, and your recruiter all at once.
You don't need a designer or a developer to set this up. A careers page with custom application forms, your branding, and a real domain takes about 15 minutes to create in Bringboard. Candidates apply through the page, and their applications flow straight into your pipeline with the data you asked for. No more parsing emails, no more shared inboxes, no more "did anyone reply to that applicant from Tuesday?"
Your job post deserves better than a Google Form. Set up a branded careers page with custom application forms in 15 minutes. Free during beta.
Head of Content at Bringboard
Recruited for three startups before any of them had an ATS. Spent too many hours wrangling spreadsheets, chasing scheduling emails, and explaining to founders why "just post it on LinkedIn" isn't a hiring strategy. Now writes about what growing teams get wrong about hiring, and how to fix it without buying software built for Fortune 500 companies.