Sign In

Rich Burroughs

I like telling stories about software (he/him)

Professional Background

Rich Burroughs is a seasoned professional in the technology sector with extensive experience in site reliability engineering, product management, and community engagement within various renowned organizations. Most notably, Rich has served as a Senior Developer Advocate at FireHydrant, where he played a pivotal role in bridging the gap between developers and operational teams, promoting the importance of reliability within software development practices.

Before his tenure at FireHydrant, Rich was a Community Manager at Gremlin, where he was instrumental in fostering a vibrant community focused on chaos engineering—a unique approach designed to improve system resilience. His experience also includes a significant role as a Product Manager at Sensu, Inc., where he contributed to the development and management of observability and monitoring solutions that help organizations ensure their systems operate smoothly and efficiently.

Rich's roots in the technology industry can be traced back to his positions at Puppet, a leader in IT automation. He started as a Site Reliability Engineer and later moved up to Senior Site Reliability Engineer, demonstrating his proficiency in maintaining and optimizing the performance of high-traffic systems. His journey in operations kicked off at Yesmail, where he served as an Operations Engineer, ensuring that transactional email platforms ran seamlessly to support client needs. Additionally, Rich led a team as Operations Team Lead at Heartland Payment Systems, where he applied his technical expertise to enhance operational workflows and ensure the reliability of payment processing systems.

Education and Achievements

Rich Burroughs has complemented his professional experience with a solid educational foundation. His commitment to continuous learning and development has not only fueled his career growth but also established him as a thought leader in the tech community. Rich's notable achievements include spearheading initiatives that promote the best practices in reliability engineering and contributing to open-source projects that improve software reliability and operational excellence.

In his various roles, Rich has successfully led workshops, shared insights at conferences, and authored articles aimed at educating both technical and non-technical audiences on the value of software reliability. His passion for community building is evident in his efforts to organize meetups and training sessions that empower professionals to adopt a more resilient approach to operations and software development.

Achievements

  • Senior Developer Advocate at FireHydrant: In this role, Rich effectively communicated best practices in reliability to various stakeholders and empowered developers to embrace a site-reliable mindset.
  • Community Manager at Gremlin: Established a thriving community around chaos engineering, leading discussions and providing resources that enhance knowledge sharing and practical application of reliability principles.
  • Product Manager at Sensu, Inc.: Played a vital role in developing market-leading monitoring solutions, driving product strategy aligned with customer needs and technological advancements.
  • Site Reliability Engineer at Puppet: Made significant advancements in system performance and operational efficiency, supporting high-availability configurations for several clients.
  • Leadership at Heartland Payment Systems: Led an operations team to optimize payment processing systems, ensuring the highest reliability standards are maintained.

Through these diverse and impactful roles, Rich Burroughs has established a remarkable career characterized by innovation, leadership, and a deep commitment to enhancing the reliability of technology systems.

Highlights

Aug 23 · linkedin

I've been playing around with Jupyter Notebooks for the first time and they're very cool. I never understood the appeal, but after using them I can see why they've caught on so much, especially with people outside of traditional software engineering environments.

I'm finding them especially useful for sketching out things quickly. I have a notebook that I'm using for just bits of random Python code.

Jul 24 · linkedin

It's been great to see my friends from the Resilience Engineering community, like Lorin Hochstein and Will Gallego, posting their thoughts about the Crowdstrike incidents. I said incidents plural because every company that was impacted had its own incident, and they were all different.

I don't have enough insight into what happened internally at Crowdstrike to have hot takes about how they can improve their processes. I read the information they posted about their remediation, but it's very surface-level. What I do know is that producing mission-critical software that runs on so many platforms and hosts is a huge challenge.

The closest I've come to living in that world was my time at Puppet. The QA team for the Puppet agent had a matrix of releases and platforms to test on, and the automated testing was slow and resource-intensive. If the agent we released failed, the worst case would probably be that the host didn't get configuration updates for a bit. Not great, but also not something likely to cause outages worldwide. And even managing that was complex.

I know it's easier and more fun to have the hot takes, but I saw Lorin talk about the lack of curiosity he'd seen from people, and I agree. I'd encourage people not to jump to conclusions and to see what we can learn as more information comes out. I'm especially interested in hearing from organizations that were impacted by the outages. There will almost certainly be cases where teams that weren't even using Crowdstrike were impacted by outages at their upstream dependencies. There should be some fascinating stories.

Related Questions

How did Rich Burroughs develop his expertise in site reliability engineering?
What inspired Rich Burroughs to transition from engineering roles to community management?
How has Rich Burroughs' work at FireHydrant impacted the field of software reliability?
What are some unique challenges Rich Burroughs faced while working as a Senior Developer Advocate?
How does Rich Burroughs approach building effective technology communities?
Rich Burroughs
Add to my network

Location

Portland, Oregon