Job Description & Details
This is a hands-on Business Analyst role centered around bridging the gap between business stakeholders and technical development teams in an Agile environment. You will spend a good chunk of your time writing crisp user stories, untangling complex business processes, and making sure everyone is actually building the right thing. If you like translating messy business requirements into structured technical execution without getting bogged down in endless alignment meetings, this gig is worth a serious look.
What You'll Actually Be Doing
You will be deep in the trenches of requirements gathering, mapping out workflows, and drafting functional specs and acceptance criteria that developers can actually code against without guessing. A typical week involves running backlog refinement sessions, collaborating with architects and QA to catch edge cases early, and supporting user acceptance testing (UAT) to validate that the delivered solution matches the original business intent. You will also be the point person for identifying process bottlenecks and dependency risks before they blow up the sprint.
The Core Tech Stack
To survive and thrive here, you need a solid command of Azure DevOps or Jira for backlog management and agile ceremonies, alongside Visio or similar tools for process mapping. Beyond the standard documentation grind, having working SQL knowledge is a huge asset because you will need to pull and validate data yourself rather than waiting on a data engineer every time you need to sanity-check a requirement.
Interview Expectations
Expect the hiring manager to throw a messy, ambiguous business scenario at you and ask how you would break it down into actionable user stories for a dev team. They want to see how you handle stakeholders who change their minds mid-stream and whether you can write crystal-clear acceptance criteria that prevent scope creep. You should also be ready to discuss a time when you used SQL to troubleshoot a data discrepancy during UAT and how you communicated that fix back to the business.
Application Advice
Your resume needs to scream Agile fluency and hands-on documentation experience. Make sure keywords like Business Requirements Documents (BRDs), user stories, acceptance criteria, Jira, Azure DevOps, and SQL are front and center, backed by metrics or examples of complex workflows you've owned. Skip the vague summaries and highlight specific instances where your requirements gathering saved a project from late-stage defects.