Hire CloudFormation Developers With a Structured Scorecard
Define the work, required evidence, and interview criteria before sourcing CloudFormation Developer candidates. This guide turns the role into a consistent, auditable hiring process.
Establish whether the hire will write new stacks, manage a large existing template library, or move the team to a higher-level tool like the AWS CDK. Then judge candidates by how they handle risky changes: reading change sets, protecting stateful resources, resolving drift, and splitting large templates into manageable pieces.
CloudFormation roles differ in template size, how many accounts and regions stacks span, and whether teams author YAML directly or generate it from code. Use this guide to define the environment first, then compare candidates by how safely they change infrastructure that is already serving traffic.
What CloudFormation Developers do day to day
The core work of the role, before tools and titles. Check that your brief, your interviews, and your scorecard all cover it.
Write CloudFormation templates or CDK code for AWS infrastructure
Manage stacks, change sets, and drift
Structure templates with nested stacks and parameters
Integrate infrastructure changes into CI pipelines
Skills to look for in CloudFormation Developers
Group requirements by area so the job post, the interview plan, and the scorecard test the same things.
01
CloudFormation
Templates, change sets, nested stacks, and StackSets.
02
AWS CDK
Infrastructure defined in TypeScript or Python.
03
Workflow
Linting, testing, and deployment pipelines.
Which specialization do you need?
Most CloudFormation Developers lean toward one of these. Name the one you need in the brief instead of listing every tool.
Multi-account setups
StackSets and landing zones.
CDK adoption
Moving templates to CDK.
Terraform migration
Moving between tools.
CloudFormation role levels and evaluation evidence
Adjust the scope to the actual job. Seniority should reflect decision ownership and system complexity, not years alone.
1
Junior
Typical scope
Entry-level profile with a strong foundation in basic YAML/JSON template writing, stack deployment via console, and parameter passing.
Knowledge areas
YAMLJSONInfrastructure as CodeStack Deployment
What to look for
Ability to define standard AWS resources (EC2, S3, VPC) declaratively. Experience deploying simple stacks and reading CloudFormation event logs.
2
Mid
Typical scope
Mid-level profile with proven expertise in change set review, IAM least-privilege enforcement, and cross-stack reference management.
Deep expertise resolving configuration drift to return production stacks to IN_SYNC status. Architectural ability to orchestrate complex dependencies via nested stacks and Lambda custom resources.
What should a CloudFormation Developer role brief include?
Describe the AWS accounts, existing stacks, and how updates are approved and run. Say who owns shared templates and cross-stack dependencies. Treat template syntax as quickly learnable; make safe update practice, deletion protection, parameter design, and recovery from failed stack operations the required core.
Accounts, regions, and the number and size of existing stacks
Authoring style: raw templates, AWS CDK, or a mix of both
Update process, including change set review and who approves production changes
Stateful resources that need deletion protection and special update handling
How should CloudFormation Developer candidates be compared?
Give each candidate the same template change that would replace a database if applied naively, and ask what they would do. Strong candidates inspect the change set, use retention and deletion policies, stage the update, and know how to recover a stack stuck in a failed rollback state.
Interpret a change set and identify resources that will be replaced
Explain how they would split a large template using nested stacks or exports
Describe handling of drift without deleting live data
Use identical scoring for safety, structure, and clarity across candidates
What to probe when interviewing CloudFormation Developer candidates
These are risks a weak hire in this role tends to bring. Turn each into a work-sample task or follow-up question that produces evidence for or against it, and score every candidate on the same set.
Can they programmatically resolve configuration drift without deleting critical production databases?
Do they know how to modularize massive templates using nested stacks and cross-stack references?
Can they write custom Lambda resources for unsupported AWS configurations during stack execution?
Job description template
A starting draft built from this guide. Replace the bracketed parts, cut anything that does not apply, and keep every requirement tied to the work.
Job description template
About the role
[Two or three sentences on the product, the team, and why this role is open now.]
What you will do
Write CloudFormation templates or CDK code for AWS infrastructure
Manage stacks, change sets, and drift
Structure templates with nested stacks and parameters
Integrate infrastructure changes into CI pipelines
What you bring
CloudFormation: Templates, change sets, nested stacks, and StackSets.
AWS CDK: Infrastructure defined in TypeScript or Python.
Workflow: Linting, testing, and deployment pipelines.
Nice to have
Multi-account setups
CDK adoption
Terraform migration
Level and scope
Junior: Entry-level profile with a strong foundation in basic YAML/JSON template writing, stack deployment via console, and parameter passing.
Mid: Mid-level profile with proven expertise in change set review, IAM least-privilege enforcement, and cross-stack reference management.
Senior: Senior profile with deep mastery of state configuration drift detection and remediation, custom resource orchestration, and nested stack abstraction.
How we hire
A structured interview and a short work sample, scored against the same criteria for every candidate.
Full-time, contract, or freelance?
CloudFormation is usually part of an AWS DevOps role. A contractor fits a CDK migration or a template cleanup. Hire full-time when you manage many AWS accounts with shared infrastructure.
FAQ
Frequently Asked Questions About Hiring CloudFormation Developers
Direct answers for role definition, evaluation, specialist depth, and compensation research.
What does a CloudFormation developer do?
They define AWS infrastructure as templates and run it as stacks: networks, compute, databases, permissions, and supporting services. The role covers authoring and reviewing templates, managing parameters and outputs, sequencing updates, detecting drift, and organizing stacks across accounts and regions, sometimes through CDK or custom resources.
Which CloudFormation skills matter in interviews?
Test template structure, parameters, conditions, intrinsic functions, outputs, and cross-stack references. Then check change sets, rollback behavior, deletion policies, drift detection, and IAM design. Senior candidates should discuss nested stacks, custom resources backed by Lambda, StackSets, and the trade-offs of using CDK on top.
How do I fairly assess a CloudFormation candidate?
Present a template with a few hazards, such as a hard-coded name that forces replacement or a database without a retention policy, and ask for a review. Add a scenario about a failed update. Use the same prompt and scoring guide for everyone, and write down the specific evidence behind each rating.
Should I hire a CloudFormation specialist or an infrastructure engineer?
If your estate is fully AWS and built on CloudFormation or CDK, a specialist can improve template structure and update safety. A broader infrastructure engineer is better when you use several clouds or tools. Many strong candidates know both CloudFormation and Terraform, so ask about transferable practices.
How do I set a pay range for CloudFormation work?
Compensation depends on seniority, AWS depth, scope across accounts, and whether the role includes on-call or security duties. Search recent postings and salary data for your own location, date the range you build, and record sources. Refresh the local market view before each offer.
Teams hiring CloudFormation specialists typically need IaC tooling, deployment pipelines, security scanning, and infrastructure automation across the AWS ecosystem.
ConnectDevs can support discovery and structured interview workflows, but the hiring team remains responsible for the role definition, evidence standard, final decision, compensation validation, and applicable legal review.