Business Analyst job description template (India, 2026)
A Business Analyst job description written for Indian companies: responsibilities, requirements, CTC and notice-period framing, five screening questions, and the full text to copy or post on ofper.
Last updated 3 September 2026. Competitor pricing and plan limits are re-verified against each vendor’s own pages.
What does a Business Analyst do?
The Business Analyst title covers two different jobs in India, and the posting should say which this is. In IT services it means requirements and documentation for client software projects. In a product or operating company it means analysing how the business works — order flow, onboarding, collections, support — finding where it breaks, and specifying the process or system change that fixes it, then testing that the fix worked. This template is written for the second.
The role sits between the people who do the work, the founder who wants it to improve, and whoever builds the solution — internal engineers, an ERP vendor, a no-code tool. The posting should state the domain, the systems in play, whether the role includes data analysis and testing, and who the analyst reports to.
Business Analyst responsibilities
Written as work the person does, not qualities they have. A responsibility a candidate can picture is one they can decide about.
- Gather requirements from the people who run each process — interviews, observation, data — and write them down so that both the business and the builders agree on them.
- Document current processes and the problems in them, with evidence, and design the future process with the stakeholders.
- Write specifications — user stories or functional specs — with acceptance criteria, edge cases and what is out of scope, for engineers, vendors or no-code tools.
- Analyse operational data to size problems, prioritise changes and measure whether a change worked.
- Coordinate delivery: clarify questions from builders, manage scope changes, and run user acceptance testing with the business.
- Configure or administer business systems — the ERP, the CRM, the helpdesk — where the change does not need engineering.
- Train users on new processes and systems, and write the documentation they will actually use.
- Report on the outcomes of changes against the original problem, and maintain the backlog of improvements.
Business Analyst requirements and qualifications
Keep the required list to what you would actually reject a candidate for. Everything else goes under nice to have — a long required list mostly filters out the people you wanted.
- Graduate, ideally with an MBA or an engineering degree, and 2 to 5 years as a business analyst, process analyst or operations analyst in an operating company or a product team.
- Evidence of a process or system change you specified that measurably improved something, with the number.
- Clear writing: specifications that builders rarely have to come back on, and process documents that users can follow.
- Comfortable with data — Excel or Sheets fluently, SQL or a BI tool a plus — to size problems and measure results.
- Familiarity with at least one business system — an ERP, a CRM, a helpdesk — as an administrator or power user.
- Diplomatic and persistent with stakeholders who disagree about how the work should be done.
Nice to have
- Experience in our domain — logistics, retail, healthcare, financial services — and its typical processes.
- Experience with no-code and automation tools, or with configuring an ERP.
- Experience running user acceptance testing and training for a system rollout.
Salary, CTC and terms for a Business Analyst in India
State a CTC range. Postings without one get fewer and worse-matched applications, and the range is the first thing an Indian candidate looks for. Say how the CTC is made up — fixed, variable, and any statutory components — so the in-hand figure is not a surprise at offer stage.
- State the CTC and its split. Business Analyst salaries in India differ sharply between IT-services and operating-company roles; state which this is so the range matches.
- State the domain, the systems and the reporting line — usually operations, product or the founder.
- State whether the role is in-office, hybrid or remote; process work needs time with the people who do it, and the posting should say how much.
- Notice period is typically 30 to 60 days.
Business Analyst job description template
Replace every [placeholder]. Cut anything that is not true of your company — a generic paragraph is worse than no paragraph.
Business Analyst — [Company name], [City] Employment type: Full-time | Location: [City] / [On-site, hybrid or remote] | CTC: [range] per annum | Experience: [years] About the role The Business Analyst title covers two different jobs in India, and the posting should say which this is. In IT services it means requirements and documentation for client software projects. In a product or operating company it means analysing how the business works — order flow, onboarding, collections, support — finding where it breaks, and specifying the process or system change that fixes it, then testing that the fix worked. This template is written for the second. The role sits between the people who do the work, the founder who wants it to improve, and whoever builds the solution — internal engineers, an ERP vendor, a no-code tool. The posting should state the domain, the systems in play, whether the role includes data analysis and testing, and who the analyst reports to. What you will do - Gather requirements from the people who run each process — interviews, observation, data — and write them down so that both the business and the builders agree on them. - Document current processes and the problems in them, with evidence, and design the future process with the stakeholders. - Write specifications — user stories or functional specs — with acceptance criteria, edge cases and what is out of scope, for engineers, vendors or no-code tools. - Analyse operational data to size problems, prioritise changes and measure whether a change worked. - Coordinate delivery: clarify questions from builders, manage scope changes, and run user acceptance testing with the business. - Configure or administer business systems — the ERP, the CRM, the helpdesk — where the change does not need engineering. - Train users on new processes and systems, and write the documentation they will actually use. - Report on the outcomes of changes against the original problem, and maintain the backlog of improvements. What we are looking for - Graduate, ideally with an MBA or an engineering degree, and 2 to 5 years as a business analyst, process analyst or operations analyst in an operating company or a product team. - Evidence of a process or system change you specified that measurably improved something, with the number. - Clear writing: specifications that builders rarely have to come back on, and process documents that users can follow. - Comfortable with data — Excel or Sheets fluently, SQL or a BI tool a plus — to size problems and measure results. - Familiarity with at least one business system — an ERP, a CRM, a helpdesk — as an administrator or power user. - Diplomatic and persistent with stakeholders who disagree about how the work should be done. Nice to have - Experience in our domain — logistics, retail, healthcare, financial services — and its typical processes. - Experience with no-code and automation tools, or with configuring an ERP. - Experience running user acceptance testing and training for a system rollout. Compensation and terms - State the CTC and its split. Business Analyst salaries in India differ sharply between IT-services and operating-company roles; state which this is so the range matches. - State the domain, the systems and the reporting line — usually operations, product or the founder. - State whether the role is in-office, hybrid or remote; process work needs time with the people who do it, and the posting should say how much. - Notice period is typically 30 to 60 days. How to apply Apply with your resume through this page. We reply to every application, and shortlisted candidates hear from us within [number] working days.
Opens a free ofper workspace with the title, description and screening questions filled in.
Screening questions for Business Analyst applicants
Five questions is the ceiling on ofper, and it is the right ceiling: a form that asks more than that costs applications. Use them for the things that decide a shortlist, not for anything the resume already says.
| Question | Type | Knockout | Why it earns a slot |
|---|---|---|---|
| Have you specified a process or system change that was implemented and measurably improved a business outcome? | Yes / No (pass: Yes) | Yes | Outcomes separate analysts who change things from those who document them. |
| How many years of business or process analysis experience do you have in an operating company or product team (not IT services delivery)? | Number (pass: 2+) | Yes | Distinguishes the two meanings of the title in India. |
| Have you administered or configured a business system — an ERP, CRM or helpdesk — yourself? | Yes / No (pass: Yes) | No | Not a knockout, but it decides how much the role can do without engineering. |
| What is your current notice period, in days? | Number (pass: 0 to 90) | No | Scheduling. |
Questions, answered straight
What should a Business Analyst job description include?
Which kind of business analyst this is — IT services requirements or operating-company process improvement — the domain, the systems, whether data analysis, configuration and testing are included, the reporting line, and the CTC. The two meanings of the title attract different candidates at different salaries.
Does a Business Analyst need an MBA?
No. It is common on applications and useful for the business framing, but evidence of a change specified and measured matters more. Engineers and operations people with analytical skills often make strong business analysts.
Business Analyst or Product Manager?
A Business Analyst improves how the business operates — processes and internal systems — and specifies changes for others to build or configure. A Product Manager owns what the company's product does for customers and its roadmap. In small companies the roles blur; state what the person will own.