SRE Conf 2023
Rootconf For members

SRE Conf 2023

Availability and reliability 24/7- the SRE life



Schedule for the conference on 24 November is published.

Why SRE Conf?

When any organization goes from product market fit or beta test phase to production rollout, or from first x customers to 10x or 100x customers and starts scaling, they typically start running into challenges with systems stability and resiliency. These challenges change with every phase of growth. So does the need for having a SRE team and/or a DevOps team, and the role these teams play.
Unfortunately, there is no one-size-fits-all solution when it comes to what roles these teams should play, and which tools various teams should use to track the metrics and processes involved. But there are some common building blocks that apply in similar (and different) ways and forms for most teams. The idea of the SRE Conference is to get together and to know about these building blocks, share and learn about the themes that fall under the SRE umbrella.

SRE Conf tracks

SRE Conf is a two-track conference. The track, “Culture, career and Evolution” is more focused on leadership, team, and organizational topics while the “Stories from the Trenches” track will cover real-world scenarios, and lessons learned which will help engineers and engineering teams to upskill themselves by understanding experiences from their industry peers.

Culture, career, and evolution

  1. SRE v/s DevOps v/s Platform Engineering teams in organizations.
  2. Hiring and building SRE teams.
  3. Blameless postmortems.
  4. Role of AI in SRE/DevOps/Platforms.
  5. FinOps and cost optimization.
  6. SRE Anti-patterns

Stories from the trenches:

  1. Incident management.
  2. Change management.
  3. Scalability and performance.
  4. SLA/SLO and golden signals.
  5. Security and DevSecOps.
  6. Systems and networking.

Key takeaways for participants

  1. Improved understanding of organizational needs and requirements.
  2. Enhanced optimization skills.
  3. Networking opportunities.
  4. Knowledge sharing and community building.

Who should participate

  • Members of SRE, DevOps or platform teams.
  • A software developer or manager who is responsible for services running on any cloud platform or on-prem data center.
  • Technology leader of an engineering team that manages critical systems which should have minimal to zero downtime.


If you are interested in speaking at the conference, submit your talk idea here. The editors - Sarika Atri, Safeer CM and Saurabh Hirani - will review your talk description and give feedback.

Speakers will also receive feedback and assistance during rehearsals from past speakers such as Sitaram Shelke.

Guidelines for speaking, speaker honorarium policy, and travel grant policy details are published here.

About the editors

This conference themes were set up by Sarika Atri and Safeer CM. Together with Saurabh Hirani, the three editors have:

  1. Reviewed the talks.
  2. Set up the editorial workflow.
  3. Finalized talk selections.
  4. Curated the schedule.

Sarika Atri is Software Architect with over twenty years experience in the industry. Sarika was reviewer for Rootconf Cloud Costs Optimization conference held in July 2023.
Safeer CM is Senior Staff SRE at Flipkart. He is author of Architecting Cloud-Native Serverless Solutions published by Packt.
Saurabh Hirani is former editor of Rootconf, and a passionate member of the community. Saurabh is SRE at,. He has a keen interest in mentoring speakers.

Become a Rootconf Member to join

SRE Conf is a community-funded conference. It will be held in-person. Attendance is open to Rootconf members only. Support this conference with a membership. If you have questions about participation, post a comment here.


Sponsorship slots are open for:

  1. Tool and solutions providers.
  2. Companies interested in tech branding for hiring.

Email sponsorship queries to

Contact information

Join the Rootconf Telegram group at or follow @rootconf on Twitter.
For inquiries, contact Rootconf at +91-7676332020.

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Ravindra Harish

SRE: "Toil Reduction" through Communication/Collaboration/Coordination!

Submitted Sep 19, 2023

Among the fundamental pillars of the SRE practice and framework, “Toil Reduction” is one that gives SREs a kick for rightly serving both the left (engineering) and right (operations) parties of the product. It reflects the principles for which Google introduced SRE in the first place. As they famously said, “Put a software engineer in front of an operational problem and see how the paradigm changes in solving the problem”.

As the conference theme includes communication, collaboration and coordination for operational challenges, I would like to bring together the best of the SRE pillar called “Toil Reduction”, the best of the collaboration tool “Slack” and how together we can work to maintain the importance of the SRE mindset to reduce workload, reduce frustration between microservice silo teams, increase the speed of incident identification and resolution. Blending ChatOps, AIOps and virtual bots with real humans is a perfect example of a future where humans work alongside bots sitting right next to each other (virtually 😊 )!

Hello everyone. I am Ravindra Harish. I am the Director of SRE at Nike. I recently moved back to India and am here to establish and drive the SRE practices at our India office serving our global technology units of Nike. I have been leading the SRE function at Nike for the last 6 years. We are a company that strongly believes that a perfect SRE can be a combination of great software engineers and a good talent of domain experts from the operations side. We run an IDENTIFICATION (proactive) model of incidents through tools like Splunk, SignalFx, Catchpoint and NewRelic to deliver the value of Distributed Tracing, Chaos Engineering with a clear focus on reducing MTTD, MTTR, PAV, improving Fault Budget and hence define CUJ through SLI/O with derivation at SLA!

I would like to present a real-life case study as part of an event. We have a product that we call D.O.E.S (DevOps Enablement Systems), which is very focused on toil reduction using Slack and AWS. We have had a lot of success with ChatOps and are now very focused on bringing AIOps into the mix. If we get the chance, we’d love to show you a demo and expose you to the possibilities of the future in the world of collaborative automation.


{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more