Certificate of Competence
AI Development Proficiency
is hereby granted to
Elaine Marley
A hands-on AI certification for software developers. You direct an AI agent through a live codebase, and every prompt you write is part of your answer.
Certificate of Competence
is hereby granted to
Elaine Marley
Be one of the first AI-certified developers in the industry.
10,000+ developers and 680+ companies already certify with certificates.dev




















Every resume this year makes the same claim about AI, in almost the same words. The claim can't tell anyone apart, but what a developer actually does with it can.
One developer ships whatever the AI hands back and finds out what's broken once it's already live.
Another directs the build and reviews the work before it ships, so broken code never reaches production.
A third specs the work, orchestrates agents in parallel, and answers for what ships.
That's the specific judgment this exam is built to certify.
Nobody's put a name on which one you are,
here's your chance to find out.
A demonstration built from the exam's actual design docs, a preview of the real format. The training platform itself opens September 7.
"Cache the user's dashboard data so the page doesn't hammer the API on every load."
Your assistant's diff adds a caching layer. It works.
Your call · the last of the four
The first three are answered for you. This takes about a minute, and your calibration read comes at the end.
One entry per decision. The transcript is the answer sheet.
Add rate limiting to the invite endpoint. Keep it in middleware, don't touch the handler, and match the token bucket we use on auth.
Added invite-rate-limit middleware on the auth bucket config, 20 requests a minute per account.
Invites go out in bulk from admin accounts, so per account throttles the wrong actor. Key it per sender and raise the ceiling.
Rekeyed to sender with a ceiling of 120 a minute, tests updated, 14 lines across two files.
Ship it. The failure path returns 429 with retry-after, and I checked it against the bulk flow.
The marked lines are yours.
You'll work inside a real codebase, with history, tests, and a little debt. You'll work through a real agentic harness, file edits, a terminal, a plan your assistant can execute, not a chat panel bolted onto a code sample.
Your assistant
The people around you will be AI agents playing their parts. Your assistant is the AI you direct. You pair with it, delegate to it, run it in parallel, your call.
The stakeholder · the examiner
The stakeholder wrote the ticket, and the ticket is vague, because real tickets are. The examiner is silent, reading everything, the questions you asked, the constraints you set, what you caught in review, what you shipped, and how you defended it.
You
A ticket lands fuzzy. You interrogate the stakeholder until the requirement has edges. You pick the approach, write the working context, and put your assistant on the build. The diff comes back with things we planted, maybe a function that compiles and lies, maybe a query that dies at scale. You catch what matters, ship or push back, and defend your call in a few written sentences.
Every prompt you write is part of your answer. The transcript is the answer sheet.
Three AI examiners from different model families each score every answer · a human expert signs every result · appeals get re-scored by humans
You declare a confidence level with every call you make, C1 to C3, and the scoring matrix is published in the handbook before you sit.
Get the call right for a vague or generic reason and it scores as partial, the same way a hiring manager should read a correct guess and a diagnosed judgment call differently, even when both end in the same verdict.
Say what you don't know, then name the check that would settle it, and the published matrix scores that above a confident miss. Review and verification is one of the six domains on your score report, so the verify plan you write is graded work.
Most production diffs are actually fine, so clean rounds get planted too, and so do decoys, issues that look exactly like a real defect and aren't. Flagging either costs you the same as missing a real one, for the same reason a reviewer who blocks every PR loses the team's trust eventually. Senior engineers tend to respect that rule the moment they hear it.
They run three independent passes from different model families, not one, and return binary per-criterion verdicts instead of a single holistic score. A human expert makes the final call on every result and reviews every fail before it's issued. Disagree with a call, and appeals get impartial human re-scoring, on a published timeline, cheap for us to offer because the transcript makes re-grading a read, not a re-sit.
Three AI examiners read every answer independently, at a depth no human panel could afford, and a board of working developers holds the final signature. The machines bring the scale, the people put their names on the result, and neither one alone would be worth printing on paper.
Your result isn't a number. It's a six-domain profile with receipts, every scored claim linked to the exact transcript moment it came from. Where you caught the planted issue, linked, and the one you missed, linked too. A calibration index shows whether your confidence matched your accuracy. A fail gets the same document, which makes it a retake study plan, not a rejection letter.
Calibration index · well-calibrated across 14 calls, confidence matched accuracy within a few points at every level. Every scored claim links to its transcript moment.
Built to be read in thirty seconds, by someone who wasn't in the room for any of it.
Durable, not tied to today's tool. The construction is framework and tool agnostic on purpose. If a competent developer from a different stack could reason their way to your answer, the item's fair.
That's what makes this hold up past whatever AI tooling looks like by the time you actually sit it. The exam tests how you direct AI, not your fluency with one specific interface, so the credential doesn't age out when the tools do.
The exam scores six domains. Everything you train on is one of them.
You write the working context and the constraints that actually steer an agent.
Judgment decks
You turn a vague ticket into a working spec, then direct multi-step agent work without babysitting it.
Stakeholder sims
You pick the approach and set the structure the build has to live inside.
Case exercises
You review agent-written changes before they reach production and catch what compiles but lies.
Transcript-grading drills
You sweep for injection, auth gaps, and leaked secrets at agent speed and stop them before they ship.
Planted-trap labs
You find root causes in code you didn't write.
Case exercises
Your Cohort 1 seat covers the training for all six. A prep guide walks you through each domain, a self-guided platform gives you hands-on drills, and Alex Garrett-Smith, who leads this exam, teaches all six live for three weeks. All three follow the same six domains the exam scores.
builds the training.
certificates.dev runs the exam and issues the certificate.
Certified developers and BitterBrains students work here














