Platform Engineering — Internal Developer Platforms
A three-day Platform Engineering course focused on the platform as a product: Team Topologies, golden paths, measuring developer experience (DevEx), and an organizational rollout roadmap — from strategy to adoption, independent of any single tool.
The platform as a product, not a pile of scripts
Platform Engineering evolved out of DevOps as a response to the cognitive overload development teams faced managing increasingly complex infrastructure on their own. The course treats the Internal Developer Platform as an internal product with its own customers (development teams), a value proposition, and a roadmap — not as a one-off infrastructure project.
Team Topologies as an organizational map
Instead of ad-hoc structures, the course uses the Team Topologies model to design the interactions between the platform team and stream-aligned teams. Participants learn how to design a platform that supports team autonomy instead of creating a new bottleneck.
From pilot to organization-wide adoption
The final module focuses on a practical rollout roadmap — how to measure developer experience, how to communicate platform value to business stakeholders, and how to scale adoption from a pilot team to the entire organization.
Benefits
- Design a platform as a product with a clear value proposition for development teams
- Apply the Team Topologies model to design a platform team and its interactions with stream-aligned teams
- Build golden paths — paths of least resistance for the most common developer tasks
- Measure developer experience (DevEx) and build a platform adoption roadmap for the organization
Who is this training for?
Prerequisites
- Experience working with Kubernetes or cloud infrastructure
- Familiarity with DevOps fundamentals and CI/CD processes
Training program
Platform Engineering as a paradigm, not a tool
- The origins of the Platform Engineering movement — a response to DevOps cognitive overload
- Platform as an internal product: customers, value proposition, roadmap
- An overview of the tooling ecosystem (Backstage, Kratix, Humanitec) without tying to one
- When to build a platform, and when it is premature optimization
Team Topologies and organizing the platform team
- The four team types per Team Topologies and how they apply to platform engineering
- Interactions between the platform team and stream-aligned teams
- Avoiding the platform becoming a bottleneck — self-service as a design goal
- Platform team structure: platform product manager, platform engineers
Golden paths and self-service infrastructure
- Designing golden paths for common tasks: new service, deployment, provisioning
- Service catalog and templates as a mechanism for scaling good practices
- Balancing team freedom with platform standardization
- Versioning and evolving golden paths without breaking existing services
Measuring DevEx and an organizational rollout roadmap
- Developer experience metrics: time-to-first-deploy, cognitive load, team satisfaction
- Building a platform rollout roadmap — from pilot to organization-wide adoption
- Communicating platform value to business stakeholders
- Maintaining and evolving the platform as a product over the organization's lifecycle
Delivery Methods
Online
- Convenience of participating from anywhere
- Interactive live sessions with trainer
- Materials available for 30 days
- No travel costs
On-site
- Direct contact with trainer and group
- Intensive hands-on workshops
- Networking with other participants
- Full focus on learning
Frequently asked questions
How is this different from Platform Engineering — Building an Internal Developer Platform and Platform Engineering — IDP and Backstage in our catalog?
Those two courses focus on building a specific platform as a tool — a service catalog, golden paths, and in the second case specifically Backstage (Spotify) as an implementation. This course approaches Platform Engineering from an organizational perspective: platform as an internal product, the Team Topologies model for designing the platform team, DevEx metrics, and an organization-wide adoption roadmap — a strategic workshop, not a tool tutorial.
Do I need to know Backstage to attend this course?
No. The course is tool-agnostic — we present the ecosystem (Backstage, Kratix, Humanitec) as context, but the learning focuses on the principles of designing a platform as a product, which carry over to whatever tool your organization chooses.
How do I measure whether a platform is actually improving team productivity?
The key metrics are time-to-first-deploy (how quickly a new team can ship its first service), reduced cognitive load (the number of tools and steps required to deploy), and team satisfaction measured via regular DevEx surveys. The course shows how to build such a metrics dashboard from scratch.
What is the optimal starting size for a platform team?
Per Team Topologies, a platform team should be small enough to maintain a clear value proposition and avoid becoming a bottleneck — usually 3-5 people to start, growing with the number of stream-aligned teams it serves. The course shows patterns for scaling the team as platform maturity grows.
Request a quote
Funding Options
Check funding options for your company
Development Services Database
An instrument for micro, small and medium-sized companies — check whether it applies to your organisation
Check availabilityNational Training Fund
An instrument for employers — we help you check whether it can be applied
Learn moreTrusted by
We train teams at Poland's largest companies
Interested in this training?
Contact us - we'll prepare an offer tailored to your organization's needs.