Job description template
A complete business analyst JD — requirements, documentation, process and UAT — written so it does not collide with your data analyst role or quietly become a project manager posting.
Business analyst is the most title-ambiguous role in Indian hiring. The same two words describe a requirements specialist in an IT services engagement, a process owner in a bank's operations team, an almost-product-manager in a startup, and — frequently and wrongly — a SQL-and-dashboards role that should have been advertised as data analyst. The template below commits to one definition: the person who turns what the business needs into something engineering can build and the business will accept. If that is not the job you are filling, use a different template rather than bending this one.
Replace everything in [square brackets] before you post it.
Job title
Business Analyst
[Company name] operates in [industry/domain]. This role supports [business function or client engagement] and works with a delivery team of [size].
We are hiring a Business Analyst to own requirements for [product area / process / client engagement]. You will work with business stakeholders to understand what they need and why, document it in a form engineering can build against, map current and target processes, support delivery through clarification and change, and run user acceptance testing to sign-off. You are accountable for the requirement being right, not only for it being written down.
Experience: [x–y] years, with at least one full delivery cycle owned from requirement to production sign-off.
Location and work model: [city, office locality] — [on-site / hybrid / remote]. If the role requires client-site presence or overlap with a specific time zone, say so here.
Reports to: [Delivery Manager / Product Owner / Head of Business Systems]. Works with: [engineering team, QA, and the named business function].
Compensation: [band and structure, or a statement that it is benchmarked to experience and domain]. State the notice period you can accommodate — BA notice periods in Indian IT services are frequently long, and it affects your timeline.
To apply: send your resume to [email / apply link] with a short note on a requirement you got wrong and how you found out. Process: [n] rounds, including a case exercise on an ambiguous business problem.
The template is the easy half. These are the decisions that decide whether the posting works.
If your organisation is hiring both, write both JDs at the same time and read them side by side. The business analyst owns requirements, process and acceptance. The data analyst owns questions, metrics and evidence. The overlap is stakeholder communication and light SQL, and nothing else.
Where the boundary blurs — a BA who also builds the reports, a data analyst who also writes specs — say which is primary and give a rough proportion. Candidates from both sides will read it accurately, and your interview loop will finally be testing for one job instead of hedging between two.
Domain is the strongest predictor of a business analyst's ramp time in the Indian market, because the job is largely about understanding a business well enough to specify it. A lending BA who knows what a moratorium does to an amortisation schedule is productive in weeks; the same person on a hospital information system is not, however good they are.
So state the domain, and then decide honestly whether it is a hard requirement or a strong preference. If you would hire a superb BA from an adjacent domain, say that in the JD — it widens a pipeline that is otherwise very narrow, and it is the single most common reason good BA searches stall.
Business analyst JDs accumulate delivery responsibilities during drafting: status reporting, timeline management, resource coordination, stakeholder updates. Individually each looks reasonable; collectively they turn the posting into a project manager role that does requirements on the side.
Keep the JD anchored on requirement quality and acceptance. If you genuinely need someone to run the plan as well, say so explicitly and adjust the band — but do not smuggle it in, because the BAs you want will read the drift and assume the requirements work is the part that gets squeezed.
Signals specific to business analyst applications — not generic screening advice.
Experienced BAs have all worked on a programme where the requirements were decorative. They screen for it.
Business analyst is the worst title in your requisition list for keyword matching, because the title is applied to at least four different jobs and because a large population of support, operations and MIS professionals carry it. Filtering on the title alone will bury the specialists you want.
Other roles, hiring guides and recruiter tooling.
Stack depth over stack breadth. The JD that attracts engineers who ship and filters out keyword collectors.
The role most often mis-scoped as a data scientist. Fix the scope and the pipeline fixes itself.
Lifecycle ownership, not talent acquisition with a bigger title. Scope it by headcount supported.
Six roles, each with its own screening guidance
The components a job offer letter usually carries, the difference between an offer letter and an appointment letter, and the omissions that cause offers to be declined or disputed later.
A working method for shortlisting at scale: build the scorecard first, run two passes, know which filters are real and which are proxies, and calibrate before you trust anyone's judgement
Score applications against your own job description
JD screening scores every application against your own job description and shows the requirement-level gaps behind the score.