SRE Technical Architect - Observability
SRE Technical Architect - Observability
Posted yesterday
SENIORITY
Manager
About the role
- Own the solution architecture: Define a scalable observability architecture across AWS, Azure, and GCP, covering infrastructure, Kubernetes, applications, and services.
- Design custom dashboards: Translate operational and business requirements into unified views of service health, availability, latency, errors, capacity, and SLO compliance.
- Lead the development team: Break down the architecture into deliverables, guide implementation, review code and designs, resolve technical blockers, and establish engineering standards.
- Integrate telemetry: Design the collection, processing, correlation, and visualisation of metrics, logs, traces, and events using OpenTelemetry, cloud-native services, and observability platforms.
- Guide full-stack engineering: Define API contracts, backend services, data models, and frontend components for interactive dashboards, drill-downs, and service dependency views.
- Embed SRE practices: Implement SLIs, SLOs, error budgets, actionable alerting, incident diagnostics, and automation to reduce operational toil.
- Ensure production readiness: Address security, role-based access, performance, resilience, telemetry retention, and operational cost.
- Drive technical delivery: Collaborate with platform, application, cloud, and operations teams from requirements and proof of concept through production rollout.
- Required technical skills
- Multi-cloud architecture - Strong hands-on experience with at least two of AWS, Azure, and GCP, including monitoring integrations and cross-cloud connectivity.
- Observability engineering - OpenTelemetry, Prometheus, Grafana, and log/trace technologies such as OpenSearch/Elasticsearch, Loki, Tempo, or Jaeger.
- Cloud-native monitoring
- Integration with Amazon CloudWatch, Azure Monitor/Application Insights, and Google Cloud Monitoring/Logging, as applicable.
- Custom dashboard development - Ability to architect frontend applications using React, Angular, or equivalent, with backend services in Python, Go, Java, or Node.js.
- Data and integrationsREST APIs, streaming/event-driven ingestion, time-series data, query optimisation, telemetry correlation, and common tagging standards.
- SRE and cloud-native platformsSLIs/SLOs, error budgets, incident management, Kubernetes, containers, distributed systems, and resilience patterns.
- Engineering automationCI/CD, Git-based development, infrastructure as code, automated testing, and deployment practices.
- Technical leadership - Architecture ownership, developer mentoring, code reviews, technical planning, and hands-on troubleshooting.
- Expected deliverables
- Multi-cloud observability architecture and implementation roadmap.
- Telemetry integration standards and a common data model.
- Custom dashboard MVP with service-level views and diagnostic drill-downs.
- SLO dashboards, alerting standards, and operational runbooks.
- Development guidelines, deployment documentation, and team knowledge transfer.
- Key hiring distinction: This should be a hands-on architect who can lead developers building a custom observability product, not only an SRE operations lead or a monitoring-tool administrator.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
