roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Laravel 13 interviews: routing, the container, Eloquent, Blade, validation, auth, queues, testing and production, plus Livewire, Inertia, Octane and first-party packages.
733 of 733 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 733 new. 0 cut, outside your plan.
In PHP backend and full-stack loops, Laravel tends to arrive through code you wrote rather than through a dedicated round, often a take-home: a small API or CRUD application, followed by an hour in which the interviewer reads it with you. That review is where framework knowledge gets tested, and it starts from your code. Why does the index page run one query per row, and what would `with()` or `Model::preventLazyLoading()` have shown you? Why is `Model::create($request->all())` safe only behind `$fillable`? Why does the ownership check belong in a policy rather than the controller? Answers separate on what a controller never shows. Having built features, you can say what a facade calls. Having run Laravel in production, you can say why `env()` returns null once `config:cache` has run, why a job dispatched inside a database transaction can reach a worker before its row is committed, why workers serve the old code after a deploy until `queue:restart`, and why a singleton that captured the request leaks one user's data into the next under Octane. From middle level up, expect one of these as a follow-up to something you wrote.
The plan opens on the application before any feature: its [boot and dispatch sequence](/topics/be-laravel-foundations-lifecycle), the config that sequence reads, Artisan, and [Composer](/topics/dev-composer), whose manifest is where package discovery finds a third-party service provider. The [service container](/topics/be-laravel-service-container) then gets a module of its own, ahead of HTTP, because nearly everything after it is resolved through it: controllers, middleware, form requests and the object behind every facade. The next stretch follows a request in. Routing comes first, with [route model binding](/topics/be-laravel-routing-controllers-model-binding) handing the controller an already loaded model, then controllers, middleware and the request and response objects. Input and access checks come straight after, since [form requests](/topics/be-laravel-validation-form-requests), [gates and policies](/topics/be-laravel-auth-gates-policies) and CSRF protection are hooks on that same path. Persistence starts from [Eloquent](/topics/be-laravel-eloquent-migrations) and only then goes down to the [query builder](/topics/be-laravel-database-query-builder) and migrations beneath it: the model is what interviewers ask about, the builder explains the SQL it sends. The [atomic locks](/topics/be-laravel-cache-atomic) kept beside the cache return later, when scheduled tasks and unique jobs need them. The interface stretch weighs [server-driven pages against an SPA](/topics/be-laravel-frontend-tradeoffs) before either answer, [Livewire](/topics/be-livewire) or [Inertia](/topics/fe-inertia). Background work then moves code out of the request: [queues and jobs](/topics/be-laravel-queues-jobs), the scheduler, events and their outbound channels. After helpers and the official add-ons, Laravel's own testing layer, with its [fakes](/topics/be-laravel-testing-fakes), and diagnostics come before PHPUnit and [Pest](/topics/dev-pest), the runners underneath. Production closes the plan, and [Octane](/topics/be-octane) comes last on purpose: it keeps the application booted between requests, removing what every earlier module could take for granted, that each request starts fresh.
Coming from another PHP framework, the gap is conventions, not the language. Read from the container module through persistence in plan order, which is what by topics gives you: facades replace explicit service wiring, and Eloquent's active record parts ways with a Doctrine-style data mapper exactly where interviewers probe, in mass assignment and relations loaded on property access. From Rails or Django the patterns look familiar, so spend the time on the boot sequence, queues and Octane, where PHP's per-request model differs from yours. If the loop starts with a take-home, build it first and come to the page afterwards. With importance at must know and study order on random, it works as a mock review: each question you cannot answer about code like yours is a gap to close before the call. A junior posting seldom reaches Octane, Horizon or Passport; for such a posting, cap level at middle and let those three wait. The plan assumes the PHP underneath. The language itself, its types, classes, traits and enums, belongs to the [PHP roadmap](/roadmaps/php), and an enum in your take-home may well be asked about as PHP. The Inertia adapters are covered here; the components they render belong to the [React](/roadmaps/react) or [Vue](/roadmaps/vue) roadmap.
In PHP backend and full-stack loops, Laravel tends to arrive through code you wrote rather than through a dedicated round, often a take-home: a small API or CRUD application, followed by an hour in which the interviewer reads it with you. That review is where framework knowledge gets tested, and it starts from your code. Why does the index page run one query per row, and what would with() or Model::preventLazyLoading() have shown you? Why is Model::create($request->all()) safe only behind $fillable? Why does the ownership check belong in a policy rather than the controller?
Answers separate on what a controller never shows. Having built features, you can say what a facade calls. Having run Laravel in production, you can say why env() returns null once config:cache has run, why a job dispatched inside a database transaction can reach a worker before its row is committed, why workers serve the old code after a deploy until queue:restart, and why a singleton that captured the request leaks one user's data into the next under Octane. From middle level up, expect one of these as a follow-up to something you wrote.
The plan opens on the application before any feature: its boot and dispatch sequence, the config that sequence reads, Artisan, and Composer, whose manifest is where package discovery finds a third-party service provider. The service container then gets a module of its own, ahead of HTTP, because nearly everything after it is resolved through it: controllers, middleware, form requests and the object behind every facade.
The next stretch follows a request in. Routing comes first, with route model binding handing the controller an already loaded model, then controllers, middleware and the request and response objects. Input and access checks come straight after, since form requests, gates and policies and CSRF protection are hooks on that same path.
Persistence starts from Eloquent and only then goes down to the query builder and migrations beneath it: the model is what interviewers ask about, the builder explains the SQL it sends. The atomic locks kept beside the cache return later, when scheduled tasks and unique jobs need them.
The interface stretch weighs server-driven pages against an SPA before either answer, Livewire or Inertia. Background work then moves code out of the request: queues and jobs, the scheduler, events and their outbound channels. After helpers and the official add-ons, Laravel's own testing layer, with its fakes, and diagnostics come before PHPUnit and Pest, the runners underneath. Production closes the plan, and Octane comes last on purpose: it keeps the application booted between requests, removing what every earlier module could take for granted, that each request starts fresh.
Coming from another PHP framework, the gap is conventions, not the language. Read from the container module through persistence in plan order, which is what by topics gives you: facades replace explicit service wiring, and Eloquent's active record parts ways with a Doctrine-style data mapper exactly where interviewers probe, in mass assignment and relations loaded on property access. From Rails or Django the patterns look familiar, so spend the time on the boot sequence, queues and Octane, where PHP's per-request model differs from yours.
If the loop starts with a take-home, build it first and come to the page afterwards. With importance at must know and study order on random, it works as a mock review: each question you cannot answer about code like yours is a gap to close before the call. A junior posting seldom reaches Octane, Horizon or Passport; for such a posting, cap level at middle and let those three wait.
The plan assumes the PHP underneath. The language itself, its types, classes, traits and enums, belongs to the PHP roadmap, and an enum in your take-home may well be asked about as PHP. The Inertia adapters are covered here; the components they render belong to the React or Vue roadmap.