← All hiring guides
Supply Chain Analyst

How to Write a Supply Chain Analyst Job Description

A supply chain analyst job posting needs to screen for data-driven cost and efficiency improvements across the supply chain — 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 supply chain analyst candidate has to demonstrate: data-driven cost and efficiency improvements across the supply chain. 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:

  • Demand forecasting
  • Inventory optimization
  • ERP systems (SAP/Oracle)
  • Data analysis (Excel/SQL)
  • Vendor performance tracking

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:

  • Six Sigma certification
  • Power BI/Tableau
  • Procurement experience

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:

  • Reduced excess inventory carrying cost by $180K annually by rebuilding the demand-forecasting model
  • Identified a vendor lead-time inconsistency that was causing stockouts, cutting stockout incidents by 25% after renegotiation
  • Built a supply-chain KPI dashboard in Power BI adopted by 3 regional teams for weekly reporting

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 supply chain 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 supply chain 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.