Senior Architect

Leading Platform Architecture

As Senior Architect, the job expanded from designing systems to designing the teams and processes that build them. Platform architecture means building the foundations other engineers build on — getting it wrong is expensive, getting it right creates leverage across everything that follows.

Stakeholder management at this level is as critical as technical judgement. The best architecture that can't be funded, staffed, or explained to non-technical leadership doesn't ship. Learning to speak business first and technology second was a hard-earned skill.

What I Created

• Apache Camel-based integration solutions connecting disparate enterprise systems across a complex, heterogeneous technology landscape
• A Node.js time-tracking system for recording and managing employee attendance data at scale
• The platform layer architecture underpinning the full enterprise product suite — the foundation every other service was built on
• A systematic security remediation initiative that identified and eliminated critical vulnerabilities across the enterprise codebase
• An API-first transformation of the enterprise suite, establishing clean contracts between services and enabling long-term extensibility
• A unified authentication and identity management layer, standardising how users and services authenticated across the platform

Going Deeper

This role pushed me to formalise what I was learning on the job. The depth of cloud work led me to pursue the AWS Solutions Architect certification, and the security challenges I encountered motivated me to complete a Postgraduate Diploma in Computer and Information Systems Security — turning hard-won practical experience into structured, credentialled expertise.

What I Learned

Leading a 20+ engineer team across a multi-million dollar product line taught me that technical leadership is fundamentally an organisational discipline. Setting direction, building consensus, resolving conflict, and keeping a large team aligned on a shared architecture requires as much rigour as the architecture itself.

The biggest shift was learning to treat architecture as a living system — one that must evolve with every change while remaining easy to reason about and safe to modify. Working directly with VPs to shape both the technical roadmap and the engineering team structure gave me a full-stack view of how product, people, and platform decisions interact.

Along the way, I built deep literacy in software security and identity management — understanding not just what secure systems look like, but why the threats exist and how authentication mechanisms hold up under real-world pressure.