EUROPE | UK | CANADA | AFRICA | UAE

1) In your opinion, what qualities should a good BA have?

This interview question is designed to test both the hard and soft skills on your CV. The interviewer is likely looking for an insight into your opinions on industry work ethic, that you are aware of current skills trends within the BA role and that you’ve read the job description and understood what this particular position requires.

​

To prepare, be sure to re-read the job description before your interview so you can match your skills to the answer. Don’t forget to include some of your own opinions in the mix, too! 

​

​

2) Can you tell me the difference between an SRS and a BRD?

This is a good example of technical business analyst interview questions that explores how well you understand jargon and how clearly you’re able to communicate technical concepts. Try to focus on the clear points of difference, such as the professionals in charge of creating each document (the systems architect and business analyst, respectively) and that the BRD is written according to client requirements, where the SRS Systems Requirement Specification (this consists of both the FUNCTIONAL & NON-FUNCTIONAL REQUIREMENT) is written according to the BRS (Business requirement Specification) or FSD (Functional Requirement Document).

​

​

3) How would you perform a Gap analysis?

In some cases, business analyst interview questions will be designed to determine your level of technical ability and your existing work processes. If they ask you to detail a process you use, try to remain concise and thorough, providing rationale for the steps you take. 

​

​

4) What is the best method for gathering requirements?

There is no best method for capturing requirements however, it all depend on the stakeholder needs during the stakeholder engagement. When they want to test how thorough you are, a potential employer could ask you to take them through your requirement gathering process. Be sure to cover each step thoroughly, including information gathering, planning, implementation and evaluation.

​

​

5) Can you tell us about a time you had to manage a difficult stakeholder?

This is a test of soft skills and is a very common interview question for business analyst jobs. Certain aspects of the role require you to work with other members of the business, which demands excellent communication and collaborative skills. Make use of the S= Situation, T=Task, A=Action, R=Result (STAR technique) to answer this question.

​

​

6) What would your process be for managing requirement changes?

Agility and the ability to work with resourcefulness and flexibility are key points of focus for most roles in the current hiring landscape. In this case, your logical thinking is also being tested. If you want to impress, try detailing how you’d prioritise the changes, the scope and impact they’ll have on the project and any gaps they leave which need to be covered off. 

​

​

7) How would you explain the Scrum methodology to someone without technical knowledge?

It’s important for a business analyst to be able to explain technical concepts to both technical and non-technical professionals. Questions like this will test how well you communicate complex ideas and processes and whether you can avoid jargon in your answer. 

​

​

8) What project methodology do you prefer and why?

Questions like this will test how well you communicate complex ideas and processes and whether you can avoid jargon in your answer. Also the interviewer wants to test if you have experience delivering projects within Agile and or waterfall environments.

​

9) Tell me a bit about yourself?

This question is what interviewers call "THE GIVE AWAY QUESTION". This is so because this questions tells a whole lot about the candidate. You are to speak for no less than 2 minute and discuss briefly on this question to provide vague answers but at the same time, communicate fluently and concisely.

​

​

10) On your most relevant role, what was the project about?

In this question, the candidate is to be very specific, talk about the objectives of the entire project BUT DOES NOT  give specific details yet about the project.

​

​

11) What were your roles and responsibilities OR What were your day to- day activities on your project?

In this question, this is where the BA has the chance to excel, shine, discuss all about who and what a BA is about.

​

If the candidates answers this question properly, and covers areas such as, types of requirements with examples, documentations produced, stakeholder management, requirement meeting facilitation, tools used (JIRA, MS Visio etc), Process flow maps, user Stories/ Acceptance Criteria if its an Agile project, daily stand ups, sprint planning, product backlog grooming, showcases, demos, retrospectives, Testing triage etc. The interviewer will be so impressed and will have no further question to ask the candidate any further.