Hi S***n,
Glad to hear it sounds like a fit. Here’s a bit more color on those points:
1. Terraform modules
, We’ve been building our shared module library for roughly two years, covering networking, IAM, EKS/AKS clusters, logging, cost-allocation and compliance hooks.
, Every change flows through our GitLab CI pipeline with automated plan/apply validations and peer reviews focused on DRY principles.
, Today it manages about 80% of our infra provisioning; we iterate on new modules each sprint based on squad feedback.
2. SRE & observability
, We’ve embedded Prometheus metrics across all services and maintain a curated set of Grafana dashboards and alerts.
, Our teams define SLIs/SLOs, manage error budgets and rotate on-call duties among cloud engineers.
, Regular post-mortems and “game days” help us tighten alerts, improve pipeline resilience and reduce noise.
3. Reporting line
, As Head of Cloud Engineering & R&D you’d sit on L***m’s senior leadership team, reporting directly to our CTO, and partner closely with product, data science and compliance heads.
4. R&D roadmap prioritization
, Quarterly planning is driven by the CTO in collaboration with product leadership, data science and QA,balancing feature requests, regulatory deadlines (Swiss data-privacy, MDR) and performance/cost targets.
, Your squads provide technical estimates and risk assessments during sprint-zero, which helps us sequence work for maximum velocity and audit readiness.
Hope this gives you a clear picture,let me know if you’d like to dive deeper on any of these or set up a call with the CTO to walk through the roadmap in detail.