Background
The practice draws on more than six years of professional experience in the design, implementation
and operation of complex IT environments, complemented by an international scientific and engineering research background.
Areas of experience include identity and access management, distributed infrastructure,
high-availability services, automation, security engineering and operational monitoring.
Beyond individual technologies, the focus is on turning complex requirements into maintainable solutions:
coordinating technical stakeholders, managing dependencies and operational risks, documenting decisions
and delivering systems that teams can operate with confidence.
Selected professional experience
The following examples describe experience acquired through professional employment, not completed
client engagements, contracts or endorsements of 113 HASH. Only high-level, non-sensitive details are shown.
High-availability platforms · Technical responsibility
BigBlueButton at cluster scale
Technical responsibility for operating and evolving a production, virtualised videoconferencing
cluster spanning approximately 15 servers in regular operation and up to around 30 at peak.
Work covered availability, capacity, stability and the transition from engineering changes to reliable operations.
Secure access · Technical project leadership
eduVPN and federated identity
Technical project leadership and server-side architecture for a university-wide VPN platform:
cluster design, authentication and authorisation, coordination with network and identity teams,
and reproducible deployments and change management using Ansible and Git-based workflows.
Security operations · Cross-team coordination
Credential-leak response workflows
Technical coordination of credential-leak monitoring and incident-handling processes, bringing
together internal security stakeholders and external service providers.
Project names identify technologies, not vendor partnerships. Individual references and further details
are available only where disclosure is permitted.
Working principles
- Understand before redesigning. Start from the actual constraints and operational reality.
- Prefer maintainable solutions. Complexity should earn its place.
- Security belongs in the architecture. It should not be added as a final checklist.
- Document the handover. A system is only useful if others can operate it reliably.