> Markdown version of [/videos/1519-empowering-thousands-of-developers-our-journey-to-an-internal-developer-platform?t=487](https://www.wearedevelopers.com/videos/1519-empowering-thousands-of-developers-our-journey-to-an-internal-developer-platform?t=487). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Empowering Thousands of Developers: Our Journey to an Internal Developer Platform

Zeiss united 6,000 developers without enforcing a single organizational mandate. Discover how their product-centric internal developer platform eliminated architectural fragmentation and drastically reduced engineering cognitive load.

- **Speakers:** [Bastian Heilemann](https://www.wearedevelopers.com/@bastian-heilemann), [Bruno Margula](https://www.wearedevelopers.com/@bruno-margula)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 29:26
- **URL:** https://www.wearedevelopers.com/videos/1519-empowering-thousands-of-developers-our-journey-to-an-internal-developer-platform

## Summary

Zeiss's transformation from a traditional optics brand into a diversified tech giant with over 6,000 developers working across embedded software, IoT, and AI brought severe architectural fragmentation and cognitive load. To solve this, the engineering leadership shifted toward a dedicated internal developer platform strategy. Instead of forcing a one-size-fits-all monolith, they adopted a "factory platform" mindset, balancing generalized enterprise standardization with specialized environments tailored for data analytics, generative AI, and web development.

To curb discovery issues and redundant work, the organization deployed a customized developer portal using Backstage. This portal acts as a single pane of glass, streamlining self-service onboarding, centralizing architecture decision records, and providing team-specific tech radars. For their MACH-based web application platform, they built a multi-tenant foundation on the Azure Kubernetes Service that abstracts infrastructure complexities like API management and observability. Crucially, adoption is driven by product-centric persuasion rather than organizational mandates, giving developers a paved path supported by dedicated site reliability engineering that they genuinely prefer to use.

Moving beyond initial deployment, the platform engineering team tackled the long-term reality of "Day 30" fleet management. By automating large-scale software updates and abstracting DevOps platforms, they seamlessly orchestrated an enterprise-wide UX library migration across 70% of diverse projects in just three weeks. Treating the developer experience as an evolving product—supported by Request for Comments, Wardley maps, and rich inner-source communities—drastically reduced the meeting-heavy culture of architectural alignment, proving that structured fleet management scales human engineering interactions just as effectively as the underlying code.

**Keywords:** internal developer platform, platform engineering strategy, backstage developer portal, developer cognitive load, fleet management automation, mach architecture, architecture decision records, self-service developer onboarding, azure kubernetes service, day 30 software operations, site reliability engineering, compliant ai model garden, micro-frontends migration, wardley mapping alignment, inner-source development, multi-tenant kubernetes

## Chapters

1. **Scale and diversity of software development teams** (00:05) — How a large optics and technology enterprise coordinates thousands of engineers across varied technical domains.
1. **Developer cognitive load and fragmented tooling challenges** (04:47) — Addressing the friction and delivery slowdowns caused by tool fragmentation, ownership boundaries, and shift-left expectations.
1. **Structuring platforms to standardize complex engineering environments** (08:07) — Layering self-service catalogs, fleet management, and architectural decision records into a unified developer portal.
1. **Specialized internal platforms for generative AI and data** (14:18) — Providing secure, compliant access to AI model gardens and centralized data governance frameworks.
1. **Architecture of the cloud native web application platform** (17:05) — Building a multi-region, Kubernetes-based framework that offers automated tenant provisioning and self-service deployments.
1. **Replacing legacy publishing with composable micro frontends** (22:51) — Integrating React-based micro frontends into existing content management systems to accelerate onboarding and deployment times.
1. **Automating fleet management and large scale codebase updates** (25:43) — Utilizing automated tooling to handle day-two operations like fleet-wide linting updates and user interface library migrations.

## Related Moments

- [Summarizing the organizational benefits of platform engineering](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) (from "Platform Engineering vs. DevOps Why not both?")
- [Pivoting product strategy toward platform engineering](https://www.wearedevelopers.com/videos/100122-how-agentic-devops-gave-us-dev-time-back) (from "How Agentic DevOps gave us Dev time back")
- [Designing internal developer platforms and product team responsibilities](https://www.wearedevelopers.com/videos/1614-ai-augmented-devops-with-platform-engineering) (from "AI-Augmented DevOps with Platform Engineering")
- [Platform engineering as the foundation for scaling AI tools](https://www.wearedevelopers.com/videos/100266-ai-won-t-fix-your-engineering-culture) (from "AI Won't Fix Your Engineering Culture")
- [Architecting the platform with modern cloud and mobile technologies](https://www.wearedevelopers.com/videos/64-shared-mobility-for-everyone) (from "Shared mobility for everyone!")
- [Scaling engineering teams using internal developer platforms](https://www.wearedevelopers.com/videos/100040-contract-testing-with-mcp-building-self-describing-self-testing-apis) (from "Contract Testing with MCP: Building Self-Describing, Self-Testing APIs")

## Related Articles

- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [How we Build The Software of Tomorrow](https://www.wearedevelopers.com/magazine/120-how-we-build-the-software-of-tomorrow)
- [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)
- [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)

## Related Jobs

- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Machine Learning Engineer](https://www.wearedevelopers.com/jobs/ext/1597388-machine-learning-engineer) at **ZEISS Group**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Platform Engineer - Mercury Runtime Platform](https://www.wearedevelopers.com/jobs/ext/293235-platform-engineer-mercury-runtime-platform) at **Raiffeisen Bank International AG**
- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Principal Product Manager, Agent Platform](https://www.wearedevelopers.com/jobs/ext/277541-principal-product-manager-agent-platform) at **GitHub**