roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Symfony interviews on how the framework wires and serves a PHP app. Covers the service container, routing and kernel events, Doctrine, forms and security, and PHPUnit tests.
62 of 62 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 62 new. 0 cut, outside your plan.
Most PHP backend loops reach Symfony in their main technical round, or in the review call after a take-home built on the framework, where you defend why each piece is wired as it is. Many questions start from the request: what happens between public/index.php and the controller, and how a listener on kernel.request can return a response before any controller runs.
The container draws the most follow-ups: autowiring that fails because two services implement the same interface, or a service fetched with $container->get() that turns out to be private. Doctrine sits close behind: a new entity that flush() ignores because it was never passed to persist(), or a list page that fires one query per row through a lazy association. Security brings the order in which access_control rules are matched, and voters for what a role cannot express, such as whether this user may edit this post.
Much of the gap between levels is about time. An early-career candidate walks through a request as it runs. A stronger one places the container earlier, built once by compiler passes when the cache is warmed, so a missing dependency usually fails that build rather than the request that needs the service, and an %env()% parameter is still resolved at runtime while the rest is fixed into the dumped PHP. Senior candidates are also asked where the framework ends, for example why the mutable HttpFoundation Request is not a PSR-7 message.
Composer opens the plan because a Symfony application is a Composer project before it is anything else. The generated autoloader is how every class under src/ gets found, the lock file decides which versions reach production, and Symfony Flex, which installs recipes, is itself a Composer plugin.
The framework module then takes its components in the order a request leans on them. The service container comes first, since controllers, listeners, voters and form types are all services and inherit its rules. Routing and controllers follow, and the event dispatcher after them explains what connected the two: the router runs as a listener on the kernel's request event, and so does the security firewall. Doctrine brings persistence in, and security comes after it because a user provider usually loads users through the entity manager. Forms and validation close the module by drawing on what came before: an entity to map onto, a CSRF token, constraints checked against submitted data.
Only then does the plan step outside Symfony, to the PHP-FIG standards. Read after the framework, most of them look familiar: the container answers PSR-11, the dispatcher PSR-14, the cache component both caching PSRs, while the HTTP message interfaces show by contrast where Symfony kept its own model. PHPUnit comes last, and its mocks and stubs depend on the seams the container created: a collaborator injected through the constructor is one a test can replace.
A developer arriving from Laravel has the most to unlearn in the framework module. Facades and global helpers give way to explicit constructor injection, and Doctrine is a data mapper: an entity does not save itself, and changes wait in the unit of work until `flush()`. Of the study orders, by topics suits this reader best: it reaches the container before the controllers and listeners that depend on it, and Composer, which comes first, can be skimmed as revision. Someone with years on a Symfony app knows most of that module by use, and should spend the hours where use hides the mechanism: compiler passes, listener priorities on the kernel events, voters. If the technical call is close, the cut falls mostly on the edges of the plan. With importance raised to must know and level trimmed to the seniority the posting names, what survives of Composer and the standards fits into an evening; the remaining days belong to the framework module, whose most-asked questions come first while study order is left on by frequency. The plan assumes the language underneath it: no module covers PHP itself, its type system, classes and traits, or the shared-nothing model that discards state after each response. If your PHP predates typed properties and enums, the [PHP roadmap](/roadmaps/php) is the place to begin. A loop that adds a system design round moves on to queues, replication and service boundaries, which no framework answers; prepare those on the [Backend Developer roadmap](/roadmaps/backend).
A developer arriving from Laravel has the most to unlearn in the framework module. Facades and global helpers give way to explicit constructor injection, and Doctrine is a data mapper: an entity does not save itself, and changes wait in the unit of work until flush(). Of the study orders, by topics suits this reader best: it reaches the container before the controllers and listeners that depend on it, and Composer, which comes first, can be skimmed as revision. Someone with years on a Symfony app knows most of that module by use, and should spend the hours where use hides the mechanism: compiler passes, listener priorities on the kernel events, voters.
If the technical call is close, the cut falls mostly on the edges of the plan. With importance raised to must know and level trimmed to the seniority the posting names, what survives of Composer and the standards fits into an evening; the remaining days belong to the framework module, whose most-asked questions come first while study order is left on by frequency.
The plan assumes the language underneath it: no module covers PHP itself, its type system, classes and traits, or the shared-nothing model that discards state after each response. If your PHP predates typed properties and enums, the PHP roadmap is the place to begin. A loop that adds a system design round moves on to queues, replication and service boundaries, which no framework answers; prepare those on the Backend Developer roadmap.