Experience is not time.
It’s responsibility.
My career didn’t grow in a straight line. It grew through systems. From early work in national media platforms, to teaching computer science, to building and leading complex commercial platforms, the common thread has always been the same:
I’ve been trusted with systems that mattered.
Act 01
Foundations: Media, Teaching, and Real Systems
Where production
discipline comes from
I started my career working in national television networks (ARY, GEO), building and maintaining real production platforms at a time when web systems were far less forgiving.
Soon after, I moved into teaching software engineering and computer science at university level, while continuing professional development work in parallel.
This period built:
Strong fundamentals in software engineering and systems thinking
Respect for correctness, structure, and clarity
The ability to explain, reason, and design — not just implement
During this time, I also completed my Masters, MPhil, and PhD in Advanced User Interfaces — grounding my practical work in deep technical thinking.
Act 02
Professional Systems & Full-Stack Engineering
From Code
to systems
I then spent several years working in professional agencies and product teams, including:
Firestone Digital (Australia)
Platinum Web Media (Australia)
Macedon Digital (UK)
Here, I worked across:
PHP, .NET, JavaScript, Laravel, WordPress
Frontend architecture and backend systems
Pixel-perfect implementations and large-scale content systems
This is where my work shifted from:
“Building things” → to “Designing systems that survive real usage”.
Act 03
Platform-Scale Work
Complexity,
at scale
At Macedon Digital and later in other high-end environments, I worked on enterprise-grade WordPress and platform systems, including projects that were featured in the Elementor ecosystem and international showcases.
This phase taught me:
How to keep systems flexible without making them fragile
How to design for long-term change
How to work inside large, multi-team, multi-stakeholder environments
Act 04
Leadership & Ownership
Owning outcomes,
not just code
For many years now, I’ve been working as Lead / Head of Development at SEO Empire (Growth Factory), designing and maintaining high-responsibility platforms for serious businesses.
This includes:
Platform & system architecture
Large WooCommerce and content platforms
Performance & frontend architecture
Long-term technical ownership
Stabilizing and evolving critical business systems
At this level, the job is no longer about implementation.
It’s about judgment, responsibility, and long-term decisions.
The Common Pattern
Across media, academia, agencies, and platform leadership, the work was never really about “making pages” or shipping isolated features. It was always about building systems that could survive growth, making complexity understandable instead of fragile, and making decisions that would not turn into future liabilities. Over time, this shaped how I think about software: as something that should remain calm under pressure, clear in its structure, and dependable long after the original implementation. That is also why my case studies focus on systems and outcomes rather than screenshots — they are stories about responsibility, not just execution.
This is what that experience looks like in practice
The case studies are selected examples of this journey —
products and platforms that required real engineering judgment.