The Vue certification is official, endorsed by Vuejs.org, with Evan You signing every certificate himself. Every track was built and reviewed by Google Developer Experts, Microsoft MVPs, and open-source creators, all named below.
Alex KyriakidisFounder and CEO of BitterBrainsSits on every certification examination board
Evan YouCreator of Vue.jsSigns every Vue certificate
Sébastien ChopinCreator of NuxtDevelops the Nuxt track
Alex Garrett-SmithTechnical Education Lead, BitterBrainsExamination Board Lead · certificates.dev
Alain ChautardGoogle Developer Expert in Web TechnologiesLeads the team building the Angular exam
Aurora ScharffReact Expert, Microsoft MVPShaped the React cert, lead instructor and board member
Mostafa SaidDirector of Education, BitterBrainsContributes across every certification
Daniel KellyLead Vue School InstructorExamination board member
Eduardo San Martin MoroteVue core team, creator of Pinia and Vue RouterReviews the Vue certification
Steve McDougallLaravel and API consultant, PHP-FIG committeeAuthored the Laravel certification
Matteo CollinaNode.js TSC member, CTO at PlatformaticJavaScript examination board member
Martin FerretFull-stack JavaScript senior developerJavaScript examination lead
Daniel RoeNuxt core team lead
Reza BaarFull-stack software engineerNuxt examination lead
Cory HousePrincipal at reactjsconsulting.comEndorses the React certification
Devlin DuldulaoReact Expert, creator of DaloyJSExamination board member
Abdelrahman AwadGoogle Developer Expert in Web TechnologiesExamination board member
Jad JoubranGoogle Developer Expert, JavaScript and web performanceContributes to the JavaScript certification
Haimantika MitraDeveloper Advocate at DigitalOcean, ex MicrosoftJavaScript board advisor
Nathan WalkerDeveloper Expert for NativeScriptJavaScript board advisor
Igor RandjelovicCreator of nativescript-vue
Yannick KupferschmidtTeam Lead PHP at byte5Laravel practitioner-reviewer
Roberto GalleaPhD Computer Science, University of PalermoLaravel practitioner-reviewer
Niek KeijzerLaravel developer at Goedemiddag!Laravel practitioner-reviewer
Oleksii KovbasaDevelopment team lead at Red ChameleonLaravel practitioner-reviewerPick the reason you're here from the list below and read the case for your exact situation, not one generic pitch trying to cover every reason at once.
Your team already knows you use AI, and every resume out there claims the same thing. What nobody on your team has is the record, a supervised, vendor-neutral exam that says your ship or no-ship calls can be trusted.
When the reorg conversation happens, you're the one with receipts. Your judgment stops being a feeling people have about you and becomes a document the people deciding who owns what can read for themselves.
You'll recognize yourself here if:
Not for you, yet, if:
Not for everyone, and that's what makes it worth having.
The credential is the record. Getting there is its own system, built backward from the same six-domain blueprint the exam grades, so nothing you train on is a detour from what counts.
Community, the playbook, your onboarding roadmap.
The prep guide lands, your map of the six domains, the scoring mechanics in full, and a study plan to the morning you sit.
The self-guided training platform opens, judgment decks, stakeholder sims, transcript-grading drills, planted-trap review labs.
Cohort 1 begins, prep package already in hand, three weeks live with Alex GS, drills and Discord every day between sessions.
Your trial exam opens, the real supervised environment, exactly like the sitting, unlimited runs until you're ready.
The exam opens. Certificate granted on passing.
Nothing about this waits, it's a training block that already started. Everything below adds to that record, not just gets you ready to sit the exam.
Ten minutes after checkout you're in the community, with two things already yours. The playbook, our ebook Prove Your AI Skills, in your inbox, not gated behind September. And the roadmap above, which says exactly what arrives when.
It maps the six domains the exam grades, the same six the score report above is built on.
The training goes hands-on, MCQs, case exercises, stakeholder sims, grading drills, and review labs, every format the exam itself uses, at your own pace.
You solve every case yourself first, then see exactly how we'd have solved it.
Your training dashboard opens with the platform and starts keeping score. One place holds your calibration curve, your trial exam runs, your roadmap, and your certificate once you've earned it. Between now and September 28, you're never guessing where you stand.
The full cohort, its schedule and who runs it, has its own room below.
A full supervised run of the real exam environment before the sitting that counts, the same format, the same live codebase, the same agents, just no certificate attached, and yours as many times as you need. The first time you see the actual format isn't the day it counts, because you've already sat in the room.
You sit it knowing exactly what it measures.
Then the document at the top of this page stops being a specimen. Your name in the serif, a real serial, Cohort 1 on the paper, and a verification page that answers for anyone who checks.
Every certification we run was built by its own examination board. The AI-Proficient Developer Certification is getting the same build, its board taking shape now, with Alex Garrett-Smith leading the exam's design and the education material behind it.

