Platform Engineering at GitHub: A Q&A Guide to Solving Infrastructure Challenges

Platform engineering is a specialized discipline within software development that focuses on building and maintaining the foundational tools and systems that product engineers use to create user-facing features. At GitHub, platform engineers ensure that internal teams have the infrastructure, libraries, and frameworks they need to deliver reliable and scalable products. This Q&A explores key lessons learned by GitHub engineers as they transitioned from product to platform roles, using the analogy of building Gundam models to illustrate the shift in mindset and skills required.

1. How do product engineers and platform engineers differ in their roles?

Imagine building a Gundam model kit. Product engineers are like the builders who assemble the kit using all its pieces to create a finished, functional model that can be displayed or played with. They focus on delivering a complete, user-facing product. Platform engineers, on the other hand, are the engineers who supply the tools—clippers, files, and even a display stand—and ensure that the builder has everything they need. They don't necessarily build the Gundam themselves, but they create and maintain the infrastructure that makes building possible. At GitHub, product engineers directly tackle external customer problems (e.g., building deployment views), while platform engineers serve internal customers by providing reliable tools, APIs, and systems that empower product teams.

2. What prompted a GitHub team to shift from product to platform engineering?

About a year ago, a GitHub team moved from the product side to the infrastructure organization. This transition meant inheriting new roles and Areas of Responsibility (AoRs). Previously, the team had focused on external customer problems, such as building deployment views across different environments—work that involved direct interaction with users who rely on GitHub for their industries. After the move, their customers became internal: other GitHub developers and teams. This changed the nature of their work from constructing user-facing features (like assembling a Gundam kit) to building the components that make up the kit itself. Adapting to this new internal focus required the team to rethink their approach to code testing, problem-solving, and collaboration.

3. Why is understanding the domain critical for platform engineers?

Before solving any platform problem, engineers must thoroughly understand the domain—the business and technical subject area their team and organization operate within. This includes learning technical terms, how systems interact, and the constraints they impose. Without this understanding, solutions may be inefficient, brittle, or misaligned with actual needs. For platform teams, domain knowledge is even more vital because they serve as the foundational layer for all other engineering work. A deep grasp of the domain enables platform engineers to design tools that are fast, reliable, and scalable. It also helps them anticipate future demands and avoid building redundant or incompatible systems.

4. What are three practical methods for getting up to speed in a new domain?

GitHub engineers recommend three key approaches: talk to your neighbors, investigate old issues, and read the docs. First, arrange a handover meeting with a team that has more experience in the subject. This is a chance to ask about terminology and gain deeper context on the problems at hand. Second, look through the backlog of issues—both stale and persistent ones. They reveal current system limitations and potential improvements. Finally, read the documentation thoroughly. Documentation is a goldmine that explains how the system works, its architecture, and common patterns. These steps collectively build a solid foundation of domain knowledge before any coding begins.

5. Which platform-specific skills are essential beyond general engineering knowledge?

While general software engineering skills apply to both product and platform teams, platform engineers need deeper expertise in certain areas. Networks: a solid understanding of network fundamentals—such as TCP/IP, DNS, load balancers, and security groups—is crucial because platform tools often interact with network infrastructure. Databases: knowledge of database design, query optimization, and replication helps when building scalable storage solutions. Operating systems: familiarity with OS concepts like process management, memory, and file systems aids in optimizing runtime environments. Additionally, platform engineers must master observability (monitoring, logging, tracing) to ensure system reliability. These skills allow them to build the robust foundation that product engineers rely on daily.