Typically Jira or Azure DevOps for requirements and stories, Confluence or SharePoint for documentation, Visio, Lucidchart, or Miro for process models, and SQL plus something like Power BI or Tableau for data. The habit that matters more than any product is keeping requirements in one place that links to the build items, rather than in documents that quietly drift out of sync.
Why interviewers ask this
Interviewers ask partly to check tool familiarity against their stack and partly to see whether you understand why the tool choice matters. They want requirements linked to delivery items rather than living in a separate document set, and awareness that a diagram in a document and a story in a backlog will disagree within weeks. Naming products without a working principle is a thin answer.
How to structure your answer
- Name the tool categories and a couple of products in each.
- Stress linking requirements to build items in one system.
- Explain why parallel documents drift out of sync.
- Say you adapt to whatever the organization already uses.
Example answer
Requirements and stories in whatever the delivery team uses, so usually Jira or Azure DevOps, documentation in Confluence or SharePoint, process models in Visio or Lucidchart, and Miro when I am running a workshop and want people drawing on it with me. For data it is SQL first and then whatever the reporting layer is, Power BI most recently. The thing I care about more than the products is that requirements live in the same system as the build items and are linked, because the moment a requirement exists in a document and separately as a story, they disagree within about three weeks and nobody knows which one is right. I have worked places where the specification was a Word document and the truth was in the backlog, and every conversation started with figuring out which version we were discussing. I would rather use the team's existing tool well than introduce a better one nobody updates.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you handle requirements when the organization has no proper tool at all?
- How do you keep diagrams current once they are in a document?
- What is your experience with dedicated requirements management tools?
Related business analyst questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions