26 to 29 of 29 Observability Jobs in Surrey

deployment, maintenance and operational support.Strong practical understanding of modern software engineering principles, including maintainable architecture, automated testing, CI/CD, secure-by-design practices, observability and reliability.Successful track record of growing teams and leading transformation initiatives across engineering effectiveness, Agile or flow-based delivery, people development, cloud/SaaS adoption … Azure, cloud-native architectures, SaaS technologies, platform engineering or internal developer platforms.Appreciation of current and emerging technologies, including AI-assisted software delivery, automation, DevSecOps, observability and developer-experience tooling, along with their benefits, limitations and risks.General knowledge of the insurance industry, actuarial or reserving domains, or other regulated software environments.What ...

platform changes through Terraform • Improve deployment processes and reduce the risk of downtime • Troubleshoot platform, networking and workload issues in production • Improve monitoring, observability and operational processes • Work closely with Software Engineering, Security and Architecture teams Required Skills Kubernetes/AKS is essential. You should also have strong experience across … Microsoft Azure • Terraform/Infrastructure as Code • Azure Front Door • Azure API Management • ArgoCD/GitOps • Renovate • CI/CD and deployment automation • Observability and production troubleshooting • Highly available, business-critical production environments Experience supporting high-volume SaaS platforms handling millions of requests would be particularly valuable. Why should ...

each is the right answer Policy-as-code exposure: OPA/Rego, Cedar or similar Running the authorisation engine in production on PostgreSQL, with observability and traceability of the decisions it makes Authentication Enterprise-scale authentication you have architected and operated, not integrated with Hands-on production Curity and/… approaches and tooling (OPA/Rego, Cedar, or equivalent) Understanding of the operational side: running the authorisation engine in production, backed by PostgreSQL, with observability and traceability of authorisation decisions Authentication (Must Have) Architecting and engineering enterprise-scale AuthN solutions, demonstrated at production scale Hands-on production experience with Curity ...

each is the right answer Policy‐as‐code exposure: OPA/Rego, Cedar or similar Running the authorisation engine in production on PostgreSQL, with observability and traceability of the decisions it makes Authentication Enterprise‐scale authentication you have architected and operated, not integrated with Hands‐on production Curity and/… approaches and tooling (OPA/Rego, Cedar, or equivalent) Understanding of the operational side: running the authorisation engine in production, backed by PostgreSQL, with observability and traceability of authorisation decisions Authentication (Must Have) Architecting and engineering enterprise‐scale AuthN solutions, demonstrated at production scale Hands‐on production experience with Curity ...