Images, multi-stage, Compose, volumes, networks, security, registries, size optimization.
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 in 15 minutes that you actually know Docker end to end: Dockerfile craft, multi-stage builds, Compose, security, and registries -- not just copy-pasted docker run commands.
The Plume Docker badge puts you through a 15-minute oral exam with an AI examiner that digs into your real containerization skills. The conversation covers Dockerfile writing and optimization (multi-stage builds, COPY --link, .dockerignore), volume and network management, local orchestration with Docker Compose, image security (non-root user, vulnerability scanning with Trivy or Snyk, secrets via BuildKit), and CI/CD integration with layer caching strategies and semantic tagging.
Unlike a self-declared 'Docker' line on a LinkedIn profile, this badge is backed by a recorded technical conversation. The AI evaluates your ability to explain architecture decisions, debug real incidents (crash-looping containers, bridge vs host networking, volume permission issues), and reason through tradeoffs between image size and maintainability. A second AI model reads the full transcript and produces a score from 0 to 100 plus a proficiency level: Novice, Proficient, Advanced, or Expert.
This badge is the right fit if you're a backend or fullstack developer containerizing your services, a DevOps or Platform Engineer maintaining image build pipelines, or an SRE debugging production incidents. It's also a sharp differentiator for freelancers and consultants who want credible Docker proof points without sitting through a lengthy certification program.
Here are the concrete dimensions the AI examines during the 15-minute oral.
Writing idiomatic Dockerfiles: layer ordering, COPY vs ADD, ARG vs ENV, multi-stage builds to separate build-time and runtime dependencies, and achieving measurable image size reductions.
Exploiting layer cache to speed up CI builds, enabling BuildKit, using cache mounts (--mount=type=cache), and building multi-platform images with Buildx for amd64 and arm64 targets.
Running containers as non-root, choosing minimal base images (distroless, Alpine, UBI), scanning for CVEs, and managing build-time secrets without leaking them into image layers.
Knowing when to use bind mounts, named volumes, or tmpfs; handling permission issues; backing up and restoring volumes; and understanding the difference between dev-local and production persistence patterns.
Bridge, host, and overlay network modes; internal DNS resolution between containers; port exposure; network isolation in Compose stacks; and troubleshooting connectivity failures.
Defining multi-container services, managing startup order with depends_on and healthchecks, layering configs with multiple Compose files, and knowing where Compose stops and Kubernetes begins.
Pushing and pulling from Docker Hub, GHCR, or ECR; tagging strategies (semver, commit SHA, latest); cache-from and cache-to in pipelines; and image signing with Cosign.
Reading logs with docker logs and docker events, inspecting containers with docker inspect and docker exec, diagnosing OOM kills and crash loops, and navigating the shift from Docker shim to containerd.
Final scoring is performed by Claude (Anthropic), which reads back the full transcript and applies this weighted criteria grid.
Precise knowledge of Docker commands, options, and behaviors: Dockerfile syntax, BuildKit features, volume and network internals, Compose configuration. The candidate shows they understand what happens under the hood, not just the happy path.
Ability to describe and analyze concrete incidents: a container that won't start, a leaked secret in an image layer, a networking failure in a Compose stack. Examples must be specific and traceable to real experience.
Systematic application of Docker security fundamentals: non-root execution, .dockerignore, vulnerability scanning, secret management with BuildKit, and selecting the right minimal base image for the workload.
Ability to fit Docker into a realistic CI/CD pipeline: tagging strategy, layer cache in automated builds, private registries, and image promotion across environments (dev, staging, prod).
Familiarity with recent developments (BuildKit, Buildx, containerd, Podman) and the ability to argue when Docker is not the right tool compared to native binaries, lightweight VMs, or serverless runtimes.
A Plume session takes about 20 minutes, from tech check to badge delivery.
Your mic and connection are tested automatically before the session starts. The system confirms audio quality is good -- no special hardware needed, just a working microphone and a quiet room for 15 minutes.
The AI examiner asks you to introduce yourself briefly and walk through your most recent or most complex Docker use case. This sets the stage -- your industry, your stack, your container volumes, and whether the work was professional or personal.
The core of the exam: the AI probes 3 to 5 themes chosen from Dockerfile and multi-stage builds, image security, volumes and networking, CI/CD integration, production incidents, and ecosystem evolution. Questions adapt to your answers -- if you mention BuildKit, expect a follow-up on --mount=type=cache or COPY --link.
The AI asks when you would advise against Docker, or which alternative you would have picked in a recent project. This part measures your ability to think critically about the tool, not just use it.
As soon as the session ends, Claude Opus analyzes the transcript and produces a score from 0 to 100, a proficiency level, and a detailed report. Your Docker badge is ready to share within minutes.
Your score out of 100 translates into a level a recruiter can grasp at a glance.
You can run a container with docker run and write a basic Dockerfile from a tutorial, but struggle to explain how layers work, the difference between CMD and ENTRYPOINT, or why instruction order in a Dockerfile affects cache invalidation.
You containerize real applications, orchestrate multi-service stacks with Docker Compose, and handle named volumes and bridge networks. You know the basic security hygiene (non-root user, .dockerignore) but haven't gone deep on build optimization or vulnerability scanning.
You use multi-stage builds to produce lean images, integrate Docker into CI/CD pipelines with fine-grained layer caching, scan images with Trivy or Snyk, and have debugged production incidents. You're comfortable with BuildKit, tagging strategies, and private registries.
You design complex build workflows (Buildx multi-arch, distributed cache), apply end-to-end supply chain security (distroless base images, Cosign image signing, SLSA provenance), and have a well-reasoned opinion on containerd vs Docker Engine, rootless Podman, and when to skip containers entirely.
No degree or years of experience required to take the badge. Here are the profiles it makes the most sense for.
You containerize your Node.js, Python, Go, or Java services and want to prove you can write a clean, optimized Dockerfile -- not just copy the one from the official README.
You maintain image build pipelines in CI/CD and want fast, credible proof of your BuildKit, registry, and tagging expertise without spending a week in a certification bootcamp.
Clients see 'Docker' on your profile but want concrete evidence. The Plume badge gives you an objective, verifiable validation you can share in under 20 minutes.
You've learned Docker hands-on and want recognition of your real skill level to land a first role or internship without years of professional experience on your resume.
You handle Docker incidents in production and want to document your ability to debug crash loops, networking failures, and memory leaks in containerized environments.
Where and how your Docker badge will help you day to day.
You're interviewing for a Docker-heavy position. You attach your Plume badge link to your application: the hiring manager sees a score of 78/100 at Advanced level and a report highlighting your CI/CD and security strengths, which gets you past the resume screen.
You add your Docker badge URL to your freelance profile. A client choosing between two similar candidates sees that your skill level is independently verified -- and picks you because the score is traceable and auditable.
You just finished a Docker course and want to know where you actually stand. The 15-minute oral reveals your blind spots -- for example, that you're solid on Compose but weak on BuildKit secret management.
During a rate negotiation, you share your Expert Docker badge to justify a higher day rate. The detailed report gives concrete talking points beyond a single number.
You're a developer moving into DevOps and need to show containerization skills before you have a DevOps job title on your resume. The Docker badge gives you a validated, shareable proof point right now.
A tech lead has the whole team take the Docker badge to map real skill levels and plan targeted training. Comparing reports shows who owns security hardening and who has gaps on BuildKit.
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 from 0 to 100 and a Docker proficiency level (Novice, Proficient, Advanced, or Expert) produced by Claude Opus from your transcript -- not a self-reported claim.
A structured report pinpoints your strengths (e.g., multi-stage optimization, security hygiene) and areas to improve (e.g., BuildKit cache mounts, registry management), with direct quotes from your answers.
Your 15-minute session is securely stored and stays private. You decide whether to share it -- it's never made public without your explicit consent.
A unique public URL lets you share your Docker badge on LinkedIn, your resume, or in a job application email. Recruiters can verify the score's authenticity in one click.
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
