MySQL
InnoDB, indexes, transactions, replication, partitioning, performance, security.
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.
InnoDB, indexes, transactions, replication, partitioning, performance, security.
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 MySQL skills in 15 minutes — InnoDB internals, indexes, transactions, and production performance, all on the record.
The Plume MySQL badge puts you through a 15-minute AI-driven oral exam that digs into your real command of the world's most widely deployed relational database. The examiner covers InnoDB internals (buffer pool, MVCC, redo and undo logs), index design (composite, covering, expression indexes, column ordering), transactions and isolation levels (gap locks, next-key locks, deadlocks diagnosed via SHOW ENGINE INNODB STATUS), GTID-based and semi-synchronous replication, schema migrations at scale, and the MySQL 8.0 feature set — CTEs, window functions, native JSON, instant DDL. This is not a multiple-choice quiz: the AI pivots based on your answers and pushes harder wherever you're less precise.
A bare "MySQL" line on your LinkedIn profile tells a hiring manager exactly nothing. The Plume badge produces a 0-100 score, a certified level (Novice / Proficient / Advanced / Expert), and a written report from Claude Opus that quotes your actual answers. A recruiter or CTO can read in five minutes what you really know about the things that matter in production: reading an EXPLAIN ANALYZE output, choosing between a composite and a covering index, avoiding table-locking schema changes on a 500-million-row table, or explaining why you'd pick PostgreSQL over MySQL for a given workload.
This badge is built for backend developers, DBAs, data engineers, and tech leads who use MySQL daily and want their expertise to be visible and verifiable. Whether you're actively job hunting, freelancing and need to reassure a new client, or just curious where you stand against the market — the Plume oral gives you an honest answer based on criteria that actually matter in professional environments.
Here are the concrete dimensions the AI examines during the 15-minute oral.
Buffer pool, tablespaces, MVCC, redo log, undo log — the AI checks that you understand what happens under the hood when a query hits your storage engine, not just that you know the acronyms.
Composite indexes, covering indexes, column ordering, expression indexes (MySQL 8.0+), and reading EXPLAIN / EXPLAIN ANALYZE to validate or invalidate your choices under real workload conditions.
Isolation levels, gap locking, next-key locks, deadlock prevention and diagnosis via SHOW ENGINE INNODB STATUS — everything you need to avoid silent data bugs and blocking issues in production.
GTID replication, semi-synchronous replication, Group Replication, ProxySQL, InnoDB Cluster — the AI explores your ability to design fault-tolerant architectures and explain their trade-offs.
Slow query log, Performance Schema, PMM, Datadog, pt-query-digest — how you identify bottlenecks before they become production incidents, and how you measure the impact of your fixes.
Instant DDL (MySQL 8.0), gh-ost, pt-online-schema-change, Flyway, Liquibase — how you evolve a schema on a table with hundreds of millions of rows without downtime or data loss.
Recursive CTEs, window functions, native JSON (JSON_TABLE, JSON_ARRAYAGG), roles and password policies — the features that separate a 5.7-era user from someone genuinely up to speed.
When would you pick PostgreSQL, Vitess, TiDB, or an analytical warehouse over MySQL? The AI asks you to defend your architecture choices against real volume and load constraints.
Final scoring is performed by Claude (Anthropic), which reads back the full transcript and applies this weighted criteria grid.
Depth and accuracy of your explanations about the InnoDB storage engine, index design, and EXPLAIN output interpretation. This is the core of the exam — we expect mechanical understanding, not Wikipedia-level definitions.
Your ability to narrate and analyze real incidents — slow queries, deadlocks, sudden load spikes — with a structured approach: diagnosis, hypotheses, fix, verification. Made-up anecdotes are easy to spot.
Relevance of your architecture choices: replication strategy, partitioning, choosing between MySQL and its alternatives. We assess whether you can argue a technical trade-off against a real business or operational constraint.
Familiarity with the tools around MySQL: migration tools (Flyway, gh-ost), monitoring (PMM, Performance Schema), ORM integration, and CI/CD best practices for schema changes.
Your ability to explain complex concepts (MVCC, isolation levels, GTID) in plain language without hiding behind jargon. An expert who can't explain things clearly can't move a team forward.
A Plume session takes about 20 minutes, from tech check to badge delivery.
Microphone, browser, and connection are all tested before the session starts. If something isn't right, you can reload without burning your attempt. The AI waits for you to confirm you're ready.
The AI examiner asks you to briefly introduce yourself and describe the most significant MySQL project you've worked on — the data volume, the architecture, and your specific role. This sets the stage for the rest of the exam.
The AI works through the calibrated themes: index design and EXPLAIN, transactions and deadlocks, zero-downtime migrations, GTID replication, MySQL 8.0 vs 5.7, and technology trade-offs. It adapts to your answers and probes deeper wherever you're less precise.
The examiner closes with an open-ended positioning question — for example, in what scenario would you advise against MySQL? — to assess your overall vision and your ability to defend a technical call under constraint.
Claude Opus reads the full transcript, produces a 0-100 score, a certified level, and a detailed report. Your shareable MySQL badge is available in your Plume dashboard as soon as the analysis is complete.
Your score out of 100 translates into a level a recruiter can grasp at a glance.
You can write SELECT, INSERT, UPDATE statements and create tables. You know indexes and joins exist, but you can't read an execution plan or diagnose a performance issue. InnoDB, MVCC, and isolation levels are still fuzzy concepts.
You design sound relational schemas, use EXPLAIN to read a basic execution plan, and create meaningful indexes for common queries. You understand transactions and isolation levels without necessarily mastering edge cases like gap locking or complex deadlocks.
You diagnose production performance issues (slow query log, Performance Schema, EXPLAIN ANALYZE), design composite and covering indexes, handle schema migrations on large tables (gh-ost, pt-osc), and work with MySQL replication. You're comfortable with MySQL 8.0's key features.
You design high-availability MySQL architectures (InnoDB Cluster, Group Replication, Vitess), tune the engine at the configuration level (innodb_buffer_pool_size, innodb_io_capacity, binlog_format), make principled calls between MySQL and its alternatives, and can mentor a team on production best practices.
No degree or years of experience required to take the badge. Here are the profiles it makes the most sense for.
You work with MySQL every day through an ORM or raw SQL, and you want to prove you go beyond basic SELECT statements — especially on index design, transaction management, and schema migrations.
You manage replication, monitoring, backups, and performance for MySQL clusters in production. The badge formalizes expertise that's impossible for recruiters to assess from a resume alone.
MySQL sits at the center of your data pipeline and you need to justify your architecture choices — partitioning, JSON column indexing, CDC with Debezium — to product teams and hiring managers.
You make decisions about database engine selection, replication strategy, and migration planning. The badge validates that your calls are grounded in a deep understanding of InnoDB and the MySQL ecosystem.
Your clients can't verify your DBA chops on their own. A Plume badge with a score and a detailed report replaces ten references — it speaks directly to the CTO or engineering manager signing the contract.
Where and how your MySQL badge will help you day to day.
You're applying for a senior developer role where MySQL is central to the stack. Your Plume badge at Advanced or Expert level gives a technical recruiter a concrete signal when choosing between three candidates with similar resumes.
A client asks you to audit and optimize a MySQL database with 200 million rows. You share your badge link before the first call — the detailed report shows you know how to read EXPLAIN ANALYZE, handle zero-downtime migrations, and configure replication.
You're going for a tech lead role at your company. The badge gives you an objective argument in your promotion review: you don't just use MySQL, you can explain gap locking, recursive CTEs, and the difference between GTID and binlog-position-based replication.
You're a full-stack developer moving into database administration. Taking the badge before applying shows that your career pivot is serious and that you already have a solid grasp of InnoDB internals, Performance Schema, and replication.
You publish open-source projects or technical articles about MySQL. Adding your Plume badge to your README or GitHub profile provides verifiable proof that your expertise is real and independently assessed.
You hold an Oracle MySQL certification but it's several years old and doesn't cover MySQL 8.0. The Plume oral lets you demonstrate that your skills are current — window functions, instant DDL, native JSON — without sitting through a multi-hour proctored exam.
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.
A 0-100 score and an official MySQL level (Novice, Proficient, Advanced, or Expert) produced by Claude Opus from the transcript of your oral — not a self-assessment.
A written report that quotes your actual answers, highlights your strengths on InnoDB, indexes, and transactions, and pinpoints specific gaps — a concrete tool for improvement or interview prep.
Your session audio is stored securely and accessible only to you. Use it to review your answers, identify areas to work on, and sharpen your delivery before your next attempt or technical interview.
A public URL you can drop into your resume, LinkedIn profile, portfolio, or a client proposal. Any recruiter or client can verify your MySQL level in seconds.
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