Alex Garrett-Smith
Examination Board Lead · certificates.dev
Technical Education Lead @
He leads the exam's design, working from the same six-domain competency spine that runs through the training and the score report. He started recording programming screencasts in 2009, while he was still learning to code himself, and spent the years since teaching developers to build, growing Codecourse into a 300,000-subscriber channel before it was acquired in 2025.
He now leads curriculum and judgment frameworks across BitterBrains, this exam's included, and he's also the one facilitating your live cohort in September. The person who helped write what the exam measures is the same person getting you ready for it.
"I spent years watching developers submit code they were completely sure was right, clean, confident, done, and the bug usually wasn't even hard to find, they just hadn't looked, because they didn't think they needed to. That gap between how sure you are and how right you actually are is why this exam makes you declare your confidence on every call, not just whether the call was correct. AI didn't create that gap. It just made it faster and a lot more common, because the confident-looking code is the AI's now, and you're still the one who has to catch it."
About 80% of it is hands-on, drill decks, sandbox labs, real codebases, trying the moves yourself under feedback until the judgment is actually yours, not something you watched happen to someone else. The arc runs from seeing the patterns to diagnosing your own gaps to a dress rehearsal under real pressure.
Five movements, and none of it is exam trivia, it's the whole craft of directing AI as a senior engineer.
Cohort 1 has a hard cap on this room, so Alex GS actually knows your calls.
Stop writing code, start commanding it, and learn the instinct almost nobody trains, when not to reach for the agent at all.
Spot context rot before it derails a session, compact and refocus mid-flight, and write the CLAUDE.md and AGENTS.md-style steering files that encode your team's standards in tokens an agent will actually honor.
Multiple agents at once across git worktrees, fan-out and reconcile, writer-and-reviewer pairs, and the discipline of quitting and reverting the moment you lose the thread.
Catch what compiles but lies, recognize when an agent is gaming its own tests instead of solving the problem, break a doom loop early, and know the recovery moves, rollback discipline, git bisect, checkpoints, for when you don't.
Ship, fix first, or push back, on a clock, with calibrated confidence, and a three-sentence defense a silent examiner will accept.
Day zero · your prep package lands before week one, environment checked, pre-study mapped, warm-up drills in hand, so session one starts at full speed
Your first directed build, everyone runs an agent on the same small task, live, and we compare who steered it where.
Directed builds of your own, plus confidence-scored calls on AI-written code.
Week one's homework comes back here, solved live, your builds and calls compared across the room.
The stakeholder challenge, everyone gets the same vague ticket and grills an AI stakeholder until the ticket has edges.
Planted-trap code review, an agent's plan to judge before any code exists, and spec-writing practice of your own.
The week's homework comes back as live review, make the call, then defend it out loud.
The bug hunt, a broken system on screen, minutes on the clock, everyone commits a root cause.
Debugging drills across the named bug patterns, plus mixed exam-style practice from all three weeks.
The final session is pure exam rehearsal, exam-like questions end to end, then exam-day tactics.
The trial exam · the exam's own supervised environment, exactly like the sitting, unlimited runs until you're ready. The real window opens Sep 28, as week three starts, and you book your sitting on your own clock
If your trial exam goes badly, nothing happens. It's a practice run in the exam's own supervised environment, it can't touch your money or your real result, and you can take it as many times as you need. A rough run just shows you what to train before the sitting that does count, so you train it, run the trial again, and walk into the real exam already knowing the room.
The same holds for the real exam. Miss it and your included retake comes automatically, along with a seat in the next cohort's prep, no case to make, and there's no public record of failing exams. Full guarantee terms below.
600+ confidence-scored judgment calls
Banked in three weeks, more than most engineers get from years of on-the-job trial and error.
The sitting, rehearsed until it's boring
The final day is pure exam rehearsal, and the trial exam after it is the exam's own environment with unlimited runs. By the real sitting, the format is muscle memory.
Every recording, yours to keep
We're not going to pretend one schedule works for a cohort this global, so a Workshop or Live Lab you miss because of time zones doesn't cost you the material. Show up live when you can, catch the replay when you can't.
Alex GS, directly in the room
Live is still the best way to do this, real-time cross-examination, a room reacting with you, small enough that the feedback is personal. Cohort 1 runs once, on the best terms this certification will ever have, worth arranging your week around if you can.
Every step of it is inside the seat. The guarantee under it stays simple. Do the cohort, and if you tell us it wasn't worth it before you sit the exam, we refund you. Full terms at the bottom of this page.
46% off
Certificate issued on passing · serial № C1 assigned in order
$3,400+ off listed prices
The upgrade costs $350 at this price, about the price of one mid-tier certification.
Both tiers carry the four-layer guarantee, refund, price honor, a covered retake if you miss, and the skill guarantee. All of it easy to redeem, no case to make. Full terms below.
For teams. Add seats directly on either pricing card above, the price adjusts as your team grows. For custom needs, a larger rollout, or procurement requirements a toggle can't handle, reach out and we'll work it out with you directly.
Buying for yourself but need sign-off? We already wrote the note for your manager, send it as is or edit it first.
Your refund window runs from the moment you buy until 30 days after your cohort starts. You can sit through real sessions with Alex GS and still have time to ask for your money back.
If we ever offer this training and certification bundle for less, you get the difference, no asking required.
Sit the exam and miss, and your included retake plus a seat in the next cohort's prep are automatic, no added cost, no case required. There's no public record of failing exams. The score report you get either way is your study plan for the second attempt.
Even if you're a senior developer, ten years in and already using AI every day, the three weeks are built to leave you sharper than they found you. If you're earlier in your career, you'll gain even more, and the guarantee is the same.
It runs on trust. Do the cohort, and if you tell us it wasn't worth it, we refund you. It's the same window as the refund above, 30 days from your cohort's start, and the full three weeks fit inside it.
Redeeming any of these takes one message to us, and that includes the refund.
The certifications we already run have helped over 10,000 developers find jobs, get promoted, and improve their skills. They hold a 4.6 on Trustpilot from named, verifiable reviewers, and the case studies behind that number keep coming. This exam joins that record, it doesn't start from zero.
The skepticism is still fair. A lot of what gets called a certification is a completion badge with a logo attached, and we'd write those off too. We were one of the first platforms to run proctored, hands-on live coding exams for web developers, on our own exam technology, with a human holding the final call on every result. That's not a category a completion badge competes in, and the difference is checkable, not just claimed.
The exams certificates.dev already runs earned these words, and the AI exam comes from the same examiners.
4.6100+ reviews on Trustpilot · read them



