Business Analyst Job Description: What BAs Actually Do

What a business analyst does day-to-day, the responsibilities employers list, how the role varies by seniority and industry, and what skills actually matter.

Start Free BA Training →

What Is a Business Analyst?

A business analyst is the person in an organisation who figures out what needs to change, and makes sure that what gets built or implemented actually solves the right problem. They sit between the business — the people with the problem and the requirements — and the delivery team — the people who design, build, and implement solutions.

The core value of a BA is translation and clarity. Business stakeholders often can’t articulate requirements in a form that’s useful to developers. Developers often can’t communicate technical constraints in a way business stakeholders understand. The BA bridges that gap — eliciting, clarifying, documenting, and managing requirements across the project lifecycle.

Business Analyst Responsibilities

A typical BA job description will list some or all of the following:

Requirements Elicitation

Gathering requirements from stakeholders through interviews, workshops, surveys, observation, and document analysis. This is the foundational BA skill — understanding not just what stakeholders say they want, but what they actually need and why.

Requirements Documentation

Translating elicited requirements into clear, unambiguous documents that delivery teams can act on. Formats vary by methodology: Business Requirements Documents (BRDs) in waterfall, user stories and acceptance criteria in Agile, use cases for complex system interactions, and process maps for workflow requirements.

Stakeholder Management

Identifying all stakeholders affected by a change, understanding their interests and concerns, managing competing requirements, and maintaining ongoing communication throughout the project. In large organisations, stakeholder management is often as complex and time-consuming as the requirements work itself.

Process Analysis and Mapping

Documenting current-state (‘as-is’) processes, identifying pain points and inefficiencies, and designing improved future-state (‘to-be’) processes. Tools: swimlane diagrams, BPMN models, value stream maps, and gap analysis frameworks.

Facilitating Workshops

Running structured sessions — requirements workshops, process walkthroughs, design reviews, retrospectives — with groups of stakeholders and team members. Effective workshop facilitation is one of the most valued and least taught BA skills.

UAT Support

Helping to define acceptance criteria, preparing UAT scenarios, coordinating user acceptance testing with business stakeholders, and managing defects and feedback from UAT back into the delivery process.

Change Impact Analysis

Assessing how a proposed change affects people, processes, systems, and data across the organisation. Feeding this analysis into change management and communication planning.

BA Responsibilities by Seniority

• Junior / Graduate BA: Documents requirements under supervision, supports workshop facilitation, assists with UAT coordination, maintains project documentation. Focuses on learning core techniques and building stakeholder relationships.
• Business Analyst (mid-level): Independently runs elicitation sessions, writes requirements documents, facilitates workshops, manages stakeholder communication on project workstreams. Leads the BA contribution to one or more projects concurrently.
• Senior Business Analyst: Leads requirements across complex, multi-workstream programmes. Mentors junior BAs. Engages with senior stakeholders and executive sponsors. Often involved in solution design and architecture review.
• Lead / Principal BA: Sets the requirements approach for large programmes. Builds and manages BA capability. Contributes to enterprise architecture and strategy. May manage a team of BAs or operate as a subject matter expert across the organisation.

How the BA Role Varies by Industry

Financial Services

BAs in banking, insurance, and financial services deal with complex regulatory requirements, large legacy system landscapes, and high-volume data. Requirements documentation is often more formal and detailed than in other sectors. Domain knowledge (credit, payments, compliance) is highly valued at senior levels.

Government and Public Sector

Government BA work involves large programmes with many stakeholders, strong documentation requirements, and complex approval processes. Policy context matters — BAs need to understand how legislation and policy shape requirements. Change management is often as important as requirements management.

Technology and Product Companies

Product-focused organisations often blend the BA and Product Owner roles. Requirements are managed as user stories and product backlogs. The pace is faster, documentation is leaner, and BAs work closely with UX designers and engineers. Agile fluency is essential.

Healthcare

Healthcare BA work involves clinical systems, complex patient workflows, and significant regulatory compliance (privacy, safety, clinical governance). Domain knowledge of clinical environments is a strong differentiator. Projects often have high stakes and long delivery timelines.

What a BA Does Not Do

Common misconceptions about the BA role:

