1. Tell me something about yourself.
2. Tell me about your responsibilities in your last project.
3. How did your typical day look like.
4. Tell me something about each of your last three projects. What was the project about?
5. Are you a leader or a follower? Have you worked with junior BA's under you? How was
the responsibilities divided among the team of BA's?
6. Whats your experience with Software Development Methodologies? We work mostly
on the waterfall methodology which is typically of a 3 month iteration. Will you be
comfortable with it? Relate your experience with the waterfall methodology.
7. Have you been in a situation where the users dont give you time for requirement
collection, whats your reaction to this situation, relate it with the experience you have
had in past.
8. How do you go ahead with requirement gathering, what are the sources you use?
9. What are some of the documents you have prepared?
10. What tools do you use for document preparation?
11. How did you prepare your user case story?
12. What is the difference between Activity diagram and Sequence Diagram?
13. Have you been involved in preparation of wireframes? What is a wireframe according
to you? What tools do you use for preparation of wireframes?
14. Have you been in a situation where your technical team could not understand the
wireframe? How did you handle it?
15. What application where you using for issue tracking?
16. Have you worked with the business users or with the technology team? How confident
are you with either?
17. What are your technological strength? HAve you worked with UI teams? What was
your responsibilities?
18. How strong are you with the understanding of Webservices? What webserice calls are
you familiar with? What was your role with webserices, As a BA how were you involved
in the process?
19. Have you worked on Project Traceability Matrix? What is Project Tracebility Matrix
used for? What tool did you use for creating the matrix?
20. Have you conducted presentations for Business users and the management? How
comfortable are you with it?
21. How strong are you with SQL? Can you work with complex SQL queries?
22. Have you been involved in Data Mapping? What tools you use for it?
23. Have you been in a situation where you had to say NO to a requirement to a business
User? Please explain the situation, and How did you go ahead with it?
24. Have you been in a situation when two managers at the same level has come with two
extremely contradicting requirements? Please explain the situation, and How did you
handle this situation?
25. As I have already mentioned we run iterations for 3 months, and at the end of the
iteration we do the testing. Have you been involved in testing? What have been your
responsibility and roles?
26. At the end of the project, was there any case when the user might have come up and
said this is not what I desired from the system? (In other words, they expected more
from the system.) How did you handle that? Did you enhance the requirements and re-
released the product?
27. What are your expectations from this new role?
28. Do you have any questions for me?
Introductory Questions:
Why did you decide to become an Analyst?
How comfortable are you with Waterfall?
Tell us about your experiences writing BRDs, SRSs etc.
What are the methods that you have used to gather requirements? Which method as per
you is the best/most effective? (Note: This is a trick question. The best method depends on
various factors. Overall, the most recommended approach is face-to-face meetings and the
like.)
What are the responsibilities that you have in your current project? What does a typical
workday look like?
Resume Based Questions:
Interviewers then go over your resume, project-by-project for at least 3 or 4 of
your previous projects and ask questionsabout them. For eg. In xyz project, what did you
do? What was the application all about? What was your exact role?
Scenario based questions:
Interviewer says: "In the following questions, we want you to answer based on a situation in your career(what
you DID) and NOTa philosophical answer(what you WOULD DO). Please be patient with us, but if we feel like
you are moving toward a more philosophical answer we will interrupt and try and pull you back to a more
specific, scenario based answer."
Explain a scenario in which you had a dependency on someone/team member to finish his
work before you could start yours. How did you follow up on it? What was the result?
Explain a scenario in which you had a conflict with a co-worker. How did you resolve it?
What was the outcome?
Explain a scenario in which a peer needed help. How did you help him? What was the
result?
Very Important: Explain a scenario where you have worked on an application with
multiple touch points(lots of interactions and transactions, meaning if one enhancement is
made there are multiple side effects within the application). What were your experiences
with such an application? What according to you are the best practices for SDLC in such
applications?
Explain a scenario in which after gathering requirements, the stakeholders change their
asks. How did you handle this change? Did you accept it? What was the result? (Note: Not
all change requests can be accepted without consequences to capacity and deliverables)
Closing Questions:
What do you think is more important: Work experience or being a team player who gets
along with the rest of the team?
How will you get to know the members of the team once you join a new project?