The skills a business analyst needs, in the order worth learning them: what employers expect first, what to add next, and the tools you will work in.
Essential skills are the ones most employers look for before they look at anything else.
A sensible order for someone starting out. Skip ahead where you already have a skill.
Get comfortable with requirements gathering and documentation, process mapping and data analysis and SQL. Nearly every employer looks for these before anything else.
Add stakeholder management, agile and project methods and modelling notations. These turn a capable beginner into someone who can work with little supervision.
Choose a direction such as systems and technology analysis or process improvement and change, and add its skills: requirements, user stories and data analysis.
Use each skill on a small, real project or task as soon as you can. Evidence of use is worth more than a list of courses.
These decide how well the technical skills get used.
Names change with fashion and employer; what matters is understanding what each kind of tool is for.
Adding these opens the more specialised versions of the role.
Speed and accuracy with data underpins nearly every role in this group.
Understanding revenue, costs and cash in the organisation makes your recommendations credible.
Case-style and judgement questions reward a clear framework and calm reasoning.
Skills stick when you use them. Each of these gives you something real to show or talk about.
Map a process you know well, such as returning an item, and mark where it wastes time.
Write five requirements for a simple app and ask a friend to say what they would build from them.
Run a short workshop with friends on a problem and write up the decisions made.
List a skill next to the work that proves it. These are the ones a reader scanning for this role will look for first.
Requirements gathering and documentation is one of the first things most employers look for, alongside process mapping and data analysis and SQL. Show each with real work rather than only naming it.
listening and asking good questions, facilitating workshops and writing clearly come up most often. They decide how well the technical skills get used, and they are what interviewers test with questions about past situations.
Start with the essentials: requirements gathering and documentation, process mapping and data analysis and SQL. Once you are comfortable, add stakeholder management, agile and project methods and modelling notations. The specialist tracks, such as systems and technology analysis, come after that.
Process mapping tools, A requirements or backlog tool, Spreadsheets and SQL are typical for the role. Pick one in each category and learn it well; the ideas carry over when an employer uses a different product.
List a skill next to the work that proves it: what you did, at what scale and with what result. Put the most relevant skills near the top, using the words the job description uses, but only for skills you really have.
Upload your resume and the job description, and the AI interviewer builds its questions from both. Every answer is scored against the bar for the role, with notes on what to fix.