• BAs don’t manage projects — scope, timeline, and budget management sit with the Project Manager. BAs manage requirements, not projects.
• BAs don’t write code — the BA defines what needs to be built; developers build it. Some BAs have technical backgrounds and can read or write code, but it’s not a role requirement.
• BAs don’t make business decisions — the BA surfaces and clarifies decision points for stakeholders to resolve. They facilitate good decisions, not make them.
• BAs don’t just take notes in meetings — meeting notes are a small part of BA work. The core is analytical: understanding complex problems, identifying requirements gaps, and ensuring solutions address root causes.

Frequently Asked Questions

What does a business analyst do day to day?

A typical BA day includes: stakeholder conversations and interviews, writing or refining requirements documents, reviewing user stories with the delivery team, facilitating or preparing for workshops, resolving requirements ambiguities raised by developers, and updating project documentation. The specific mix shifts by project phase — heavier on stakeholder work early, heavier on review and UAT support later.

What is the difference between a business analyst and a project manager?

The Project Manager owns the delivery: schedule, budget, resources, risk, and issue management. The Business Analyst owns the requirements: what needs to be built, why, and to what standard. On large projects, both roles are critical and work closely together. On smaller projects, one person sometimes covers both — but this is a significant workload.

Is business analysis a good career?

Business analysis is one of the most consistently in-demand roles in technology and enterprise organisations. It’s accessible from a wide range of backgrounds, offers clear career progression, and provides competitive salaries. The role is also relatively resilient to automation — it fundamentally requires human judgment, stakeholder empathy, and communication skills that are difficult to replicate.

Further reading: Business Analyst Career Path | BA Soft Skills Guide | BA Interview Questions | Entry-Level BA Jobs

Real BA Job Advertisement Example (Seek-Ready Template)

To understand what employers genuinely want, nothing beats seeing a complete, realistic job advertisement. Below is a sample BA job ad written to the standard you’d find on Seek or LinkedIn — use it as a template when writing your own applications or when your organisation needs to hire a BA.

BA Responsibilities by Seniority Level

One of the most common misconceptions about business analyst job descriptions is treating all BA roles as equivalent. In practice, responsibilities differ significantly between junior, mid-level, senior, and lead BAs. Here is how the role evolves across the career ladder:

What Employers Actually Look For: Analysis of 50+ BA Job Ads

Rather than guessing what skills matter, we analysed more than 50 BA job advertisements posted on Seek and LinkedIn across Australia and New Zealand in 2024–2025. The patterns are striking — and quite different from what most BA training programmes emphasise.

• Jira — mentioned in 78% of ads. Not just ‘exposure’ — employers want demonstrated proficiency in backlog management, story creation and sprint tracking.
• Agile/Scrum experience — required in 67% of ads. Most employers now assume agile is the default delivery methodology.
• Stakeholder management — referenced in 61% of ads as a specific competency, not just a soft skill.
• SQL or data literacy — specified in 41% of ads, particularly in financial services, insurance and government.
• BABOK knowledge — mentioned in 34% of ads, almost always in government, consulting or large enterprise roles.
• Process mapping (BPMN/Visio) — required in 48% of ads, often alongside requirements documentation.
• UAT coordination — listed as a responsibility in 55% of ads — BAs are expected to lead user acceptance testing, not just observe.
• Confluence — mentioned alongside Jira in 59% of ads; often treated as a paired skill.
• Certification (CBBA/ECBA/CBAP) — listed as ‘advantageous’ in 31% of ads, essential in only 9% — but it consistently differentiates candidates in shortlisting.

The takeaway: practical tool proficiency (Jira, Confluence, SQL basics) combined with genuine stakeholder facilitation experience outweighs academic knowledge of frameworks alone. If you are building your BA skills profile, prioritise these high-frequency requirements first.

Red Flags in BA Job Ads: When ‘BA’ Means Something Else

Not every job advertised as a ‘Business Analyst’ is a true BA role. Misrepresented BA jobs are surprisingly common — particularly in SMEs and non-tech industries. Here is how to spot a job description that misuses the BA title:

