Business Data Analyst
Summary
The Business Data Analyst acts as a bridge between business stakeholders and technical teams to support a multi-year data transformation program. The role focuses on translating business reporting needs into actionable technical requirements for data developers.
Business Data Analyst
RONIN - Australia (Remote)Not another BA brief. Read this one properly.
Business Data Analyst
Somewhere inside a well-established Australian organisation, a multi-year data transformation programme is quietly reshaping how the business understands itself. They need an intermediate-level Business Data Analyst (Business Intelligence) who can sit between the people who ask for reports and the people who build them, and translate one into the other without losing anything in the middle.
This is deliberately not a lead or principal-level position, and it's not rated as one. If you're used to running the show end-to-end with a team under you, this will feel like a step down, not a lateral move. If you're a few years in, sharp, hands-on, and happy to be part of a delivery team rather than running it, keep reading.
What you'll actually be doing
- Sitting in workshops and interviews, asking the annoying-but-necessary questions nobody else thinks to ask
- Turning business waffle into functional requirements, user stories and acceptance criteria that a delivery team can actually build from
- Working elbow-to-elbow with BI and Data Engineering to keep requirements grounded in reality
- Running traceability between what was asked for, what was built, and what was tested (so nothing quietly disappears along the way)
- Supporting UAT, defect triage, and the odd stakeholder demo where you get to show off the finished product
What you'll bring
- Circa 3+ years turning business needs into clear, documented requirements (this is an intermediate role, priced and scoped accordingly, so if you're operating at senior/lead/principal level with the day rate to match, this one won't be a fit)
- Comfortable enough with SQL and relational data concepts to hold your own in a technical conversation
- Some exposure to conceptual/logical data modelling (bonus, not a dealbreaker)
- Agile or hybrid delivery experience
- The diplomacy to manage a room full of senior stakeholders with competing opinions, without losing the plot
The practical bits
- Contract role, intermediate level, rate set accordingly
- Remote friendly
- No direct reports of your own to manage (just requirements)
If this sounds like your kind of chaos, and the level's right for you, get in touch.