This recap includes the following episodes and guests.Â
Guest title reflects the guest's position at the time of the episode.
Recipes:
The Origin StoryÂ
SRE Fundamentals
Career PathÂ
People First - The Core Ingredient
ROI - Measuring what Matters
Welcome to the first crack at our SRE Omelette! I had the pleasure of speaking with two powerhouse voices in IBM - Ingo Averdunk, IBM Distinguished Engineer, IBM Garage for Cloud and IBM SRE profession leader, and Kareem Yusuf, now SVP, Ecosystems, Strategic Partners & Initiatives. Together, we peeled back the layers of what SRE means, how it evolved at IBM, and why itâs more than just a roleâitâs a mindset, a movement, and a recipe for success.
Goal: Reframe culture as an outcome.
The omelette metaphor wasnât just about clever branding. It was about shifting the conversation from reactive firefighting to intentional transformation. Kareem explained that culture isnât something you wait forâitâs something you create. âWhen you think about culture and behavior,â he said, âyou are really driving for an outcome.â That outcome, he emphasized, must be rooted in the customerâs reality. âNone of our customers wake up every single day going, âOoh, I want to use your software today.â Theyâre trying to get an actual task done.â
This clarityâabout purpose, value, and impactâbecame the foundation for IBMâs SRE evolution. It wasnât about adding another layer of process. It was about aligning engineering with outcomes that matter.
âWhen you think about culture and behavior,â he said, âyou are really driving for an outcome.â - Kareem Yusuf
Goal: Shift from reactive ops to full lifecycle ownership.
Ingo Averdunk, IBMâs Global SRE profession leader, has long believed that the real challenge in software isnât building itâitâs running it well. His background in service management gave him a front-row seat to the âday twoâ experience, where systems either deliver value or fall short. Thatâs why SRE, to him, was a natural evolution.Â
âWe are moving away from projects to products,â he explained, âand SRE is very much in support of understanding the full life cycle.â - Ingo Averdunk
Ingo emphasized that SRE isnât just about uptimeâitâs about ownership. He encouraged engineers to build depth before breadth, advising, âPick one area and go deep. Build the muscle of being able to decode the system.â That depth, he believes, is what builds confidenceâand ultimately, resilience.
But he also challenged the idea that automation is the end goal. Sharing a story about a server that crashed every Monday, he noted, âIf my application server dies every Monday, I could automate a restartâbut the problem still exists.â True SRE and the engineering rigor we want to arrive at, he said, is about engineering the problem away, not just masking it with scripts.
Goal: Create space for SREs to grow, thrive, and be recognized.
One of the most transformative decisions IBM made was to formally recognize SRE as a profession. This wasnât just a title changeâit was a cultural shift. Ingo helped lead the effort, and he speaks about it with pride. âItâs not just a roleâitâs a profession with a curriculum, a roadmap, and a career path.â
This structure gave SREs a place to grow, learn, and be seen. It also helped IBM attract and retain top talent. âUltimately,â Ingo said, âwe want to attract, nurture, and retain the right skill and the right talent.â It was a recognition that SRE isnât a temporary trendâitâs a long-term investment in people and practice.
Kevin echoed this sentiment, reflecting on his own journey. âIâve always worked in performance, scalability, and reliability,â he said, âbut I often had to explain and justify my contributions. Having a formal SRE profession gives future engineers a clearer path.â
Ingo also offered advice for aspiring SREs: âDonât try to do it all. Pick one area and go deep. Build the muscle of being able to decode the system.â Whether youâre a dev or a sysadmin, thereâs a path into SRE if youâre curious, collaborative, and committed to resilience.
Goal: Center the SRE profession around human skill and collaboration.
Both episodes closed with a reflection on people and emphasized that the real secret sauce is people.
For Kareem, the most important part of building a world-class SRE function isnât the toolingâitâs the people. âThe number one ingredient,â he said, âitâs got to be people and their skills.â He spoke about the importance of meaningful work, professional pride, and creating environments where people can thrive. âEverything we do is human capital. Itâs us who bring our brains to work to generate this IP every day.â
Ingo reinforced this idea, especially when it comes to incident response. âSRE is a team sport,â he said. âKnowing someone has your back at 2 a.m. matters.â Itâs not just about solving problemsâitâs about solving them together.
Goal: Define success through outcomes, not just uptime.
Kareem also tackled the tough topic of prioritization. His framework? Time, cost, and quality. But he added a twist: âFeatures are useless if customers cannot use them meaningfully to get their work done.â
When it comes to ROI, Kareem offered a refreshingly honest perspective: âA real simple measure of ROI for me isâI ainât getting calls.â But behind that simplicity is a deeper vision. Heâs not just looking for fewer incidentsâheâs looking for transformation. âThe real return on investment Iâm looking for,â he said, âis this vision of being able to deliver our software consistently everywhere, no matter how itâs deployed.â
Ingo added that while metrics like MTTR and automation rates are useful, theyâre not the whole story. âYou need to find good performance indicators that measure velocity, quality, and efficiency,â he explained. Because in the end, SRE isnât just about keeping systems upâitâs about helping teams move faster, build better, and deliver more value.
Here are a few questions to spark deeper conversations with your team or community:
đ§© How do you define the boundaries of SRE in your organization - where does it start and stop?
đ§ How do you personally define the ROI of reliability work in your organization?
đ§Ș If SRE is a team sport, what role do you playâand how can you support your teammates better?