How to Build a Platform Engineering Team [Structure & Roles]

Platform engineering is slowly becoming the de-facto standard for managing your software development and operations activity. As organizations grow and continue to adopt cloud-native architectures and microservices, the complexity of managing the underlying infrastructure grows significantly.

In this post, we will talk about how to build a successful platform engineering team and what you should consider when hiring engineers.

What we will cover:

1. Platform engineering focus areas
2. Platform engineering roles
3. Hiring the right talent
4. Onboarding, goals, and training

Platform engineering focuses on the following areas:

• Infrastructure as code – Using tools such as OpenTofu, Terraform, Pulumi, and AWS CloudFormation to automate, build, and scale your infrastructure
• Configuration management – Automatically configure your infrastructure after it is provisioned.
• Continuous integration and delivery – Integrate code changes, lint checks, vulnerability scans, build, tests, and deploys.
• Container orchestration – Orchestrate your microservices applications.
• Monitoring and observability – Maintain the health and performance of your application.
• Security and compliance – Ensure your platform respects industry standards and regulations and your users’ information is safe.
• Infrastructure management platforms – Easily integrate all focus areas with a single product.

See also: Top 20 Platform Engineering Tools

A platform engineering team often includes roles such as platform engineers, site reliability engineers, cloud architects, and security engineers. Other roles might include DevOps engineers, automation engineers, and quality assurance engineers.

When platform engineering is implemented, the most common split for the infrastructure team is between platform engineers and site reliability engineers. Usually, at least one cloud architect assists the platform team with the platform’s architecture and design. A dedicated security team also assists with everything related to security, governance, and compliance.

Platform engineers

Platform engineers are responsible for designing, building, and maintaining the platform infrastructure:

Choosing the right platform engineers is key to the successful implementation of the platform. You need to find engineers who are automation-first, demonstrate strong problem-solving skills, and can collaborate effectively with other teams. They should be proficient in a programming language such as Golang, Python, TypeScript, or JavaScript.

Site reliability engineers

Site reliability engineers (SREs) handle deployments to superior environments, are experienced in incident management and response, and have strong problem-solving skills.

The best people for SRE positions have a good grasp of distributed systems and cloud-native architectures and are keen to continuously improve the performance of the systems they manage. They should also have a solid understanding of scripting and automation

Cloud architects

Cloud architects should be experts in designing platforms and ensuring the platform architecture is resilient and satisfies all the organization’s needs.

When selecting a cloud architect, look for candidates who have extensive experience in designing and implementing cloud infrastructure solutions in different cloud providers. They should be able to enforce architectural standards and best practices and collaborate extensively with other teams.

Security engineers

Security engineers work hand in hand with platform engineers and cloud architects to implement and maintain the security best practices for the platform:

The best security engineers can enforce security best practices and are aware of industry standards and regulations (GDPR, HIPAA, etc). They should work regularly with all teams involved in the platform and ensure vulnerability scanning is implemented for everything.

The many steps involved in hiring the right talent to build a platform engineering team start with the job description.

Tips for creating a good job description

Most contemporary IT jobs have many requirements. It is extremely difficult to find engineers who excel in all the areas a platform engineer activates, and that’s why you need to create focused jobs. For example, if your platform uses AWS, Terraform, Kubernetes, GitHub Actions, and Ansible, you should expect all applicants to know something about these tools but not to be experts in all of them.

If you have to hire four platform engineers for this tech stack, you should create focused jobs such as:

• Platform engineer – Terraform focus
• Platform engineer – Kubernetes focus
• Platform engineer – CI/CD focus
• Platform engineer – Ansible focus

In the focused job description, you should require the engineer to be an expert in the focused tool and have extensive experience with at least one, as well as some experience with others.

If you don’t offer focused jobs, at least ensure that the job description specifies that engineers don’t need to be experts in all technologies. Otherwise, some good candidates might not even apply.

Another important aspect of creating a job description that attracts top talent is to specify what the company does, the way the collaboration will be implemented, and the perks and benefits of joining your company.

