Jerry Sayre
About Jerry Sayre
Jerry Sayre serves as the Chief Software Engineering Officer at Mutual of Omaha, where he has implemented cloud environments and streamlined software development processes. He has extensive experience in enterprise architecture and technical solution architecture, having held various leadership roles at Mutual of Omaha since 1998.
Current Role as Chief Software Engineering Officer
Jerry Sayre currently serves as the Chief Software Engineering Officer at Mutual of Omaha, a position he has held since 2018. In this role, he has implemented a cloud environment and integrated it into the DevOps CI/CD toolchain, which has streamlined software development processes. His leadership in this capacity focuses on enhancing the efficiency and effectiveness of software engineering practices within the organization.
Previous Experience at Mutual of Omaha
Jerry Sayre has extensive experience at Mutual of Omaha, where he held multiple roles over a span of nearly two decades. He served as the VP of Service, Marketing Support, & Solution Architecture Division from 2015 to 2018, and as the Principal Enterprise Architect from 2007 to 2012. Additionally, he worked as the Lead Technical Solution Architect from 1998 to 2007 and as the Director of I/S Enterprise Architecture Division from 2012 to 2015. His diverse roles contributed to the development and implementation of various technical solutions.
Education and Academic Background
Jerry Sayre studied at Bellevue University, where he earned a Bachelor's degree in Computer and Information Sciences from 2000 to 2001. Prior to that, he attended the University of Nebraska at Kearney, studying Computer Science from 1992 to 1995. His educational background provided a strong foundation for his career in software engineering and architecture.
Key Projects and Initiatives
Throughout his career, Jerry Sayre has led several significant projects that have improved operational capabilities. He successfully handled the acquisition and provisioning of 500 smartphones in just 12 hours as a contingency plan for a customer support outage. Additionally, he led the migration of multiple call centers from on-premises technologies to Amazon Connect, which enhanced customer support capabilities. He also integrated vendor and custom solutions into a cloud-based platform for a new insurance product.