One real night.

Atlas Technica’s model — shouldering IT management and cybersecurity for hedge funds so those firms can stay focused on capital — is exactly the kind of focused, high-accountability service environment I want to work in. The core values you publish (ownership, execution, camaraderie) aren’t wallpaper; they read like the operating principles of a team that actually ships.

The JD asks for proficiency with Azure and hybrid cloud environments, and the ability to design, scope, and execute tailored solutions for complex clients. That’s the work I’ve been doing at my current employer: designing and implementing Azure governance, policy, cost management, hub-and-spoke shared services, and identity-vend workload automation — all in a multi-subscription topology delivered through GitHub Actions and Bicep IaC pipelines. AWS is not my primary platform today, but the architecture and governance patterns transfer, and I’m direct about closing gaps fast when the work demands it.

Mozilla’s 25-year track record of shaping internet standards without shareholder pressure is exactly the kind of operating environment I want to work in. The mission isn’t a tagline — it’s the actual constraint that drives product and infrastructure decisions, and that’s rare. When I read that Mozilla is building the next 25 years of technology with 225 million monthly users depending on it, I want to be part of the infrastructure holding that up.

The Staff Operations Engineer role calls for someone who can own architecture within a defined domain, lead complex cross-team initiatives, and stay hands-on with critical systems — that’s the job I’ve been doing at my current employer. I’m mid-flight on a Bicep hub-and-spoke landing-zone modernization spanning multi-subscription topology, hybrid DNS with Azure Private Resolver, Entra-based deployment identities, and GitHub Actions IaC delivery. On the cross-team side, I’ve been the person who breaks ambiguous architecture problems into implementable phases, writes the runbooks that make systems operable by others, and eliminates toil systematically — I track it monthly, not as a vibe but with receipts.

ClickHouse landing on the 2025 Forbes Cloud 100 — while posting 250%+ ARR growth and closing a $400M Series D — is the kind of signal that’s hard to ignore. That’s not a company coasting on a good product; that’s a company in the middle of something. The Senior Consulting Engineer role on the AMER team is exactly where I want to be for it.

The JD asks for 5+ years operating scalable, fault-tolerant distributed systems and hands-on cloud infrastructure work — that’s the job I’ve been doing at my current employer. I own the Azure landing-zone modernization end to end: hub-and-spoke topology, multi-subscription management, Bicep IaC delivered through GitHub Actions, hybrid DNS with Azure Private Resolver, and RBAC scoped per environment. I haven’t worked with ClickHouse specifically yet, but I’ve been closing gaps deliberately — Terraform, FinOps, data pipeline fundamentals — and I pick up new tooling fast when the work demands it.