Success at Scale: Building a Platform Organization through Rebranding and Realignment
summary
Eighteen months of platform work at CLEAR reduces operational complexity by consolidating Kubernetes under infrastructure, creating an application platform team with deep Java expertise, and launching an SRE function; teams rebrand to Developer Experience and unify reactive support into a single Slack channel backed by on‑call leads. Outcomes include a full rearchitecture of core frontend/backend/hardware, three new lines of business launched, measurable developer efficiency gains, improved observability and security hygiene, and lower overall cloud and SaaS spend.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 3:58Before and after platform maturity
- 8:10Key strategy and platform model
- 13:15Reducing sociotechnical complexity
- 18:09Platform ownership model changes
- 22:01Abstraction in platform interfaces
- 26:17Alignment and engineering goals
- 29:31Visibility and accountability
related talks
26mLessons Learned from 7 years of Running Developer Platforms
46mBeyond DevOps: How and Why Companies Converge on Platform Models
21mScaling Platform-as-a-Product Without Losing Your Mind - Eline Henriksen & Jakub Pawelczak
13mWhat To Do When SRE is Just a New Job Title?
21mDriving Platform Adoption: Embedded SRE
27mTurning Platform Engineering Work Into Business Value Leadership Understands
33mPlatform as a Product - Transforming from Service Delivery into Continuous Operations
32mStarting and Scaling a Platform Engineering Team