About
I’m Robert, a Principal Software Engineer & Product Designer based in Melbourne, Australia. I build AI systems, shape technical platforms, and design the interfaces that make those systems usable where the buttons actually get pressed.
Most of the work lives where architecture, product direction, interface design, and delivery overlap. I’m usually brought in when the moving parts are messy, the stakes are real, and the thinking has to stay coherent all the way through.
About
I’m Robert, a Principal Software Engineer & Product Designer based in Melbourne, Australia. I build AI systems, shape technical platforms, and design the interfaces that make those systems usable where the buttons actually get pressed.
Most of the work lives where architecture, product direction, interface design, and delivery overlap. I’m usually brought in when the moving parts are messy, the stakes are real, and the thinking has to stay coherent all the way through.
That has taken me through Defence, finance, healthcare, education, and enterprise SaaS, mostly in independent contract roles. The fit is strongest when a brief needs senior judgment, hands-on delivery, and as little translation loss as possible between them.
Defence
Government-cleared platforms under security constraints, built for environments that do not forgive loose thinking.
Finance
Institutional finance interfaces and concept architecture shaped by regulated workflows and a strong need for clarity.
Healthcare
National-scale component systems with accessibility, compliance, and member-facing work built in from the start.
Education
Learning analytics, accreditation platforms, and online delivery at university scale.
Building for the early internet. Photoshop comps, sliced layouts, and front-end work close to the metal.
Consulting begins. Finance, healthcare, and education were first on the roster, with delivery work moving fast.
Institutional finance concept work. Tight constraints, complex workflows, and a strong bias toward clarity.
Defence. LMS architecture and product design for the central system in a training platform shipped across parallel teams.
AI work shipped. RAG, agents, MCP servers, and governance into Defence and enterprise SaaS.
Consulting on AI systems and integration, alongside commercial AI products still in development.
Building for the early internet. Photoshop comps, sliced layouts, and front-end work close to the metal.
Consulting begins. Finance, healthcare, and education were first on the roster, with delivery work moving fast.
Institutional finance concept work. Tight constraints, complex workflows, and a strong bias toward clarity.
Defence. LMS architecture and product design for the central system in a training platform shipped across parallel teams.
AI work shipped. RAG, agents, MCP servers, and governance into Defence and enterprise SaaS.
Consulting on AI systems and integration, alongside commercial AI products still in development.
How I Work
Problem first
Start with what the business needs to be true, then map the constraint properly. Stack choice comes after the problem is properly defined.
Systems thinking
Follow the data, the failure modes, and what the next engineer inherits. I build for the day the system is under pressure and I'm not in the room.
Designcode
The person shaping the interface should understand how it is built. That keeps intent intact and makes accessibility harder to postpone.
AI that ships
Most AI projects break between prototype and dependence. I work in the gap where orchestration, governance, and product behaviour become reliable.
Revenue aware
Revenue model and delivery model matter earlier than most teams want to admit. A useful system still needs a commercial frame, or it turns into expensive drift.
Early and market proven
I adopt tools before they are fashionable, but only when they solve a real problem better. The pattern is less about novelty than judgement under uncertainty.