Business Analyst Job Description Template

In plain language: States the official job title, the department the role sits within, and the employment classification (full-time, part-time, or contract).

Common mistake: Using an informal working title instead of the title that will appear on the employment contract and payroll records — mismatches between documents create confusion during onboarding and performance reviews.

In plain language: A 3–5 sentence overview of the role's purpose, the problems it solves, and how it fits within the organization's broader goals.

Common mistake: Writing a role summary that reads like a marketing tagline rather than a functional description — vague language like 'drive synergies' tells candidates and hiring managers nothing concrete about what the role actually does.

In plain language: Identifies the direct manager and any dotted-line relationships, clarifying the chain of authority and collaboration expectations.

Common mistake: Omitting dotted-line or matrix reporting relationships — in matrixed organizations, an undocumented secondary reporting line creates authority disputes and performance review gaps.

In plain language: An itemized list of the primary tasks the employee is expected to perform on a recurring basis, written with enough specificity to support performance evaluation.

Common mistake: Listing 15 or more bullet points without grouping or prioritizing — a candidate cannot tell what the role actually focuses on, and a manager cannot use the list for performance evaluation.

In plain language: Minimum education, certifications, years of experience, and domain knowledge the candidate must have to be considered for the role.

Common mistake: Setting years-of-experience thresholds that screen out qualified candidates — requiring '5 years of experience' for a role that genuinely needs 2 years creates unnecessary recruiting friction and may raise adverse impact concerns under equal employment law.

In plain language: Nice-to-have skills, certifications, or domain experience that would make a candidate more competitive but are not mandatory for the role.

Common mistake: Blurring required and preferred qualifications into a single undifferentiated list — candidates cannot assess their fit, and recruiters cannot filter applicants consistently.

In plain language: States the salary band or hourly rate, bonus eligibility, and a reference to the company's standard benefits package.

Common mistake: Omitting the salary range entirely in jurisdictions that now legally require pay transparency — Colorado, California, New York, and Washington state mandate salary ranges in job postings; non-compliance draws regulatory penalties.

In plain language: Describes the physical or remote work environment, travel requirements, standard working hours, and any physical demands of the role.

Common mistake: Leaving working conditions vague at the time of hire and then mandating return-to-office later — without a documented baseline, changes to work location can trigger constructive dismissal claims in Canada and the UK.

In plain language: Affirms the employer's commitment to non-discriminatory hiring under applicable federal, state, or provincial law.

Common mistake: Using a boilerplate EEO statement that doesn't include all protected classes required by the applicable jurisdiction — state and provincial laws often extend beyond federal minimums, and an outdated statement can create compliance exposure.

In plain language: Provides a signature line for the hiring manager and, where used as a Schedule of Duties attached to an employment contract, for the employee — confirming they have reviewed and understood the role.

Common mistake: Treating the job description as an informal document that doesn't require a signature — when attached to an employment contract as a Schedule of Duties, an unsigned exhibit weakens the enforceability of IP assignment and non-compete clauses that reference the role scope.

A business analyst job description is a formal document that defines the responsibilities, qualifications, reporting structure, and working conditions of a business analyst role. It serves as both a recruitment tool and a legal reference document when attached to an employment contract as a Schedule of Duties. A well-written job description also provides the baseline for performance reviews, compensation benchmarking, and role-change documentation.

Core business analyst responsibilities typically include eliciting and documenting business requirements through stakeholder interviews and workshops, analyzing current-state processes and identifying gaps, producing business requirements documents (BRDs), user stories, and process maps, tracking project progress against defined KPIs, and serving as the communication bridge between business stakeholders and technical teams. The specific balance of these responsibilities varies significantly by industry, seniority level, and whether the role is embedded in an agile or waterfall environment.

Standard required qualifications include a bachelor's degree in business, computer science, or a related field, 2–5 years of relevant BA experience (depending on seniority), proficiency in requirements documentation tools such as JIRA or Confluence, and experience with at least one delivery methodology (Agile or Waterfall). Preferred qualifications often include CBAP or CCBA certification from the IIBA, domain expertise in the employer's industry, and familiarity with specific platforms like Salesforce, SAP, or SQL. Avoid requiring certifications as mandatory unless the role genuinely needs them — it narrows the candidate pool without improving hire quality.

A standalone job description used only for recruitment does not typically require a signature. However, when a job description is attached to an employment contract as a Schedule of Duties — which is common practice for roles with IP assignment or non-compete obligations — both the hiring manager and the employee should sign it before the start date. An unsigned exhibit weakens the enforceability of any contract clause that references the scope of the role.

In an increasing number of jurisdictions, yes — legally. Colorado, California, New York, and Washington state require salary ranges in job postings, including remote roles visible to residents of those states. Even where not legally required, including a salary range reduces time-to-fill by aligning candidate expectations early and avoids late-stage offer rejections. Always confirm the applicable pay transparency requirements before publishing any posting.

A job description defines what the role entails — duties, qualifications, and working conditions. An employment contract is the binding legal agreement that governs the employment relationship — covering compensation, IP assignment, confidentiality, non-compete, termination, and severance. The two documents work together: the employment contract typically incorporates the job description by reference as a Schedule of Duties. A job description alone creates no enforceable employment obligation.

Review the job description annually at minimum, and update it immediately whenever the role changes materially — for example, if the BA takes on direct reports, moves from waterfall to agile delivery, or gains access to a new category of confidential data. Each update should be dated, stored in the employee's personnel file, and acknowledged in writing by the employee. An outdated job description undermines performance reviews and compensation benchmarking.

With modifications, yes — but the document must be carefully adapted. A contractor engagement should remove references to benefits, employment classification, and at-will or notice-period termination terms. The scope-of-work section from the job description can inform the Independent Contractor Agreement's Statement of Work. Avoid language that implies an employment relationship (set hours, direct supervision, exclusive availability) as this can contribute to worker misclassification findings in the US, Canada, and the UK.

Technical skills commonly listed include proficiency in requirements management tools (JIRA, Confluence, Azure DevOps), process modeling (Visio, Lucidchart, BPMN notation), data analysis (SQL, Excel, Tableau, Power BI), and familiarity with ERP or CRM platforms relevant to the business. Soft skills worth specifying include structured communication with non-technical stakeholders, facilitation of workshops and requirements sessions, and the ability to translate ambiguous business needs into precise technical specifications. Tailor the list to the tools actually used in your environment rather than listing every possible BA tool.