How to Write a Business Analyst Job Description
A business analyst job posting needs to screen for requirements clarity and measurable process improvement, not just documentation — not just list duties. Here's what to include and what actually filters for the right candidates.
What this role actually needs to prove out
Before writing requirements, get clear on the one thing a strong business analyst candidate has to demonstrate: requirements clarity and measurable process improvement, not just documentation. Every requirement you list should trace back to that, not to a generic template for the job title. A posting that just restates the job title in bullet-point form filters for nothing — it neither attracts strong candidates nor repels weak ones.
Must-have requirements to include
Keep this list short and real — these are the skills that actually predict success in the role, not a wish list:
- Requirements gathering
- Process mapping
- Stakeholder management
- Data analysis
- SQL
Nice-to-have — list separately, don't gate on these
Worth calling out as a plus, but requiring them as "must-haves" needlessly shrinks your pool:
- Agile/Scrum experience
- Tableau or Power BI
- Six Sigma certification
What a strong candidate's resume bullet looks like
Useful as a benchmark when screening — this is roughly what real, specific evidence of the role's core skill looks like on paper:
- Led requirements gathering for a cross-functional process redesign, reducing average order-processing time by 22%
- Built a stakeholder-aligned process map that cut a 6-step approval workflow down to 3 steps
- Delivered data analysis that informed a $500K budget reallocation decision for the operations team
Mistakes that scare off good candidates
- Requiring years of experience as a proxy for skill (e.g. gating on "5+ years" when the real bar is demonstrated competence) — filters out strong candidates with less conventional paths.
- Listing every tool/skill your team has ever touched as a "must-have," rather than the handful that actually predict success.
- Burying the actual role and responsibilities under generic company boilerplate that could apply to any posting.
Frequently asked questions
What should I put at the top of a business analyst job posting?
A short intro (1-2 sentences) on the role and team, then straight into responsibilities and requirements. Candidates skim the first few lines to decide whether to keep reading — don't bury the actual role behind company boilerplate.
How many requirements should a business analyst job description list?
Split them into must-have (5 or fewer — every extra must-have measurably shrinks your applicant pool) and nice-to-have. A JD that lists 15 "requirements" with no distinction screens out strong candidates who'd have been a genuinely good fit.
Should I list a salary range?
Where legally required or common in your market, yes — it's increasingly expected, and its absence is one of the top reasons strong candidates skip an otherwise good posting without applying.