Domen Gabrovšek
I build backend systems and cloud infrastructure that hold up under scale and regulation: high-throughput services, infrastructure as code, and the privacy engineering that keeps both compliant. I prefer designs small enough to reason about and dependable enough to run in production, and I automate the repetitive work so the time goes to problems that genuinely need it.
I work remotely, and I am always up for a conversation about backend architecture, privacy engineering, or what it takes to run a platform in a regulated industry.
Ten years of building and operating systems has given me a reliable instinct for what will hold up in production. I judge the work by what ships and keeps running. The rest I keep learning, from every system I help grow and from engineers who would approach it differently.
Backend systems. Services that carry real traffic and stay steady as they grow. Observable by design, so the team running them always knows what the system is doing.
Cloud infrastructure. Infrastructure as code, reviewed and versioned like everything else. Environments rebuild from scratch on demand, so production matches what was approved and deploying stays routine rather than an event.
Privacy engineering. Consent and data handling designed into the system from the start, so regulation becomes a constraint you build against and teams keep shipping.
Leading engineering. Choosing the architecture, setting the bar for delivery, and staying close enough to the code that decisions stay grounded in how the system actually works.
Outside work I am usually outdoors: hiking, on the bike, or travelling somewhere I have not been yet. The rest of the time I am probably learning something new.