• ‘Administrative support’ buried in responsibilities — If more than two bullet points reference filing, scheduling, inbox management or minute-taking, this is an office coordinator role dressed up as a BA.
• No mention of requirements, analysis or stakeholders — A genuine BA job ad will always reference requirements elicitation, stakeholder engagement or process improvement. Absence of these signals is a red flag.
• ‘Business development’ conflated with ‘business analysis’ — Some organisations confuse the two. Watch for references to sales targets, client acquisition or revenue generation — these are sales roles.
• Data entry presented as ‘data analysis’ — ‘Analysing reports’ in a BA ad often means updating spreadsheets, not conducting genuine analysis.
• IT helpdesk work labelled as BA — If the role includes ‘logging support tickets’ or ‘troubleshooting user issues’ as primary duties, it is likely a systems support role.
• Salary significantly below market — Mid-level BA roles in Australia pay $85,000–$115,000. Ads offering $55,000–$65,000 for a ‘Business Analyst’ are almost always misclassified roles. Check current BA salary benchmarks before applying.

How to Tailor Your Resume to a BA Job Description

Once you have identified a genuine BA role worth pursuing, the difference between a shortlisted and rejected application usually comes down to how well your resume mirrors the language and priorities of that specific job description. Here is a practical approach:

• Extract the top 8–10 keywords from the job ad — look for repeated terms, skills listed under ‘essential’ and nouns in the responsibilities section (e.g., ‘requirements elicitation’, ‘UAT’, ‘Confluence’, ‘backlog refinement’).
• Use the same terminology — if the ad says ‘acceptance criteria’, use that phrase, not ‘success conditions’ or ‘test criteria’. ATS systems match exact phrases before human reviewers see your application.
• Lead with a tailored summary — your top three to four lines should directly address the role’s primary needs. If the ad emphasises agile delivery, your summary should open with your agile BA experience.
• Quantify your impact — ‘improved process efficiency’ is weak; ‘reduced loan approval cycle time from 14 days to 6 days by redesigning the credit assessment workflow’ is compelling.
• Mirror the seniority signals — if the ad lists ‘lead workshops’ and ‘mentor junior analysts’, reflect back leadership language in your experience bullets, not just task completion.
• Address the industry context — if it is a financial services BA role, lead with your fintech or banking project experience, even if your broader background is mixed.

Explore the full BA career path to understand how to position your experience at each level, and visit free BA training to sharpen your skills before applying.

{“@context”: “https://schema.org”, “@type”: “FAQPage”, “mainEntity”: [{“@type”: “Question”, “name”: “What should a business analyst job description include?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “A complete BA job description should include: job title and seniority level, a brief company and project overview, a detailed list of day-to-day responsibilities (10–15 bullet points), required qualifications and experience, desirable skills and certifications, the tools and methodologies used (e.g., Jira, BPMN, agile), and the salary range. Omitting salary ranges increasingly deters strong candidates.”}}, {“@type”: “Question”, “name”: “What is the difference between a junior and senior BA job description?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Junior BA roles focus on documenting requirements under supervision, producing process maps and supporting workshops. Senior BA roles involve leading complex stakeholder engagement, producing business cases, mentoring junior analysts and owning the requirements strategy for entire programs. The stakeholder level also differs: junior BAs work with team members, while senior BAs engage directly with executives and external partners.”}}, {“@type”: “Question”, “name”: “How do I know if a BA job ad is legitimate?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “A legitimate BA job ad will explicitly mention requirements elicitation, stakeholder engagement, user stories, process mapping or business case development. It will list specific tools (Jira, Confluence, Visio) and specify industry experience. Red flags include vague responsibilities, salary well below market rates, conflation of BA with business development or administration, and no mention of analysis-specific deliverables.”}}, {“@type”: “Question”, “name”: “Do BA job descriptions require coding skills?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Most BA job descriptions do not require programming skills. However, data-focused roles increasingly request SQL literacy (reading and writing basic queries), and technical BA roles in API-heavy environments benefit from understanding REST concepts. Coding is not typically required, but data literacy — the ability to work with data, interpret reports and understand system integrations — appears in over 40% of BA job ads.”}}, {“@type”: “Question”, “name”: “What certifications appear most in BA job descriptions?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “CBBA (Certified Business and Business Analysis) is increasingly listed for entry-level and mid-level roles due to its practical focus and no-experience-required entry pathway. ECBA and CCBA (from IIBA) appear in mid-level ads. CBAP (Certified Business Analysis Professional) appears in senior roles, particularly in consulting, government and large enterprise. PMI-PBA appears in project-management-heavy environments. See the full BA certification comparison for details.”}}]}