iCapital · posted · checked
Site Reliability Engineer – Vice President
AWSKubernetesLinuxTerraformOn-site · LisbonManager
Who can apply
On-site · Lisbon
Location: Lisbon, Portugal
About the Role
The Site Reliability Engineering team at iCapital is fundamental to ensuring our platform delivers consistent, reliable service to our client base. Our services run on Kubernetes in AWS, and this role focuses on keeping them healthy in production.
We're looking for the hands-on engineer others turn to when production is broken and the cause isn't obvious. You'll troubleshoot across the full stack (the application, its containers, Kubernetes, and the underlying cloud infrastructure) and turn what you learn into lasting improvements: stronger reliability standards, safer rollouts, sharper alerts, and automation that prevents repeat failures. You'll rely on metrics, logs, and traces every day, but the heart of this role is diagnosing and fixing what they reveal.
Responsibilities
Act as a senior escalation point for complex production issues in Kubernetes-based services, leading hands-on investigation across application, container, Kubernetes, and AWS layers through to root cause.
Partner with the teams that own our cluster infrastructure to resolve platform-level issues, and feed what you learn back into reliability standards and improvements.
Define and implement reliability and operability standards for Kubernetes-based services, including resource sizing, health checks, scaling patterns, rollout safety, and baseline monitoring, as part of service onboarding.
Serve as Incident Commander or senior technical lead for high-severity incidents, lead postmortems, and drive systemic improvements through action items and measurable follow-through.
Turn recurring investigations into runbooks, diagnostic tooling, and automated remediation that shorten time to resolution and eliminate toil.
Coach engineers in systematic troubleshooting and Kubernetes best practices through reviews, game days, and knowledge sharing.
Define, implement, and iterate service level objectives (SLOs) and service level indicators (SLIs) that reflect customer and business expectations.
Standardize monitoring and alerting through “monitors as code” (Terraform preferred), including quality gates such as severity, ownership, and runbook links.