Job Description

Every bad feature starts life as a valid-looking request.

http

POST /features HTTP/1.1
Content-Type: application/json

{
"ask": "make it work like the other one",
"acceptance_criteria": null,
"stakeholders": ["everyone"],
"edge_cases": []
}

http

HTTP/1.1 400 Bad Request

{
"error": "requirement_not_testable",
"resolution": "send a human"
}

You are the human.

The role

Technical Business Analyst on a 12 month contract, sitting between the product tribes and the engineering teams on a newly funded programme. No direct reports. You own the solution instead.

What the work looks like

- Workshop with business owners in the morning, refinement with engineers in the afternoon, and both walk out feeling understood

- Turn what people say they want into what they actually need, then into user stories and acceptance criteria an engineer can pick up without asking you what you meant

- Pull apart system and enterprise architecture until you know how the thing really behaves





- Stay with the solution from pre-discovery all the way through delivery, not just until the Confluence page is signed off

You will recognise yourself if

- You have around five years doing this properly, in real agile teams, not agile-as-a-meeting-schedule

- You read an API spec for orientation, not for reassurance. Swagger, Postman, JIRA, Confluence

- You understand cloud, microservices and how digital products get built, without being asked to write the code

- You have started using AI tools in your own work and have opinions about where they help and where they do not

The detail

- Day rate contract, 12 month initial duration

- Sydney CBD, hybrid, three days on site

- Mid-level by design. If you are a principal, this one will bore you

Want to see it?

Say the word and I will send the full job description across, no obligation, no twenty questions first.

📌 New Job Opening: Technical Business Analyst in Sydney
🏢 Nameless
📍 Sydney