Eloquent, migrations, queues, Livewire, Sanctum, tests, Composer, deployment.
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 you actually know Laravel in production — Eloquent optimization, Horizon queues, Sanctum tokens — not just on your resume.
The PHP / Laravel badge from Plume certifies your real-world command of the most widely used PHP framework in the industry. Over a 15-minute voice conversation with an AI examiner (OpenAI Realtime), you're challenged on the topics that separate solid Laravel developers from the crowd: Eloquent N+1 detection and eager loading strategies, risky database migrations in production with rollback planning, async job processing with Redis and Horizon, API authentication trade-offs between Sanctum and Passport, and full-stack orchestration with Livewire, Inertia.js, and CI/CD pipelines. A second AI model (Claude Opus) reads the full transcript and produces a 0-100 score with a certified level: Novice, Proficient, Advanced, or Expert.
What sets this badge apart from a self-declared LinkedIn skill is that the examiner adapts in real time. If you mention Horizon, it probes how you supervise workers and handle failed_jobs. If you bring up Sanctum, it digs into SPA token management and CSRF handling. You can't rehearse a script — you have to reason live about real trade-offs, like when you'd reach for Passport instead of Sanctum, or when you'd skip Eloquent entirely in favor of a raw query builder. The score reflects your technical depth, your architectural judgment, and your hands-on production experience.
This badge is for PHP developers applying for backend or full-stack roles who want objective proof beyond their CV, freelancers who need to build trust with new clients quickly, and engineering leads who want a consistent benchmark before technical interviews. Whether you're job-hunting, pitching a contract, or just curious where you actually stand in the Laravel ecosystem, this badge gives you a timestamped, shareable credential backed by a real AI-driven assessment.
Here are the concrete dimensions the AI examines during the 15-minute oral.
Mastery of Eloquent relationships (hasMany, morphTo, polymorphic), identifying and fixing N+1 issues with eager loading, and handling large datasets efficiently using chunk() and lazy collections.
Writing robust migrations with nullable columns, composite indexes, and foreign key constraints, plus strategies to avoid table locks and safely execute rollbacks on critical production databases.
Configuring queue drivers (Redis, database), structuring jobs and listeners, setting retry policies and exponential backoff, and supervising workers at scale with Laravel Horizon and the failed_jobs table.
Knowing when to use Sanctum (SPA tokens, cookie-based auth, simple API tokens) versus Passport (full OAuth2, third-party clients, authorization codes), and handling token refresh and scope management correctly.
Service providers, repositories, form requests, policies, observers, and the trade-off between facades and dependency injection — explaining each architectural choice with real project constraints in mind.
Wiring Laravel with Livewire (reactive server-side components) or Inertia.js (React/Vue frontend), managing Composer and Vite, and running CI/CD pipelines with Laravel Forge, Envoyer, or Docker.
Writing feature and unit tests, using model factories and database seeders, mocking external services with Laravel's built-in fakes, and testing queue jobs, notifications, and HTTP requests end-to-end.
Comparing Laravel with Symfony or Lumen for specific use cases, knowing when to skip Eloquent for raw SQL, and staying current with new Laravel primitives like Pennant, Folio, Volt, and Reverb.
Final scoring is performed by Claude (Anthropic), which reads back the full transcript and applies this weighted criteria grid.
Accuracy and precision across Eloquent, queues, migrations, Sanctum/Passport, and the broader Laravel ecosystem. This is the core criterion: candidates must demonstrate real knowledge of the framework's internals and patterns, not just surface-level familiarity.
Ability to justify technical decisions — why Sanctum over Passport, why Livewire over Inertia, when to abandon the ORM for raw SQL — with arguments grounded in real project constraints, not personal preference or trend-following.
References to concrete situations: a risky migration handled in prod, a worker supervision issue with Horizon, a real N+1 debug on a high-traffic dataset. Responses that stay abstract without any grounding in lived experience score lower on this dimension.
Ability to explain complex concepts — lazy collections, OAuth2 with Passport, job chaining with Horizon — in a clear, structured way without unnecessary jargon. Strong technical communication is essential for developers working in teams.
Familiarity with recent Laravel additions (Pennant for feature flags, Folio for file-based routing, Volt for single-file Livewire components, Reverb for native WebSockets) and ability to position them relative to community alternatives and competing frameworks.
A Plume session takes about 20 minutes, from tech check to badge delivery.
Before the exam starts, the platform checks your microphone and connection quality. No camera needed — the entire session is voice-only. You can use a headset or your laptop's built-in mic. Once everything is green, you're ready to go.
The AI examiner asks you to introduce yourself and describe your most recent or most complex Laravel project: the stack, your role, the key technical challenges. This answer calibrates the difficulty and focus of the questions that follow.
The core of the exam: 5 to 6 targeted questions on Eloquent, queues, migrations, API authentication, frontend integration (Livewire/Inertia), testing, and deployment. The examiner adapts in real time — mention Horizon and it goes deeper on worker supervision; bring up Sanctum and it explores SPA token flows and CSRF cookies.
The examiner asks an open-ended question about your trade-offs and limits: when would you avoid Laravel? What do you think of Pennant or Reverb? This step reveals your technical maturity beyond factual knowledge of the framework.
As soon as the session ends, Claude Opus analyzes the full transcript and generates your score (0-100), your certified level, and a detailed written report. Your badge is available and shareable within minutes.
Your score out of 100 translates into a level a recruiter can grasp at a glance.
You know the basics of Laravel: routing, controllers, Blade templates, simple migrations, and CRUD operations with Eloquent. You've followed tutorials or built a personal project, but you haven't worked with Laravel in production and struggle to explain architectural decisions or the framework's internal mechanics.
You use Laravel in a professional or collaborative context. You're comfortable with Eloquent relationships, middlewares, form requests, and Sanctum for API authentication. You've set up queues and run migrations in production. You can spot N+1 issues but haven't yet optimized high-traffic systems or architected complex solutions from scratch.
You design robust Laravel architectures in production: you optimize Eloquent with eager loading and lazy collections, supervise Horizon workers with Redis, choose between Sanctum and Passport with clear reasoning, integrate Livewire or Inertia based on project constraints, and own CI/CD pipelines. You can mentor junior developers on the framework.
You know Laravel's internals deeply: the service container, macros, the tap helper, pipeline patterns. You weigh Laravel against Symfony for business reasons, contribute to or maintain open-source packages, have executed zero-downtime migrations on critical databases, and track new Laravel primitives like Pennant, Folio, Volt, and Reverb as soon as they ship.
No degree or years of experience required to take the badge. Here are the profiles it makes the most sense for.
The badge gives recruiters objective proof that your Laravel skills go beyond a checkbox on your resume. You answered live questions on Eloquent optimization, queue architecture, and API authentication — with a verifiable score to back it up.
Add your badge to your Upwork, Toptal, or LinkedIn profile to build trust with new clients from the first touchpoint — especially on sensitive topics like production migrations, API security with Sanctum, or Horizon worker configuration.
Ask shortlisted candidates to take the badge before the technical interview. You get a consistent set of scored reports on the same criteria (Eloquent, architecture, production experience), so you can focus your interview time on the gaps that matter.
You've finished a Laravel course and want external proof of your level to stand out from other junior candidates. The badge gives you a credible, third-party-evaluated credential to attach to your job applications and portfolio.
You build React or Vue on the frontend and Laravel APIs on the backend, but your CV doesn't capture your backend depth. The badge certifies specifically your Laravel expertise — Sanctum, Horizon, migrations, and Eloquent — separate from your frontend work.
Where and how your PHP / Laravel badge will help you day to day.
You attach your badge link to a job application for a senior Laravel engineer position. The recruiter sees a score of 81/100 at Advanced level, with a report that highlights your strengths in Eloquent and queues and flags Passport as an area to explore. The technical interview skips the basics and goes straight to architecture.
A startup is choosing between you and another freelancer to rebuild their Laravel API. You share your certified badge: the client can see you explained live how to handle a risky production migration with a rollback plan and how to supervise Horizon workers. The decision is easy.
You take the badge and score 52/100 at Proficient level. The report pinpoints gaps in queue configuration and Horizon supervision. You study those areas, take the badge again three months later, and reach Advanced. Two badges that tell a concrete progression story.
As a hiring manager, you ask all five shortlisted Laravel candidates to complete the badge before meeting them. You receive five comparable reports scored on the same dimensions — Eloquent, architecture, production experience, communication — and use them to personalize each technical interview.
You add your PHP / Laravel badge URL to your Toptal or LinkedIn bio. Clients comparing multiple profiles immediately see you have an AI-evaluated certification, not just years of experience. Your inquiry-to-project conversion rate improves.
A CTO wants to map the Laravel skill levels across a team of eight developers before migrating to an architecture using Horizon and Inertia.js. Each developer takes the badge: the results show who can lead the technical workstreams and who needs targeted upskilling before the migration starts.
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.
Your overall score and certified Laravel level (Novice, Proficient, Advanced, or Expert) are calculated immediately after the session by Claude Opus, based on the full transcript of your answers.
A written report breaks down your performance on each criterion: Eloquent mastery, architectural reasoning, production experience, communication clarity, and ecosystem awareness — with specific observations tied to your actual answers.
Your session audio is securely stored and accessible only by you. You can replay it to pinpoint where you hesitated on Horizon supervision or SPA token management, and use those moments to guide your next study session.
Your PHP / Laravel badge lives at a unique URL you can drop into your CV, LinkedIn profile, GitHub bio, or a job application. Any recruiter or client can verify your score and level with a single 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