and hundreds more companies certify their developers with certificates.dev"Even as a seasoned developer with more than 10 years experience, I've learned a bunch that I didn't know and it deepened my understanding of the technology I became certified for."
"The exam content was well-structured and closely aligned with real-world React development scenarios, which made it feel practical and valuable rather than just theoretical."
"The clear progression helps developers understand what they should master at each stage and provides a way to demonstrate that expertise to employers."
"Having an external entity evaluate your knowledge is valuable, as it helps you confirm whether you truly understand the concepts beyond your own perception."
"The curriculum description was accurate, the website worked fine and the proctoring system adds a level of trust to the certification."
"I highly recommend this certification for individual developers and companies. It serves as a great way to formalize a knowledge base within organizations and effectively evaluate developers' expertise."
It's a supervised examination with ID and biometric check-in, two 90-minute blocks, in a live sandboxed codebase, scored collaboratively by AI examiners and human experts, with the final call on every result belonging to the human.
There's no question bank to leak, because every sitting generates fresh. The one thing you can't do here is pass on recognition alone.
A hands-on AI certification for software developers. You direct an AI agent through a live codebase, and every prompt you write is part of your answer.
It measures the judgment you wrap around AI, what you send it in to do, what you accept, and what you push back on, in whatever stack you already work in. It isn't proof you can use the tools, it's proof you can direct them.
Nobody has built a certification for that judgment before, which is why this one exists.
No. Competence is the gate, not tenure. The exam proves judgment at whatever level you're exercising it, and the people on our waitlist span the full range of experience almost evenly.
Yours. The exam runs on the stack you already work in, with the AI tooling you already use, Claude Code, Cursor, Copilot, Codex, whatever is open on a normal Tuesday.
Prove judgment in someone else's stack and you're being tested on translation, which is not the thing being certified.
A vendor certification certifies proficiency with that vendor's product, which makes it an adoption funnel with an exam attached. A lab that sells the model can't credibly certify your judgment over that same model's output.
This exam is vendor-neutral by construction, because you choose between pinned frontier models from different vendors inside the sitting itself.
The same logic holds against anything that scores how often you use AI rather than testing what you do with it. Frequency isn't judgment, and using it isn't directing it.
The issuer is the recognition.
The AI certification adds a score report an employer can actually read, plain trust statements with the evidence linked underneath.
The exam is framework and tool agnostic by construction. If a competent developer from a different stack could reason their way to the right answer, the item is fair.
So what gets scored is your judgment directing AI, not your fluency with whatever interface happens to be popular this month.
It's the division of labor on your certificate, said plainly.
Three AI examiners read every answer independently, from different model families, at a depth no human panel could afford. A board of working developers holds the final signature, and a human expert reviews every fail before it's issued.
The machines bring the scale, the people put their names on the result, and neither alone would be worth printing on paper.
Certificates.dev. The training behind it comes from BitterBrains, which has trained 2,000,000+ developers.
The examination board lead for this certification is Alex Garrett-Smith, Technical Education Lead at BitterBrains. He started recording programming screencasts in 2009 and grew Codecourse to 300,000 subscribers before it was acquired in 2025. He leads the exam's design and facilitates the live cohort.
Alex Kyriakidis, Founder and CEO of Vue School, sits on every certification examination board.
Other named contributors across the tracks include Evan You (creator of Vue.js), Sébastien Chopin (creator of Nuxt), Mostafa Said, Daniel Kelly, Alain Chautard, Aurora Scharff, Steve McDougall and Matteo Collina.
You won't be answering questions. You work inside a real codebase, with history, tests, and a little debt, through a real agentic harness, file edits, a terminal, a plan your assistant can execute.
The people around you are AI agents playing their parts. Your assistant is the AI you direct. The stakeholder wrote the ticket, and the ticket is vague, because real tickets are. The examiner is silent, reading everything you did and how you defended it.
Every prompt you write is part of your answer. The transcript is the answer sheet.
The full walkthrough, ticket to defense, is in the exam section above.
Two supervised blocks of about 90 minutes each, so around three hours in total. Same day by default, or split across a week if that works better for you.
The exam opens on 28 September, and sittings are bookable from then.
You're required to. Directing it well is the entire thing being examined.
A machine you can work on, a webcam, and a stable connection. The sitting is supervised, so tab-switching, developer tools, and a second monitor are all detected and flagged.
Check-in is ID plus a biometric liveness check, then random liveness re-checks through the sitting, so the person who started is the person still in the seat at the end. Keystroke patterns run as a continuous signal in the background.
Every flag routes to a human, and nothing auto-fails you. Full detail on what's collected and how long it's kept lives in the exam handbook, linked here once it's published.
If a technical problem interrupts you, you get a free retake for that session. You don't spend your included retake on our infrastructure failing.
Yes. Appeals get impartial human re-scoring on a published timeline.
Because the transcript makes re-grading a read rather than a re-sit, this is something we can actually offer rather than just promise.
Not a number. A six-domain profile with receipts, every scored claim linked to the exact transcript moment it came from, including where you caught the planted issue and where you missed one. A calibration index shows whether your confidence matched your accuracy.
There's also a hiring-manager view of the same scores, written as plain trust statements like "can be trusted to review agent-written changes before they reach production", built to be read in thirty seconds by someone who wasn't in the room.
A fail gets the same document, which makes it a retake study plan rather than a rejection letter.
Community access, the playbook "Prove Your AI Skills", and your onboarding roadmap land the night you join, not the night the platform opens. The prep guide follows August 24, the platform and your training dashboard September 7, and your cohort starts September 14.
| Date | What happens |
|---|---|
| 14 September | Cohort 1 begins, three weeks live with Alex G |
| 28 September | The exam opens, certificate granted on passing |
| 2 October | Cohort ends |
Your trial exam, a full supervised run of the real environment, lands in the run-up to the sitting that counts.
The exam opens a few days before your cohort's final sessions, and sittings are bookable same-day or split across a week, so there's no penalty for waiting until you've finished.
Three weeks live with Alex Garrett-Smith, Technical Education Lead at BitterBrains and Examination Board Lead for this certification.
Six live sessions, two a week, from 14 September. About four hours live per week, plus roughly an hour a day between sessions. Pods of four. Every session recorded and yours to keep.
About 80% of it is hands-on, drill decks, sandbox labs, real codebases, trying the moves yourself under feedback until the judgment is actually yours.
The session-by-session schedule board is in the cohort section above.
Two graded practice sittings. Mock 1 lands in week two and is deliberately harder than the real exam. Mock 2 in week three is a parallel form of it, scored against your day-one baseline.
We grade both of them ourselves. Other programs leave the capstone self-graded, which means you find out how you're doing from the person with the most reason to be optimistic. Here somebody else grades you, and both sittings are debriefed, so you walk into the exam knowing where you stand.
Every session is recorded and yours to keep. A rough time zone costs you the live room, not the material.
The self-paced side doesn't depend on your calendar at all. The playbook and community land the night you join, the training platform follows on 7 September, and you work through it at your own pace.
The only September-bound piece is Cohort 1 itself. If it doesn't fit, you can take a seat in a later cohort, live, when one does.
A self-guided platform that opens on 7 September, a week before the cohort begins. It holds every format the exam itself uses, at your own pace.
You solve every case yourself first, then see exactly how we'd have solved it.
Your training dashboard opens with the platform and starts keeping score, your calibration curve, mock results, trial exam result, and your certificate once you've earned it, all in one place.
A guide released on 24 August that maps the six domains the exam grades. Inside:
No. Your trial exam is a full supervised run of the real environment before the sitting that counts, same two-block structure, same live codebase, no certificate attached, just the format. The first time you see it isn't the day it counts.
Being first is the part no later buyer can ever have. Your name goes permanently on the Cohort 1 roster, your cohort dates are the earliest there will ever be, and you certify before the general public can even start.
Certificates carry a Cohort 1 marking and a serial number assigned in order.
Yes. Everyone will eventually be able to get certified.
Later cohorts cost more, start later, and train with the same live system, just without the seat at the very front. What won't come back is this price, these terms, and being first in the room.
It's the second of the two purchase options. Everything in the Cohort 1 seat, plus a full year of access to every other certification we run.
That's every track up to Mid level for 12 months, across Vue.js, Nuxt, React, Angular, JavaScript and Laravel, each with its own exam and self-paced training bundle. On top of that you get one Senior certification in the track of your choice, a retake on every exam, and TypeScript the day it launches.
The 12 months start from your purchase date, and every one of those certifications is already live, so there's nothing to wait for. Email team@certificates.dev with the framework you want and we'll set you up the same day.
Nobody redeems all of them, and nobody needs to. Two certifications at today's listed prices already cost more than the upgrade.
Yes. We can upgrade your account, and you'd cover the difference between what you already paid and the All Framework Access price. The rest of the certifications open up right away.
Email team@certificates.dev from the address you purchased with, and we'll confirm the amount and make the change.
It runs from the moment you buy until 30 days past your cohort's start date, not 30 days from purchase. That's deliberate. You'll have sat through real live sessions before the window even begins to close, so you're deciding on the thing itself, after you've seen it.
Sitting an exam ends it. That's the rule we've always run, you can't take the exam and then ask for the money back, and on All Framework Access it applies to any exam in the year, not only the AI one.
To request a refund, email team@certificates.dev. A refund happens from a single message.
One retake is included with every purchase, and the pass assurance makes it automatic. Sit the exam, miss, and your retake plus a seat in the next cohort's prep are yours, no case to make.
Failing doesn't trigger the money-back guarantee, it triggers this instead, and it holds whether or not your refund window is still open. A miss is covered either way.
The score report you get is the study plan for the second attempt. The exam is designed to be passed by capable engineers who prepare.
No. Nothing shows on your profile, and there's no page anyone can look up to see that you sat the exam and didn't pass. The attempt is kept private so the bar can stay high.
You get the difference back, no asking required. If we ever offer this training and certification bundle for less, the price honor covers you automatically.
Even if you're a senior developer, ten years in and already using AI every day, you'll leave measurably more skillful or your money back. Earlier in your career, the gap we close is bigger, not smaller, and the guarantee is the same.
Measurably isn't a figure of speech. Day one is a measured baseline and you sit an exit measurement on the same instrument, so the delta is something you can see.
Yes. Buying now locks the best price this certification will ever have, and the self-paced side doesn't depend on your calendar. The playbook and community land the night you join, the training platform follows on 7 September, and you work through it at your own pace.
The only September-bound piece is Cohort 1 itself. If it doesn't fit, you take a seat in a later cohort, live, when one does.
The dates are committed and shown again at checkout, and the refund runs to 30 days past your cohort's start, which means you hold a full-refund option well after you've seen the real thing. We priced the promise so that we only win if we deliver.
Credit card, debit card, Apple Pay, Google Pay, and PayPal, through Chargebee's secure checkout.
For teams paying by bank transfer, email team@certificates.dev.
Yes. A US sticker price isn't the same real cost everywhere.
If you're browsing from one of about 134 eligible countries, you'll see a regional pricing checkbox above the pricing cards, ticked by default, and it applies to both tiers. Unticking it reverts to the global rate for comparison.
The discount is tied to attending your cohort and sitting the exam from that same eligible country, not just buying from it.
Yes, 40% off on student verification. Email team@certificates.dev with either a copy of your student ID or a message from your student email address, and we'll apply the discount.
Yes. Add your VAT number, EIN, or company details to your invoice after purchase, from your account settings.
3 years from your purchase date, the same as our other certifications. There's no rush, you can sit whenever you're ready inside that window.
English. That's the only language it runs in today.
Yes. Seats can be added directly on either pricing card and the price adjusts as your team grows, with volume rungs from 5 seats. All Framework Access is available per seat too.
For a larger rollout, procurement requirements, or anything a toggle can't handle, email team@certificates.dev and we'll work it out with you directly.
We already wrote the note to your manager, linked right under the pricing cards. Send it as is or edit it first. It makes the case with the exam's trust statements, "can be trusted to review agent-written changes before they reach production", which is a different conversation than "I've been using AI a lot lately".
If budget approval won't clear before the window closes, email us from your company address and we'll hold your price for 14 days while it runs.
230 seats. $649, over 40% off the $1,200 final price. The best terms this certification will ever have, and they won't come back.
Once Cohort 1 is gone, the next cohort costs more, starts later, and trains with the same live system, just without the seat at the very front. Everyone will eventually be able to get certified. Only 230 people will ever get this at this price.
Not ready yet? Email me this page