Talk at PlatformCON

This track will showcase talks from speakers who have built an internal developer platform (IDP) with their team. They will discuss challenges and benefits of building an IDP, showing how to make modern tech and infrastructure available for developers, boost developer productivity and enable developer self-service. 

Typical questions to answer in a platform story talk:

• Why and how did you build your platform?
• Which challenges did you come across, how did your team overcome them?
• What’s the impact of the platform you built?

Ideally, the talk covers technological as well as cultural and product design aspects. If your talk has a strong focus to either one of the three fields, no problem at all, just submit it to Platform Tech, Platform Design or Platform Culture.

This track will be all about the underlying technologies used to build your platform or that integrate with it. Talks can be about certain approaches, platform tools or toolchains, related challenges and solutions. Typical technologies and approaches can be: Kubernetes, cloud native CI/CD, Infrastructure as Code (IaC), GitOps, etc.

Typical questions that can be discussed in a Platform Tech talk:

• How to build a self-service layer on top of a Kubernetes setup?
• What are the key technological challenges of migrating to a new setup (e.g. IaC, GitOps, etc.)?
• How do you integrate security and observability into your IDP?
  

This track is focused on the Platform as Product mindset. How to design a platform that engineers really love working with. Talks will cover Developer Experience, how to provide the right level of abstraction, how to reduce cognitive load and how to design your platform so that it enables developer self-service. Speakers will also discuss how to deal with interface design (API, UI or CLI), self-documentation, workflow design and the main challenges of product management for platform engineering.

Typical questions that can be discussed in a Platform Design talk:

• How to work with developers to find the right level of self-service and abstraction?
• How to build a successful internal platform team and treat internal tooling as a product?
• Which is the right interface for a given development team?
  

No platform lives for itself. It is built by humans for humans and has deep cultural implications. Introducing a platform often requires change management across the entire organisation. Very frequently, launching an internal platform is only one building block of an organisation’s transformation strategy.

Typical questions that can be discussed in a Platform Culture talk:

• How to get stakeholder buy-in for your platform project (e.g. management, but also developers, operations or security teams)?
• How to build a high performing platform team?
• How to roll out a platform across an organisation (incl. training, onboarding)?