Job Description Implementation Consultant Sydney | Hybrid If you’ve ever thought: “I’m more technical than a BA… but I don’t want to be a developer” “I like working with clients, but I still want to stay hands-on” “I want to actually build solutions — not just write requirements” This is probably the role you’ve been looking for. What this role actually is This is not a pure BA role. And it’s not a software engineering role either. It sits right in the middle. You’ll take real customer problems → break them down → and actually build the solution inside a platform . You’re not handing work over to devs — you’re owning the outcome end-to-end . What you’ll be doing Configuring the platform — including data structures, workflows, business rules, and financial calculations Analysing and transforming data to support system integrations Testing and validating solutions to ensure quality delivery Working closely with clients and developers to translate requirements into technical outcomes Documenting changes, tracking progress, and contributing to new product features The kind of background that works here There’s a pattern to people who succeed in this role. You’ve probably come from one of these: A Technical BA who leans into the technical side An Implementation / Solutions Consultant in a SaaS or platform environment A Systems Analyst who enjoys both problem-solving and stakeholder interaction A developer who wants to stay hands-on, but be more involved with clients and outcomes What we’re looking for Hands-on coding experience (Java, C#, C++, Python, or similar OOP languages) Strong logical thinking and problem-solving capability Experience working with databases (SQL) and software configuration Ability to communicate clearly with both technical and non-technical stakeholders A genuine interest in technology and how systems work Nice to have: Experience in general insurance, SaaS, or complex rule-based systems Why people move into roles like this Because it gives you: Ownership — you’re building, not just documenting Balance — technical depth with real client interaction Variety — different problems, projects, and stakeholders Impact — you can see what you’ve delivered in action A quick sense check You’ll probably enjoy this if: You like solving complex problems and seeing them through to delivery You’re comfortable working with both systems and people You want to stay hands-on, without being purely engineering-focused You prefer building outcomes over writing documents If this sounds like you — or close enough to be curious — it’s worth a conversation.
