Playbooks, roles, inventories, variables, vault, collections, idempotence, Tower/AWX.
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.
Show recruiters and clients you actually know Ansible — playbooks, roles, idempotence, Vault and AWX stress-tested in a 15-minute AI oral exam.
The Plume Ansible badge is a 15-minute oral exam conducted by an AI examiner that probes your real-world Ansible skills. This is not a multiple-choice quiz: you talk through how you structure multi-environment inventories, how you enforce idempotence when shell or command is your only option, how you design reusable roles and ship collections to Automation Hub. Your transcript is then scored by Claude Opus, which produces a 0-100 result and a certified level: Novice, Proficient, Advanced, or Expert.
Why does this badge carry more weight than listing 'Ansible' on LinkedIn? Because anyone can type a keyword. The oral exam forces you to justify your decisions: why group_vars over host_vars in this specific case, how Ansible fits alongside Terraform in your GitLab CI pipeline, when you would have reached for Puppet or Salt instead. The AI scores technical precision, the ability to reason about Ansible's real limits at scale, and how you handle production failures — not just happy-path knowledge.
This badge is built for DevOps engineers, SREs, sysadmins, and cloud architects who run Ansible in production and want a clear, verifiable signal of their level. It is particularly valuable if you are applying for a role that lists Ansible as a hard requirement, pitching a freelance contract, preparing for the RHCE (EX294) exam, or simply want an honest benchmark before stepping into a new position.
Here are the concrete dimensions the AI examines during the 15-minute oral.
Designing and maintaining static and dynamic inventories (AWS EC2, Azure, GCP plugins), using group_vars and host_vars consistently across dev, staging, and production environments.
Writing plays, tasks, handlers, tags and blocks with proper error handling via ignore_errors, failed_when and rescue to keep runs reliable when things go sideways in production.
Enforcing idempotence even when using the shell, command or raw modules through changed_when, creates/removes, and check_mode for safe dry-runs with zero side effects.
Designing reusable roles following the Ansible Galaxy directory layout, versioning and publishing them to Galaxy or a private Automation Hub, and knowing when a collection is the right abstraction.
Encrypting sensitive variables with ansible-vault (encrypt_string, encrypted files, multiple vault-ids) and integrating HashiCorp Vault via the hashi_vault lookup plugin.
Wiring Ansible into pipelines alongside Terraform, GitLab CI, Jenkins or GitHub Actions, consuming dynamic cloud inventories, and managing inter-tool dependencies at scale.
Administering Red Hat Automation Platform or AWX: job templates, multi-level workflows, RBAC, execution environments, ansible-navigator and centralized credential management.
Critical analysis of where Ansible shows its limits at scale (SSH fan-out performance, lack of native state management) and when Salt, Puppet, Chef or cloud-native tooling is the better call.
Final scoring is performed by Claude (Anthropic), which reads back the full transcript and applies this weighted criteria grid.
Correctness of the concepts you reference: core modules, task options, handler behavior, Jinja2 templating, play keywords. The AI flags confusions, approximations and outdated claims.
Quality and credibility of the concrete examples you bring: inventory scale, actual complexity of the playbooks described, production incidents managed, architecture decisions explained.
Ability to explain why one choice over another: Ansible vs Terraform, role vs collection, shell vs native module. Critical thinking counts as much as raw knowledge of the tool.
Awareness of established patterns: recommended directory structure, using Molecule to test roles, linting with ansible-lint, consistent tagging, and safe secrets handling workflows.
Understanding of recent structural shifts: the ansible-core/collections split, Tower to AWX/AAP migration, execution environments, ansible-navigator, and deprecated legacy modules.
A Plume session takes about 20 minutes, from tech check to badge delivery.
The AI verifies your microphone and audio quality, then walks you through the format. No stress here: it is just to make sure the recording will be usable for scoring.
You describe your Ansible background: your most recent or complex project, the inventory size, what you automated and in what infrastructure context (bare-metal, cloud, hybrid).
The AI probes the key dimensions: multi-environment inventory design, idempotence with non-idempotent modules, roles and collections, CI/CD integration, Vault secrets management, Tower/AWX administration, and Ansible's limits compared to its alternatives.
The AI asks when you would actively steer away from Ansible, and gives you a chance to add anything relevant the interview has not yet covered.
Claude Opus analyzes the transcript and produces a 0-100 score, a certified level, and a detailed written report. Your Ansible badge is available within a minute of the exam ending.
Your score out of 100 translates into a level a recruiter can grasp at a glance.
You understand basic YAML playbook syntax and can run simple tasks (copy, file, apt, yum) against a static inventory. You have limited experience with roles, advanced variable precedence or managing multiple environments in a single Ansible project.
You manage multiple environments using group_vars and host_vars, use handlers, tags and ansible-vault for secrets, and have written working roles. You can debug a failing production run and understand why idempotence matters in practice.
You design reusable roles tested with Molecule, publish collections to Galaxy or a private Hub, integrate Ansible into CI/CD pipelines with dynamic cloud inventories, and are comfortable with execution environments and ansible-navigator.
You administer Red Hat Automation Platform or AWX at scale (RBAC, multi-level workflows, credential management), contribute to open-source collections, reason sharply about Ansible's limits versus Terraform or Salt, and lead Tower-to-AAP migrations.
No degree or years of experience required to take the badge. Here are the profiles it makes the most sense for.
You run Ansible in production daily and want an objective, verifiable signal of your level to use in interviews, salary negotiations or team discussions.
You automate patching, user management and deployments with Ansible and want to confirm your practices are in line with current industry standards.
A verifiable Ansible badge strengthens your pitch to clients who ask you to prove your level without being able to audit your private commit history.
You are learning Ansible hands-on and want an honest benchmark to know whether you are ready for a first automation-focused role before sending out applications.
You need to assess Ansible skills across your team, or you want to back up your own IaC architecture decisions with a credible third-party signal in a multi-tool context.
Where and how your Ansible badge will help you day to day.
A job listing names Ansible as a hard requirement. You share your badge URL with your score and certified level, saving the recruiter from running a custom technical screen and speeding up the hiring process.
A CTO is choosing between two consultants at the same day rate. Your Advanced Ansible badge settles it: it proves you can handle complex multi-environment inventories and wire Ansible into an existing CI/CD stack, not just write hello-world playbooks.
You want to move from sysadmin to DevOps engineer at your current company. The badge gives you a concrete, data-backed argument in your annual review: a precise score and a detailed report your manager can actually read.
You are preparing for the Red Hat Certified Engineer exam (EX294) and want to know your real starting point before investing in training. The Plume oral gives you an honest skills snapshot in 15 minutes.
You lead a six-person SRE team and want to standardize Ansible practices. Everyone takes the badge: the detailed reports reveal who is solid on roles and collections and who needs coaching on idempotence and testing workflows.
You add your Ansible badge URL to your LinkedIn profile and GitHub README. Recruiters searching for 'Ansible expert' see a verifiable, timestamped signal rather than a self-declared keyword buried in a skills list.
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.
Get a precise score and an official Ansible level (Novice, Proficient, Advanced or Expert) calculated by Claude Opus from your full exam transcript.
A written report highlights your strengths (e.g. solid roles and collections design) and areas to improve (e.g. AWX workflow depth, Ansible at-scale limits) with concrete next steps.
Your exam audio is securely stored and remains private by default. Only you have access to it unless you explicitly choose to share it.
Get a public URL for your Ansible badge to paste on LinkedIn, your CV, your portfolio or a job application. The link displays your score and level in real time.
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
