HCL, providers, state, modules, workspaces, sentinel, tests, drift, IaC CI/CD.
Before starting, we run a 1-minute tech check — microphone, ambient noise, connection. If your setup isn't good enough, the test is fully refunded.
Prove your Terraform skills in 15 minutes — state management, module design, IaC CI/CD, and real-world incident recovery, not just copy-pasted apply commands.
The Plume Terraform badge certifies your ability to design, maintain, and scale infrastructure as code using Terraform in real professional settings. Over a 15-minute AI-conducted oral exam, you walk through your hands-on experience: managing state at scale, building reusable modules, integrating Terraform into CI/CD pipelines, handling state incidents and drift, and making reasoned decisions between workspaces and separate directory structures. The exam covers HCL, providers, remote backends, Terraform Cloud, Atlantis, and recent features like terraform test and stacks.
What sets this badge apart from a self-declared LinkedIn skill or a certification based on multiple-choice questions is the format itself: an unscripted oral conversation with an AI examiner that rephrases, digs deeper, and challenges your answers. Knowing the commands is not enough — you need to explain your architecture decisions, narrate real incidents you resolved, and defend your position on Terraform's actual limitations versus tools like Pulumi, CloudFormation, or Crossplane. The full transcript is then analyzed by Claude Opus, which produces a 0-100 score and a certified proficiency level.
This badge is designed for SREs, DevOps engineers, platform engineers, and cloud architects who use Terraform in production and want verifiable proof of that expertise. It's equally valuable for freelancers and consultants competing on technical credibility, and for developers transitioning into DevOps who want an objective benchmark of their IaC skills. Whether your stack runs on AWS, GCP, Azure, or a mix of custom providers, the exam adapts to your context.
Here are the concrete dimensions the AI examines during the 15-minute oral.
Mastery of expressions, built-in functions, dynamic blocks, locals, and complex constructs like for expressions and templatefile to write configurations that are both powerful and maintainable.
Remote backends (S3+DynamoDB, GCS, Terraform Cloud), state locking, state splitting by functional domain, terraform state mv/rm/import commands, and recovering from corruption, stuck locks, or significant drift.
Designing reusable modules with clean interfaces (typed variables, documented outputs, semantic versioning via public or private registries), and making deliberate choices between for_each and count.
Plan/apply workflows in GitHub Actions, GitLab CI, or Jenkins; Atlantis and Terraform Cloud for PR-based reviews; secure secrets handling with OIDC, Vault, or environment variables; and manual approval gates.
Making a reasoned case for workspaces vs separate directories based on project size and team structure, managing cross-state dependencies with terraform_remote_state or data sources, and the pipeline implications of each approach.
Integrating Sentinel or OPA for policy-as-code, running scheduled terraform plan for drift detection, and ensuring cloud credentials are never stored in plaintext within the state file.
Using TF_LOG for diagnostics, unlocking a stuck state with terraform force-unlock, rolling back a partial apply, and importing existing resources via terraform import or the native import block introduced in 1.5.
Comparing Terraform with Pulumi, CloudFormation, Crossplane, and CDK for Terraform. Forming an informed opinion on the OpenTofu fork, the BSL license change, and new features like terraform test and stacks.
Final scoring is performed by Claude (Anthropic), which reads back the full transcript and applies this weighted criteria grid.
Ability to explain Terraform's internal mechanics precisely: resource lifecycle, dependency graph, state behavior, provider initialization, and the distinction between plan and apply phases. Approximations and conceptual confusion are penalized here.
Quality and authenticity of the specific examples cited: state incidents handled, migrations led, modules designed. Candidates who stay abstract without referencing actual situations score lower on this dimension.
Ability to structure a Terraform codebase at scale: module decomposition, state strategy, environment management, versioning, and documentation. Choices must be justified and proportionate to the project context.
Mastery of integrating Terraform into automated pipelines, with specific attention to secrets handling, approval strategies, drift detection in production, and the tradeoffs between different automation tools.
Ability to compare Terraform with its alternatives, take a stance on the OpenTofu fork and BSL license, and identify scenarios where Terraform is genuinely not the right tool for the job.
A Plume session takes about 20 minutes, from tech check to badge delivery.
The AI confirms your mic is working and that you're in a quiet environment. No screen sharing, no code to type — this is a spoken exam. You can have notes nearby, but the AI is calibrated to detect when answers are being read rather than recalled.
You introduce yourself and describe your most recent or most complex Terraform project: codebase size, providers involved (AWS, Azure, GCP, Kubernetes...), and team context. This calibrates the depth of the questions that follow.
The AI moves through state management, module design, CI/CD integration, incident handling, multi-environment strategy, and ecosystem positioning. It follows up on your answers, probes fuzzy areas, and challenges your architectural decisions. Every answer can open a new thread.
The AI asks one or two big-picture questions: your take on OpenTofu, terraform test, or stacks, or a case where you would have chosen a Terraform alternative. This is your chance to show technical maturity and active engagement with the ecosystem.
Claude Opus analyzes the full transcript, assigns a 0-100 score and a proficiency level (Novice to Expert). You receive your digital badge with a shareable public URL, a detailed competency report, and access to your private audio recording.
Your score out of 100 translates into a level a recruiter can grasp at a glance.
You know the core commands (init, plan, apply, destroy) and have followed tutorials or contributed to an existing codebase without being the primary author. You understand what a provider and a state file are, but haven't handled incidents or designed modules from scratch.
You use Terraform autonomously on real projects: you've designed straightforward modules, manage a remote backend, and plug Terraform into a basic CI/CD pipeline. You can diagnose drift and have a solid understanding of the resource lifecycle and provider behavior.
You own the IaC architecture for a team or platform: versioned modules, state splitting, robust multi-environment strategy, Atlantis or Terraform Cloud integration, secrets management via OIDC or Vault. You've handled state incidents in production and are comfortable with dynamic blocks and complex expressions.
You design enterprise-scale IaC frameworks, build custom providers or public modules, implement Sentinel or OPA for policy-as-code, and hold well-argued opinions on OpenTofu, Terraform stacks, and the tradeoffs against Pulumi or Crossplane. You mentor and upskill other engineers on Terraform.
No degree or years of experience required to take the badge. Here are the profiles it makes the most sense for.
You use Terraform daily but that expertise is invisible to anyone outside your team. The badge turns hands-on mastery into a concrete, shareable proof point for your manager or your next recruiter.
You design cloud infrastructure and Terraform is your primary IaC tool. The badge validates your ability to think about infrastructure at scale, well beyond provisioning isolated resources.
You build the internal infrastructure that other teams consume. The badge signals that you think in modules, clean interfaces, versioning, and developer experience, not just local apply runs.
When you pitch for a contract or negotiate your day rate, a verified Terraform badge carries far more weight than 'Terraform' listed under skills on your LinkedIn profile.
You're learning Terraform seriously and want an objective signal of where you stand, plus a credible proof of your IaC upskilling for recruiters who have no other way to verify it.
Where and how your Terraform badge will help you day to day.
You're interviewing for a senior DevOps role. Instead of waiting for a live Terraform coding exercise, you share your badge with the recruiter beforehand. Your score and report do the talking before the first call.
You're pitching for a high-value IaC engagement. The Terraform Expert badge lets you back up your day rate with third-party verified proof, and skip the ad hoc technical screening the client would otherwise run.
You've completed a Terraform training program and want to know if you're actually production-ready. The Plume oral gives you precise feedback on your gaps (state splitting, secrets handling, module design at scale) before you make expensive mistakes.
You're going after a lead DevOps or platform engineer role at your company. The badge gives your manager an objective, external assessment of your Terraform mastery to complement your case during your performance review.
You add the badge URL to the README of your open-source Terraform module or to your GitHub profile. Visitors and potential contributors immediately see verified proof of your credibility on the subject.
You're a hiring manager recruiting a DevOps engineer. You ask candidates to complete the Terraform badge before the panel interview, giving you comparable objective scores instead of subjective CV impressions and saving two rounds of filtering.
A few minutes to check you have everything you need.
At the end of your session you don't just get a score — here's everything that awaits you.
You get a precise score and a proficiency level (Novice to Expert) produced by Claude Opus after analyzing your transcript. The result reflects your actual Terraform mastery, not a self-assessment.
A full report identifies your strengths (modules, state management, CI/CD...) and your growth areas across each evaluated dimension. Ideal for planning your next step in the IaC learning curve.
Your oral exam recording is stored privately and accessible only to you. You can replay it to analyze how you articulate complex technical concepts and tighten your explanations.
A public, verifiable URL you can drop on LinkedIn, in your CV, on GitHub, or in a client proposal. Anyone who clicks it sees your certified Terraform score and level instantly.
Discover related skills you can validate with Plume.
A 15-min oral exam with an AI, a shareable badge for your recruiters.
Choose this badge · €19.99
