Senior Infrastructure & Identity Engineer. I work at the point where identity, security, automation, and AI intersect — designing platforms that are boring in production and difficult to break on purpose.
I design and operate infrastructure platforms for fast-moving startups and regulated enterprises, with identity, endpoint security, and observability as first-class concerns. I treat identity lifecycle, access control, and policy enforcement as software — expressed as code and orchestrated through APIs, event-driven workflows, and data pipelines rather than manual tickets.
I lead the development of internal platforms and opinionated interfaces that hide underlying complexity, so product teams integrate once and get consistent authentication, compliance, and automation behaviour “for free.”
identity & IAM · MDM / EDR · SIEM · zero trust · API-first · SOC2 / ISO27001
I approach infrastructure as a systems-thinking problem: understand the signals, model the feedback loops, then make the safest path also the default path. Most of the work is about aligning mechanisms — identity, devices, networks, logs — so that the system resists bad states without constant human intervention.
I like problems where the failure modes are subtle, the blast radius is big, and the answer is a change in architecture or automation — not just another runbook.
I’m particularly interested in using AI and automation to make security and operations less reactive. That includes building workflows that correlate identity signals, device posture, and activity patterns to drive real-time access decisions — as well as internal services that continuously reconcile “what should exist” with “what actually exists.”
When things work the way I intend, most people never notice. Access just works, reviews are pre-populated, alerts are filtered, and incidents arrive with context instead of guesswork.
Over the years, I’ve shifted from fixing individual incidents to shaping the platforms and guardrails entire organisations build on. I care about long-term technical quality: de-risking critical paths, simplifying architectures, and creating patterns that other teams can adopt without thinking about the underlying machinery.
My favourite compliment is when a complex system feels “simple” from the outside — even if the internal graph of services, policies, and automations is anything but.
I share enough about my work to be useful, but not enough that you can fully reconstruct the systems I design. The most interesting pieces live in internal diagrams, threat models, and quietly-evolving automation — not in public screenshots.
If you’re working on hard problems around identity, infrastructure, or AI-driven automation, I’m always open to the right conversation.
I’m open to collaborations, technical discussions, and ideas that push infrastructure, security, and automation beyond “standard practice.” If it doesn’t quite fit into a checkbox — reach out.