Services

Resources

Company

The implications of AI in the SRE world | One2N Bits Ep.5

Jan 5, 2026

AI in SRE is not just about flashy incident bots or code‑completion in your terminal. In this One2N Bits episode, Saurabh Hirani (Principal SRE, One2N) and Jaideep (CTO, One2N) break down what it really takes for AI to be useful in SRE teams, from documentation and RCAs to on‑call culture and leadership incentives.

​They discuss whether AI can actually replace SREs, how to think in terms of “sub‑agents” mapped to SRE workflows, and why organizational context, knowledge sharing, and responsibility ownership matter more than yet another AI tool.

What you’ll learn

Why AI in SRE is more than a code completion agent, and how to scope AI sub‑agents across incident management, capacity planning, and automation.

How to handle knowledge hoarding, fear of replacement, and responsibility diffusion when AI is mandated from the top.

Practical ways to use AI to clean up RCAs, keep architecture and docs fresh, and shorten onboarding feedback loops for SREs.

How AI can free SRE teams from boilerplate and cognitive load so they can focus on business‑critical reliability work.

Continue watching

Watch Talk

Platform Engineering Strategy: Scaling from 5 to 500 Engineers | One2N Bits Ep. 6

Jaideep Khandelwal

CTO @One2N

Srivatsa RV

SRE @One2N

Platform engineering means very different things depending on where your org is, and most teams don't realize they've been doing it all along. In this One2N Bits episode, Srivatsa (SRE, One2N) and Jaideep (CTO, One2N) put on a strategy hat to break down platform engineering from first principles, not tooling. They cover when you actually need a platform team, what non-negotiables hold at every org size, how to drive adoption without disrupting developers, and the classic specialist trap that growing teams fall into. What you'll learn - Why the line between DevOps, SRE, and platform engineering is intentionally blurry, and when it needs to get sharper - Non-negotiable cultural practices for platform teams, regardless of whether you're 5 or 500 engineers - Hub-and-spoke vs embedded platform engineers: which model works and when - The specialist trap: when generalists are enough, and when you need execution with authority - How shift-left thinking is quietly increasing developer cognitive load Who this is for: Founders and engineering leaders deciding when to spin up a dedicated platform team. Platform engineers and SREs looking to frame their work as a product, not just plumbing. Teams at the 50–200 engineer stage where platform culture either solidifies or fractures. 🔔 Part 2 coming soon: team topologies, org structures, and measuring platform success beyond vanity metrics.

Watch Talk

Platform Engineering Strategy: Scaling from 5 to 500 Engineers | One2N Bits Ep. 6

Jaideep Khandelwal

CTO @One2N

Srivatsa RV

SRE @One2N

Platform engineering means very different things depending on where your org is, and most teams don't realize they've been doing it all along. In this One2N Bits episode, Srivatsa (SRE, One2N) and Jaideep (CTO, One2N) put on a strategy hat to break down platform engineering from first principles, not tooling. They cover when you actually need a platform team, what non-negotiables hold at every org size, how to drive adoption without disrupting developers, and the classic specialist trap that growing teams fall into. What you'll learn - Why the line between DevOps, SRE, and platform engineering is intentionally blurry, and when it needs to get sharper - Non-negotiable cultural practices for platform teams, regardless of whether you're 5 or 500 engineers - Hub-and-spoke vs embedded platform engineers: which model works and when - The specialist trap: when generalists are enough, and when you need execution with authority - How shift-left thinking is quietly increasing developer cognitive load Who this is for: Founders and engineering leaders deciding when to spin up a dedicated platform team. Platform engineers and SREs looking to frame their work as a product, not just plumbing. Teams at the 50–200 engineer stage where platform culture either solidifies or fractures. 🔔 Part 2 coming soon: team topologies, org structures, and measuring platform success beyond vanity metrics.