[I’ve been meaning to write this post for several months]
Earlier this year I changed roles within Red Hat. My new role is “OpenShift SaaS Architect”, and organizationally is part of Red Hat Service Delivery.
Service Delivery encompasses:
- SRE teams that design, build and operate Red Hat OpenShift Dedicated and Azure Red Hat OpenShift
- Development teams responsible for cluster and account management microservices behind cloud.redhat.com
- SRE teams that run core OpenShift Container Platform infrastructure (such as Cincinnati, Telemeter, try.openshift.com and many more).
- Teams building OperatorHub.io tooling, certification programs and Operator SDK training (delivered dozens of Operator trainings for our customers)
Basically, if you’ve had any interaction with OpenShift 4, you’ve likely consumed those services.
I’d been in my previous role for 7 years, and celebrated my 10th anniversary at Red Hat by being acquired by Big Blue. My previous team (Red Hat Performance and Scale) afforded me endless technical challenges, opportunities to travel, present, help shape product and build engineering teams from the ground up. Perhaps most importantly, I had the opportunity to mentor as many Red Hatters as I possibly could.
Red Hat Service Delivery allows me to broaden my technical and architecture skill set to areas outside of performance, scale and optimization, while letting me apply the many hard-fought lessons from prior chapters in my career.
Hopefully $subject makes a bit more sense now. Onward!
Jeremy Eder's Blog 