In addition, it is really important to outline the necessary qualifications (education, years of experience, certifications) you require from the engineers applying for the job. These need to be realistic — at one point, FastAPI’s creator couldn’t apply for a role that required FastAPI experience because the number of years of experience required exceeded the number of years the tool had existed. Be realistic and do your research when you are creating job descriptions.

Tips for creating a good interview process

The interview process is crucial for evaluating a candidate’s technical competencies and cultural fit, so structuring an interview effectively will make the difference between hiring the right people for the job:

Hiring the right talent is very important, but retaining talent is also crucial. Many things can go wrong when you are hiring a new team member, so let’s explore a couple of things that you can do to improve your retention.

Without proper onboarding, some engineers can get frustrated and be tempted to leave within the first three months. This costs money in terms of hiring costs and can also impact team morale and productivity. 

A good onboarding process includes, at minimum, an orientation meeting (company overview, mission, values, team introduction, and what portals to use for different kinds of requests) and a technical onboarding meeting in which a colleague (a buddy) explains the tools used and presents the kind of access the new colleague should have. Regular check-ins are needed to discuss progress, address any challenges, and provide feedback to help identify and resolve issues early on, thus minimizing frustration.

Monthly, quarterly, and yearly goals should be set for the new hire from the beginning of their tenure. This is important because it clarifies to the new engineer what is expected from them and what they can do to exceed the expectations you’ve set. Setting clear, achievable goals (check out SMART goals here) provides direction and motivation, helping new hires stay focused and engaged.

Training is another important aspect an engineer will be interested in. Having access to LinkedIn Learning, Pluralsight, or Udemy, can significantly enhance their skills and keep them updated on the latest industry trends and technologies. By offering access to platforms like these, you will demonstrate your organization’s commitment to your team’s professional development of your team. Offering two or three hours of training per week will encourage your engineers to improve.

Spacelift offers all the mechanisms required to build a successful platform. Apart from being the product you can easily leverage in step 7 of how to implement platform engineering, by checking the website, documentation and blog posts, all the other steps can be facilitated.

Let’s explore how Spacelift can help.

1. Policies

With policies, you can control what kind of resources people can create, what kind of parameters these resources can have, build custom policies for third-party tools you integrate into your workflow, control how many approvals you need for runs, and more:

In the above example, we are enforcing a couple of mandatory tags for our resources (Name, env, and owner).

2. Stack dependencies

With stack dependencies, you can build dependencies between your configurations, and even share outputs between them. You don’t have any constraint to the number of dependencies you want to create, and whenever a parent configuration finishes a run successfully, it will trigger runs to its children. As Spacelift supports multiple infrastructure tools, you can build dependencies between them, so a parent stack can use OpenTofu for example, and a child stack can use Kubernetes.

3. Blueprints

Blueprints enable you to configure every aspect of your stack, including governance and compliance. With blueprints, you can create self-service infrastructure, and by this your developer velocity will increase considerably.

4. Cloud integrations

Static credentials are easily intercepted and can be used with malicious intent. Spacelift understands that, so it offers you the ability to integrate natively with AWS, Microsoft Azure, and Google Cloud to generate dynamic credentials. Based on the roles you are using, these integrations can offer as few or as many permissions as you want:

5. Spaces

Spaces help you implement RBAC, and give partial admin rights to your users.

In the above example, if you give a user admin rights to the resources space, and no other rights, he will have all permissions to the resources and production space, but he won’t be able to even view resources in other spaces.

6. Contexts

Contexts are logical containers that can be shared between multiple configurations and contain environment variables, mounted files, and lifecycle hooks, making it easier to ensure reusability and idempotency.

7. Drift detection and optional remediation

Infrastructure drift can be one of the worst problems you can have because if, for example, you fix something manually and then apply the code again at a later time, you will reintroduce the bug into your configuration.

Spacelift offers a drift detection mechanism that runs a schedule that informs you about drift and can optionally remediate it:

8. Resources view

With Spacelift, you can see all the resources that have been deployed into your Spacelift account (based on the permissions you have), details about them and their health:

Building a successful platform engineering team involves planning across multiple stages, starting with defining what your platform looks like, crafting job descriptions, defining the interview processes, and implementing effective retention strategies.

By setting clear goals, fostering a culture of collaboration, and implementing training programs, you can ensure your platform team’s success.