Hi everyone,

I have an upcoming technical interview for a Drupal-focused full-stack role, and I would appreciate some guidance from experienced Drupal developers.

From my conversation with the interviewer, I expect the interview to involve reviewing existing code, tracing complete workflows, identifying production issues, and explaining improvements. The organization is also planning work around upgrading from Drupal 10 to Drupal 11.

The areas I believe may be covered include:

• Custom modules, routes, controllers, services, entities, and forms
• Twig, Drupal behaviors, AJAX, and JavaScript
• Caching, queues, cron, and external API integrations
• SQL, database consistency, and performance
• Testing and deployment
• Drupal 10-to-11 upgrade readiness
• Composer dependencies, deprecated APIs, and contributed-module compatibility

My background is stronger in general software engineering than in PHP and Drupal. I have been using AI-assisted exercises and small Drupal code-review challenges to prepare, but I want to make sure I am learning the right concepts and not developing an unrealistic understanding of production Drupal work.

For someone interviewing at roughly the three-year experience level:

1. What Drupal concepts would you consider essential?
2. What code-review or debugging exercises should I practice?
3. What questions are commonly asked about Drupal 10-to-11 upgrades?
4. How deeply should I understand Symfony, Composer, Drush, testing, SQL, and deployment?
5. What mistakes do candidates commonly make in Drupal technical interviews?

Any practical examples, learning resources, or advice about what to prioritize would be greatly appreciated. Thank you!

Hey, i am looking for drupal freelance opportunity. I have 10+ years experience in monolithic, hybrid and headless drupal architecture. Any help would be appreciated

I'm open for freelance jobs, located in Denmark, got experience on expert level since Drupal 4.7 beta ~2006.

https://www.drupal.org/u/ramlev

Hello everyone, i am looking for freelance drupal opportunities. I have 10+ experience in drupal development.

I'm trying to prevent a page from being restored from the browser's Back/Forward Cache (bfcache) in a Drupal site.

I have the following response headers set:

Permissions-Policy: unload=() Expires: 0 Pragma: no-cache Cache-Control: no-store, no-cache, must-revalidate, max-age=0, private 

My understanding was that these headers would prevent caching, but the page is still being restored from bfcache when navigating back and forward.

Am I missing something? Do these headers have any effect on bfcache, or is there another recommended way to prevent a page from being stored and restored from bfcache?

Private files are accessible through URL regardless of taxonomy access.

I have a site with a multi tenant situation including different roles for each tenant. I'm managing access to content through taxonomy terms and views, which works well so far. However, I have different file types that should be accessible to different roles within one tenant. Content or files of one tenant should never be visible to anyone (user or role) of another tenant.

I have only found the global access permission "view media". When that is not checked for my role, I can't access the file even though I see it in the view (which makes sense). However, when that is checked for the role, the role has access to any file (including other tenants) through the url (even if they don't have access to the view that would link to the file).

Is there a module that can differentiate view media permissions by media type? My research only showed small, instable or experimental modules.
Or do you have any other suggestions on how I could solve this issue?

Hello everybody,

I'm helping customers with specific types of sites (similar to customer portals) which often contain some part of basic functionality and a lot of custom ideas.

My approach is usually 0 code (if I can avoid it).

So I'm really deep inside configuration / modules / etc.

Parts can be easily exported as configurations / recipes.

Some other parts are often quite custom.

Custom views with custom permissions, tags, ECA etc.

I see some customers / people I know just vibe coding everything in Lovable and similar solutions and I'm still clicking around in the admin area.

For the configuration / site building part of Drupal where you configure specific modules etc.:
Do you use any AI?
How to improve building speed there?

(not talking about Canvas landing pages - more features like inquiries, customer dashboards etc.)