Hosted by Ash Patel & Sebastian Vietz · 🇺🇸 US · EN · 71 episodes
Established thought leaders with verified media credentials.
Software reliability is a tough topic for engineers in many organizations. The Reliability Enablers (Ash Patel and Sebastian Vietz) know this from experience. Join us as we demystify reliability jargon like SRE, DevOps, and more. We interview experts and share practical insights. Our mission is to help you boost your success in reliability-enabling areas like observability, incident response, release engineering, and more. read.srepath.com
Ash Patel & Sebastian Vietz hosts Reliability Enablers, a technology show with 71 episodes published.
What if the hardest part of reliability has nothing to do with tooling or automation? Jennifer Petoff explains why real reliability comes from the human workflows wrapped around the engineering work. Everyone seems to th
A new or growing SRE team. A copy of the book. A company that says it cares about reliability. What happens next? Usually… not much. In this episode, I sit down with Dave O’Connor, a 16-year Google SRE veteran, to talk a
I know it’s already six months into 2025, but we recorded this almost three months ago. I’ve been busy with my foray into the world of tech consulting and training —and, well, editing these podcast episodes takes time an
Most teams talk about reliability with a margin for error. “What’s our SLO? What’s our budget for failure?” But in the energy sector? There is no acceptable downtime. Not even a little. In this episode, I talk with Wade
Exploring how to manage observability tool sprawl, reduce costs, and leverage AI to make smarter, data-driven decisions. It's been a hot minute since the last episode of the Reliability Enablers podcast. Sebastian and I
Andrew Tunall is a product engineering leader focused on pushing the boundaries of reliability with a current focus on mobile observability. Using his experience from AWS and New Relic, he’s vocal about the need for a mo
Andrew Fong’s take on engineering cuts through the usual role labels, urging teams to start with the problem they’re solving instead of locking into rigid job titles. He sees reliability, inclusivity, and efficiency as t
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit read.srepath.com
Here’s what we covered: Defining Platform Engineering * Platform engineering: Building compelling internal products to help teams reuse capabilities with less coordination. * Cloud computing connection: Enterprises can n
Why many copy Google’s monitoring team setup * Google’s Influence. Google played a key role in defining the concept of software reliability. * Success in Reliability. Few can dispute Google’s ability to ensure high level
Monitoring in the software engineering world continues to grapple with poor signal-to-noise ratios. It’s a challenge that’s been around since the beginning of software development and will persist for years to come. The
The question then condenses down to: Can technical leads support reliability work? Yes, they can! Anemari has been a technical lead for years — even spending a few years doing that at the coveted consultancy, Thoughtwork
We're already well into 2024 and it’s sad that people still have enough fuel to complain about various aspects of their engineering life. DORA seems to be turning into one of those problem areas. Not at every organizatio
We’ll explore 3 use cases for monitoring data. They are: * Analyzing long-term trends * Comparing over time or experiment groups * Conducting ad hoc retrospective analysis Analyzing long-term trends You can ask yourself
Shlomo Bielak is the Head of Engineering (Operational Excellence and Cloud) at Penn Interactive, an interactive gaming company. He’s dedicated much of his talk time at DevOps events to talk about a topic less covered at
Incident response is an increasingly difficult area for organizations. Many teams end up paying a lot of money for incident management solutions. However, issues remain because processes supporting the incident response
According to Vlad Ukis, there are a lot of enterprises around whose IT functions are organized around ITIL. What you use SRE for is something completely different. SRE is not for setting up the IT function. It is for ena
Sonja Blignaut is a complexity expert. That might not sound relevant to incident response in reliability engineering. But it is! Our systems are becoming more complex and so are the resulting incidents. Learning about co
Have you got complete monitoring of your software in effect? Are you sure? Google's SREs break monitoring down to white box versus black box monitoring. It's not the same as internal versus external monitoring, which we'
Jack Neely is a DevOps observability architect at Palo Alto Networks and has a few interesting ways of extracting value from o11y data. We crammed into just under 25 minutes ideas like these 7 takeaways: * Reasserting th
Sponsor detection runs nightly. Check back soon.
No public pitch examples yet for this show.
Generate your own personalised pitchBased on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:
Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.
Shows with the most semantically similar episode content. Pitch one, pitch all; producers cluster.
To pitch Reliability Enablers, visit https://read.srepath.com/s/podcast for contact information, then craft a tight one-paragraph hook that ties your expertise to a gap in their recent technology coverage.
Reliability Enablers is hosted by Ash Patel & Sebastian Vietz. The show is categorised under technology (business) and has published 71 episodes.
Reliability Enablers has published 71 episodes.
Reliability Enablers regularly covers technology, business. It sits in the technology category, with a business focus.
Reliability Enablers is accessible for guests with genuine technology expertise. A personalised, episode-aware pitch will still outperform a generic one every time.
Reliability Enablers hasn't explicitly signalled guest openness in recent episodes. That doesn't rule out pitching. your hook just needs to be especially compelling and relevant to their recent content.
Episodes of Reliability Enablers average 25 minutes. a focused format where a clear narrative arc and tight preparation matter most.
Our data rates Reliability Enablers's guest bar at 80/100 (Premium tier). Established thought leaders with verified media credentials. Sign in to PitchCentric to see how your own Pod Score compares against this show.
Methodology. Booking Probability™ blends Listen Score, 30-day Virality, open-to-guests detection, and Apple ratings. Data refreshed every 60 minutes. Listen Score and Booking Probability are calculated by PitchCentric. Last enriched 4 days ago.
