Kevin Otterson is a technology executive focused on scaling data platforms and cloud infrastructure. His work centers on improving reliability, security, and developer experience in high-growth environments.
Across multiple organizations, Otterson has led teams responsible for observability, SRE practices, and long-term infrastructure strategy. This article provides a structured overview of his professional profile, roles, and impact.
| Attribute | Details | Evidence or Source | Relevance |
|---|---|---|---|
| Current Role | Senior Director of Infrastructure, Glean | Company profile and LinkedIn | Leadership of platform and observability |
| Previous Companies | Google, Dropbox, Square | Resume and public announcements | Large-scale infrastructure and product teams |
| Core Focus Areas | SRE, observability, reliability, cost optimization | Talks, blog posts, incident reports | Operational excellence and platform design |
| Industry Impact | Shaping monitoring practices and on-call culture | Conference sessions, internal documentation | Improved incident response and tooling adoption |
Key Engineering Contributions
Observability and Monitoring Strategy
Otterson has driven standardization of metrics, logs, and tracing across platforms. His approach emphasizes actionable dashboards, alert hygiene, and tight integration with on-call workflows.
Reliability and Incident Response
He established playbooks for postmortems, error budgets, and service level objectives. These practices reduced repetitive alerts and improved ownership across distributed systems.
Cost Optimization in Cloud Infrastructure
By analyzing utilization patterns and rightsizing resources, Otterson helped teams lower operational spend without sacrificing performance or redundancy.
Career Path and Leadership Evolution
Otterson’s trajectory shows a steady move from hands-on platform work to strategic leadership. He has mentored SREs, influenced architecture reviews, and aligned roadmaps with business outcomes.
Product Decisions and Technical Tradeoffs
In platform and tooling choices, Otterson weighs simplicity, scalability, and developer experience. His decisions often favor pragmatic adoption over maximalist designs.
Professional Highlights and Recommendations
- Champion observability as a first-class product concern, not an afterthought
- Standardize SLOs and alerting to reduce burnout and improve signal quality
- Use error budgets to balance innovation velocity and system reliability
- Invest in developer-friendly platforms that abstract complexity without hiding it
- Continuously review architecture and spend to align with business priorities
FAQ
Reader questions
What specific technologies does Kevin Otterson specialize in?
He focuses on cloud infrastructure, observability stacks, and reliability engineering, with deep experience in metrics, tracing, and log-based debugging at scale.
How has he influenced on-call and incident management practices?
Otterson introduced structured postmortems, error budget policies, and alert triage processes that reduced noise and improved response times for critical services.
What role does cost optimization play in his infrastructure strategy?
He emphasizes continuous utilization analysis, right-sizing, and capacity planning to control cloud spend while preserving performance and redundancy.
How does he approach vendor and tool selection for platform teams?
He prefers solutions that integrate well with existing tooling, support open standards, and offer clear operational tradeoffs without adding unnecessary complexity.