Career path
Business Analyst
A business analyst bridges the gap between a business problem and a workable solution — usually a software or process change. They figure out what's actually needed, capture it clearly, and make sure what gets built solves the real problem.
What the job actually is
You translate fuzzy business needs into clear, agreed requirements. That means interviewing stakeholders, mapping current and future processes, and documenting requirements precisely enough that a delivery team can build the right thing. The hard part is uncovering what people really need versus what they first asked for, and getting everyone to agree.
A typical day
Workshops and interviews with stakeholders, mapping processes, writing requirements or user stories, and acting as the go-between for the business and a technical team. You'll spend time resolving conflicting needs, clarifying scope, and validating that what's being built matches what was agreed.
Skills that matter
- Elicitation — drawing out real needs through good questions.
- Process modelling — mapping how work flows, today and tomorrow.
- Clear documentation — unambiguous requirements and user stories.
- Stakeholder facilitation — aligning people who disagree.
- Analytical thinking — breaking a vague problem into parts.
How to switch in
Business analysts often emerge from operations, customer support, or being a domain expert in a particular function — anyone who deeply understands how a business actually works. Domain knowledge is a genuine asset here. Start by volunteering for a process-improvement or systems project in your current role to build evidence you can do the work.
Frequently asked questions
Is business analyst a technical role?
It sits between business and technical teams, so some technical literacy helps, but you don't usually write code. The core skills are communication, requirements-gathering, and process analysis — strong domain knowledge often matters more than coding.