Business Analyst
What the work looks like, the contexts behind the title, what each level means and the training that helps, then how interviews run and how to prepare for each step.
What a business analyst actually does
An analyst who turns business needs into clear requirements that technical teams can build and test, and who knows the processes behind them.
A business analyst helps business teams and technical teams understand each other. They run workshops, map the current processes, find what needs to change and write clear requirements or user stories.
They often support the testing, prepare user acceptance tests with business users and check that the delivered solution meets the need. Some business analysts use SQL to check data, or process mining tools such as Celonis to study processes.
Business analysts work in consulting firms, in IT services companies and in the IT teams of large companies, on ERP, CRM, data or custom software projects.
- A workshop with business users on a process
- Writing requirements or user stories
- Answering questions from developers
- Preparing user acceptance tests
- Checking data with SQL queries
The same title, very different contexts
Most business analysis searches are defined first by the type of project, then by the ground every business analyst shares.
What each level means in practice
Titles vary from one company to the next. What changes from one level to the next is the scope you own and the decisions you take.
- Works on a project with a senior analyst
- Learns the business, the processes and the tools
- Writes requirements with review
- Owns the requirements of a project on their own
- Runs workshops with business users
- Supports testing and the go-live
- Leads analysis on large projects
- Manages several analysts or business areas
- Shapes the solution with architects
- Leads business analysis across projects
- Sets the methods and the standards
- Advises leadership on processes and systems
The paths into the role, and what really counts
Companies look first at requirements you wrote and processes you understood. Education and certifications help most early in a career, or to change field.
- Business school or university degreeA common path for business analysts who work closely with business teams.
- Engineering school or master's in ITA common path in France, often valued for technical projects.
- Business user firstMany business analysts start in finance, logistics or sales before moving to IT projects.
- Graduate programs in consultingConsulting firms recruit young graduates as junior business analysts.
Our view: for this role, requirements you wrote and can walk through, from the workshop to the test, often say more than any certificate.
A conversation with a senior tech recruiter
Your first interview is with one of our senior tech recruiters, who knows the role, the methods and the levels in this guide. The conversation covers your own work through real examples, and the case studies come later, with the company. Before the call, we send you the six themes we will cover so you can prepare your examples.
- What you owned yourselfThe requirements, processes or projects you were responsible for, and your own part in the team's work.
- Your environment and its constraintsBusiness needs, existing systems, deadlines or the people involved: what shaped your technical choices.
- The decisions you madeHow you captured the need, which solution you supported and why, the options you compared and the reasons for your choice.
- The impact of your workWhat changed thanks to your work, with numbers when you have them: time saved, errors removed, adoption or test results.
- How you work with other teamsYour work with business users, developers, testers and project managers, and how you settle a disagreement.
- What you want nextThe kind of projects, domain and scope you are looking for in your next role.
- Clear requirements
- Process understanding
- Bridge between business and IT
The same ground for every candidate. For a given role, every candidate answers the same final questions, built with the hiring manager around what the role really needs.
Ready for the next steps. After our call, we tell you how the company runs its interviews, who you will meet at each step and what each step is meant to assess.
What the company will assess, step by step
Each company runs its own process, and we walk you through its steps before you start. Business analysis processes often combine the steps below, and the depth expected at each step grows with your level.
- A case studyA business need to analyse, with the questions you would ask and the requirements you would write.
- A requirements exerciseUser stories or a process map to write from a short description, live or as a take‑home.
- A deep dive on a past projectOne project you worked on, discussed in depth: the need, your requirements and the result.
- Meeting the manager and the teamHow you work, how you take decisions with others and what the team expects in your first months.
- Senior ConsultantYou ask the right questions, write clear requirements and explain them in simple words.
- ManagerYou lead the analysis, connect the need to the process and point out gaps and risks before you are asked.
- DirectorYou run most of the interview as a peer, think about several processes and connect them to the goals of the company.
How to prepare as a business analyst
Practical advice for each step of a business analysis process, from the way you introduce yourself to the questions you ask at the end of each interview.
Start with the projects and processes you worked on, their context and your part in them. Mention your main methods and tools in one sentence, then close with what you want next.
For each one, prepare the context, the constraints, your decision, the options you set aside, the result and what you would change today. Say "we" for the team and "I" for your own part.
In a case study, ask who the users are, what the process is today and what success looks like before you write anything.
Prepare one real requirement or user story you wrote, anonymised, and explain why you wrote it that way.
Prepare one example where you explained a business need to developers, or a technical limit to business users.
Rules on AI tools differ from one company to the next, especially for take‑home cases. Ask before each step, and when they are allowed, explain what you asked the tool and how you checked its output.
- Walk us through a project where you wrote the requirements.
- How do you run a workshop with business users?
- How do you handle conflicting needs from two teams?
- How do you check that the delivered solution meets the need?
- Which projects and business areas would I work on?
- How do business analysts and product owners share the work?
- Which methods and tools does the team use?
- How are business users involved in testing?
- How is the work of a business analyst reviewed?
- How does the team use AI tools in its daily work?
Where business analysts come from, and where they go
The roles people most often hold before this one, and the ones they most often move to.
Many business analysts also start as business users, data analysts or testers.