How to Hire Drupal Developers: Finding the Right Talent

Say you already have your product specifications clearly written and you start "hunting" for the right Drupal talent for your project. Where should you start your searches? And, once you've found a pool of talent, how to hire Drupal developers who are the perfect match for your skillset requirements and who fit your organization's needs?

What recruitment strategies should you apply to... speed up things a bit?

What criteria should you use for filtering through your candidates?

What questions should you prepare for the selected Drupal developers and... what questions should you be asking yourself, too? About your project needs, scope, budget constraints...

Let's get you some answers.

Here's a handy checklist including 5 tips that'll streamline your searches and optimize your selection process:

1. First: What Is a Drupal Developer?

What does a Drupal developer do?

Generically speaking, a "Drupal developer" does a lot of things:

conducts researches, selects and installs those Drupal modules that fit your project's feature needs
develops new modules, from scratch, tailored to your project's needs
tweaks and extends existing modules so that they provide the precise functionality that you require
handles the look and feel of your Drupal website/app by creating a custom theme that meets CSS/HTML code standards
handles different PHP implementations
architects your Drupal solution incorporating data, display, and information infrastructure
migrates your existing websites to Drupal
puts together and runs performance-boosting strategies on your existing Drupal website

And this leads us to the 3 main Drupal roles that you might "bump into" while running your investigations.

Each one with a specific skill set to evaluate and to set against your own project's size and scope.

For instance, no need to look for a Drupal themer when it's a new functionality that you want to get developed and integrated into your website...

1.1. Drupal Site Builder

If your Drupal project doesn't require highly complex feature implementation or a PHP "guru", but rather someone who:

is familiar working with the latest versions of Drupal and, overall, with site frameworks
has basic Drupal project management skills
has a decent understanding of the essential concepts of JS and PHP code

... then a Drupal site builder experienced enough to put together core and the right contributed modules and create a fully functional website is what you need.

1.2. Drupal Front-End Developer

Looking for someone to "revamp" your Drupal site's presentation layer?

Or we're talking about a new project, that you want to make sure it'll deliver the best user experience?

Then a Drupal front-end developer (or themer) is what you should be looking for.

One that:

is experienced enough to develop new themes and to customize existing Drupal themes
has extensive knowledge in basic PHP, JS/JQuery, HTML, CSS
sticks to the best testing practices to ensure that the delivered theme is fully responsive and light enough not to impact your website's performance

1.3. Drupal Back-End Developer

Or maybe you need someone with proven expertise to set up a robust "bone structure" for your Drupal project?

One who can:

develop a whole new module, if needed, to fit specific functionality needs
tune an existing module till it meets your feature needs to the slightest detail
prove his/her expertise in CSS, Object-Oriented PHP, HTML, JS/Query

Note: a Drupal back-end developer's knowledge is not limited to code; a great one knows what goes into building a Drupal site, knows general design concepts and deployment best practices, as well.

Of course, the list of Drupal role doesn't end here. From Drupal Design/UX to Drupal Architecture, to Drupal Product Owner to Drupal DevOps Engineering... you could populate it with pretty much any level of specificity that you aim for.

Which brings us to the next question:

2. What's Your Project?

In order to find the answer to your "How to hire Drupal developers for my project?" question you should first try to answer:

What's my project scope?
What about its size?
Which are the general and (more) specific feature needs?

For, as you've already seen, there's a whole bunch of Drupal roles out there and selecting the right one(s) for your project can get challenging. To say the least...

So, to narrow down your options, identify and examine your needs:

is it Drupal maintenance that you need for your current website? Then you should get reasonable and not expect a lead Drupal developer to "jump" right in
is it a whole new enterprise-grade Drupal solution that you need? Then you might want to adjust your budget and time resources to the level of Drupal experience required and the complexity of your project
is it just back-end Drupal talent that you need, maybe just someone to integrate a new feature to your website? Or a... full-stack developer?

Do you just have a rough idea of what you'd like him/them to develop or clear wireframes and project specifications already laid down? Such as:

Drupal security updates
enhancing your website's overall performance
various eCommerce integrations
custom-built content tools

... etc.

Do you need a freelancer Drupal developer or a contract-to-hire? Or you'd like to go with a staff augmentation solution?

As you take the time to ask yourself all the right questions you gradually start to identify:

what level of experience you need
what skill set your project requires
whether you need a Drupal developer to pay specialized attention to a specific area of your project or a generalist
what technology stack your project depends on

While you have your "Aha!" moments, simply turn your answers into... job responsibilities.

3. How to Hire Drupal Developers: Where to Look?

OK, now that you've identified your skillset needs and included them in your job description, it's time to "go hunting".

"But where can I find developers that have experience working with Drupal?"

You can run passive or active searches or... both.

Top channels to consider for passive searches:

job portals like LinkedIn, Monster, Glassdoor, Indeed ...
online Drupal (or PHP) communities
freelance platforms like Upwork, Toptal, Scalable Path

Top channels for your active searches:

social media Drupal groups
local IT communities
LinkedIn (when you start analyzing particular profiles on LinkedIn your passive search becomes... active)
Drupal.org (select the top Drupal profiles there and start evaluating them against your own requirements)
developer communities like GitHub, Stack Overflow

Note: an effective way to identify the perfect match is to delve deep into those profiles and evaluate those developers':

portfolios; are there any projects in there similar to yours?
Drupal roles that they "played" in different projects that they worked on
type of questions they posted
proof of them volunteering in different Drupal projects
documentation skills

Also, keep in mind to run a deep scan of the candidates' own social media profiles, as well. They're often packed with valuable information like:

number of connections within the Drupal community
number of projects that they've worked on, time spent on each of them and... number of clients, as well (is he prone to working with the same client on multiple projects?)
developer groups that he's joined
client feedbacks

4. 4 Questions to Ask Your Candidates

So, you've shortlisted your candidates and your "How to hire Drupal developers?" dilemma has turned into:

"How do I... know which is the best Drupal talent for my project?"

Here are 4 questions to ask them (among other things), which will speed up your "identification" process:

What techniques would you apply to enhance a Drupal website's performance?
What modules do you find essential, irrespective of the projet's scope?
Do you have a Drupal project portfolio that I can have a look at?
Have you contributed to developing or improving any Drupal modules?

5. What to Look for in a Drupal Developer: 8 Things to Evaluate

Level of experience, community involvement, proven expertise reflected in the projects that he's worked on, certifications... what precisely should you analyze first when you're evaluating your candidates?

Since the number of aspects that you could be checking can get... overwhelming, here's a shortlist of things to look into to identify your best match from a group of potential candidates:

5.1. GitHub Profile

It's a never-ending source of priceless information about your candidates:

how much time they spent on different projects
samples of their written code
details on their contributions

5.2. Experience Level

And here, what you should pay attention to is the no. of Drupal versions that they've worked with. The more... the merrier.

The more experienced that particular candidate is, the more familiar he is with Drupal's specific "roadblocks" and how to address them.

5.6. Technical Expertise

How do you assess their level of technical expertise? There are 2 straightforward methods to apply:

ask your candidates to review some of their own code
challenge them with a specific scenario: a challenge that they should find a custom solution to (e.g. "What module would you use to...?")

5.7. Community Involvement

An experienced Drupal developer is (most of the time) an active member of the Drupal community, as well.

Look for profs of his/her active involvement: discussions where's he used his expertise to help out other developers, contributions to different projects...

5.8. Client References

Are there any client references online to have a look at? If not, can he/she give you any references that you could talk to?

And this is particularly important if it's Drupal agencies that you're evaluating.

The END!

These are the 5 aspects to look into for finding your personalized answer to the "How to hire Drupal developers" question. Happy "hunting"!

Photo by Kaleidico on Unsplash

We do Web development

Go to our Web development page!

Visit page!

Recommended Stories

Drupal Drupal 8 Tips

10 Best Headless CMS in 2020, That Cover Most of Your Requirements (Part 2)

Ready to compare the features of 5 other best headless CMS in 2020? We've got them ready for you to just dive in and: survey the key reasons why you'd want to choose one over the other discover each one's main use cases narrow down your options … and pick the one that matches your requirements. What Is the Best Headless CMS in 2020? 5.6. Directus An open source tool for managing and delivering content across an entire network of platforms and devices. And here are some of the top reasons for choosing Directus: it provides your editorial team with an easy to use admin app for managing content it can be in the cloud or self-hosted it provides API for your development team to fetch content 5.7. Netlify CMS One of your top 10 headless CMS options, an open source one, that you get to add to any static site generator of your choice. A React single-page application that provides you with an easy to use UI, playing the role of a… wrapper for your Git Workflow. Basically, when using Netlify CMS your content gets stored in your web app's git repository (as markdown files), close to your codebase. "How does a Netlify CMS Gatsby setup work?" It's pretty straightforward: You enter your content via that user-friendly interface, then Gatsby uses it to come up with the right pages for your web app. Why would you use it? it fits both large and small-sized projects, with fewer pages to create, add content to, to edit, and to manage you get to review/preview your content and make changes in real-time, and even control entries status in editorial workflow mode it provides you with an easy-to-use UI, with just 3 tabs: workflow, media, and content you're free to use it with any static site generator you get to extend its functionality: add your own UI widgets, editor plugins, customized previews, etc. 5.8. GraphCMS An API-first content management system, a GraphQL-native one, that allows you to distribute content across multiple digital platforms. And not just anyhow, but… within minutes. Your developer team gets to create content APIs in no time, whereas your content team gets all the tools they need for a smooth editor experience. Source: capterra.com GraphCMS vs Contentful: Main Differences GraphCMS works best for enterprise and mid-market companies, enabling them to build highly scalable applications GraphQL is its underlying technology: an open source query language for APIs, that's been growing more and more popular among developers Contentful targets top global brands, helping them distribute digital content experiences across complex networks of markets and channels REST is its underlying technology: a programming paradigm for distributed systems And here are 2 good reasons for choosing GraphCMS as your go-to headless content management system: you get a CMS that's client-side and JAMstack compatible you get to tap into the benefits of a JAMstack approach to development (JavaScript & Markup & API) 5.9. Cosmic A cloud-hosted headless content management system that provides you with both GraphQL and REST APIs. But What makes Cosmic one of the best headless CMS in 2020? Why choose the Cosmic Headless CMS? it ships with features like content modeling, media management, localization, and webhooks it grants you a smooth editor experience with its WYSIWYG editor, that you can use to incorporate (by embedding code) third-party services like Typeform and GitHub. it integrates smoothly with AWS, Slack, Algolia, Stripe, HubSpot 5.10. Kentico Kontent A cloud-based content delivery API that turns your structured content into content that's easy to be "consumed" by any device or digital platform that you might use as a front-end delivery layer. Why would you choose it over other great options of headless CMS? you get an AI chatbot when using Kentico Kontent it provides webhooks and custom elements that make third-party integrations a lot smoother you get content management API enabling content consumption And we've come to… the END of the list of 10 best headless CMS in 2020. Which one checks the most features off your list? If you're facing a "Headless Drupal 8 vs Contentful" dilemma, we're here to: help you identify the one that works best for your business and your requirements make your headless CMS-based project work Just drop us a line! Image by tdfugere from Pixabay ... Read more

Adriana Cacoveanu / Sep 26'2020

Drupal Drupal 8 Javascript Tips

10 Best Headless CMS in 2020, That Cover Most of Your Requirements (Part 1)

Overwhelmed with options? Are you building your first (e-commerce) headless CMS and you don't know what headless CMS platform to choose? What are the best headless CMS in 2020, so you can at least narrow down your choices and start... somewhere? Which system matches most of your feature requirements? Here's a top 10: 1. But First: What Is a Headless CMS, More Precisely? Relax, I won't bore you with too many details — we already have an in-depth post on the differences between headless and traditional CMS. So, if we were to sum up the concept in just a few words, we could say that: A headless content management system is an architecture where content is separated from the presentation layer (the client-side front-end). Meaning that you get to create, store, and edit "raw" content (with no design or layout) in the backend and deliver it wherever needed —wearable, mobile app, website — via API. In short, what you get in a headless architecture is: a database to store your content in a dashboard for editing your content Source: Zesty.io As for the "head" that serves your content to the end-user : you're free to build your own front-end, from the ground up … and even multiple front-ends, if needed, that will all use calls from the API to retrieve and display content 2. … Then What's a Decoupled CMS? Headless CMS vs decoupled CMS: what's the difference? And why headless over decoupled? The role that the API plays… That's what makes the difference (and why you'd want to go for a headless approach): If, in a decoupled architecture, the API plays the role of an intermediary between back-end and front end, in a headless architecture the API can be used by any of the front-end portions for pulling data. In other words, a decoupled CMS does come with a built-in front-end delivery layer, that you can rely on, but a headless approach is an API-driven content repository. Which gives you more flexibility for delivering content to any type of display layer. … to multiple "heads". You're free to distribute it wherever it needs to get displayed. 3. Why Choose a Headless CMS? Top 9 Benefits Before I "divulge" the best headless CMS in 2020 to you, here's a shortlist of the key advantages of using a headless CMS software: you get to engage your customers with personalized content across an entire network of digital channels, at different stages in their journey you can deliver richer digital experience, tailored to each channel you gain platform independence you're free to choose your technology of choice you benefit from cross-platform support you get to manage your content from a central location and distribute it to multiple platforms/IoT-connected devices, in a universal format you're free to manage all your platforms from one interface your development team gets to choose the development framework of their choice, integrate new technologies and, overall… innovate you're free to redesign as often as you need to, without the dread of re-implementing your entire CMS from the ground up 4. … And When Should You Use It? 5 Best Use Cases How do you know for sure that you need to adopt this approach? You know it because your scenario describes one of the following use cases for headless CMS: you're building a site using a technology you're familiar with you're building a website with a static site generator you're building a JS-based website or web app you're building a native mobile app you're building an e-commerce site and you know that the commerce platform you're using won't… cut the mustard as a CMS; or you need to enrich product info in your online store 5. What Are the Best Headless CMS in 2020? Top 10 "Which CMS should I use?" you wonder. "The one that meets most of your requirements…" So, you should start by pinning them down. What features are you looking for in a CMS? Maybe you need a system that should: be straightforward and easy to use for the marketers/non-technical people in your team be built on… Node be highly customizable and editable for your content team to be able to change overlay text, logo, background video/image be simple to set up integrate easily with Gatsby support multi-site setups not be tied up to (just) one specific database provide ease of content entry and rich-text support provide a granular permission system provide native support for content types What are the features that your project couldn't live without? Now, with that list of "mandatory" features at hand, just drill down through your top headless CMS options in 2020. Here they are: 5.1. Storyblok A purely headless CMS that ships with a visual editor, as well. Why would you go for Storyblok? What makes it one of the best headless CMS in 2020? it provides the experience of a page builder for all those non-technical users in your team: editors get to manage content via a more user-friendly interface it grants your developers easy access to the APIs they need 5.2. Prismic Its major selling point? It allows you to choose your own language, framework, technology… And these are the 3 good reasons to go with Prismic as your headless CMS: it allows you to model your content schema and to add your content you're free to choose whatever framework that meets your feature needs: React, Vue, Next, Nuxt, Node, Gatsby… you're free to choose either GraphQL or RESTful API to query content 5.3. Drupal 8 Headless CMS Another great option is to exploit Drupal's headless capabilities and pair them with the JavaScript framework of your choice. Here are some of the best reasons why you'd use a Drupal 8 API-first architecture: Drupal's a mature and enterprise-level headless solution backed by a wide community, used by more than 1 million sites globally; you get to tap into its massive module collection and even create new custom ones to extend your website's functionality its JSON:API follows the JSON:API specification; developers in your team can start using the API even if they're not experts in working with Drupal you get to load your GraphQl schemas straight from your Drupal content repository; there's a specialized module for this: the GraphQL module you get to use all of Drupal's famed features (granular access to content, processes, workflows, modules, etc.) right away; you get them out-of-the-box since the REST API is… rooted deep into Drupal 5.4. Strapi, One of the Best headless CMS for Gatsby. It's an open-source Node.js headless CMS, a "host it yourself" one, that allows you to build Node.js apps in… minutes. Why would you use it? because it generates available RESTful API or uses GraphQL shortly after installation, making data available via customizable API because it allows your developers to invest all their resources in writing reusable app logic (instead of having to use some of that time to build an infrastructure) because it's fully JavaScript because it supports plugins that extend the platform's functionality because it's open-source: you'll find the entire codebase on GitHub 5.5. Contentful Looking for a platform-agnostic solution? A… content delivery network that would enable your development team to manage and distribute (and reuse) content to multiple channels? Then this is the API-driven headless CMS you're looking for. Here are 6 other reasons why you'd want to put Contentful on your shortlist: consistent APIs easy to set up you're free to create your own models easy to use: ships with a robust, non-technical, user-friendly UI you get to add custom plugins quick and easy you get to set your own schemas to get displayed the way you want them to, across different apps Good to know! There's even a Shopify extension available. What it does is connect your online store to your content, stored in Contentful. And if you'll need help with building, fine-tuning, and integrating your content hub, we're ready to tweak Contentful to your needs. END of Part 1! Stay tuned, for there are 5 more candidates for the title of "the best headless CMS in 2020" waiting in line. Image by Couleur from Pixabay ... Read more

Adriana Cacoveanu / Sep 25'2020

Drupal Drupal 8

Drupal 9 Modules Readiness: How Hard Is It to Find Compatible Modules and Build a Website in Drupal 9?

Is it (still) too early to give Drupal 9 a try? To start fresh and build a website from scratch in the latest version of Drupal? Should you stick to Drupal 8 for... a little longer and upgrade later? How difficult will it be for you to find compatible Drupal 9 modules (and themes)? Let's find out: 1. But First: Why Drupal 9? What are the biggest benefits of Drupal 9 over Drupal 8? Why would you choose precisely this version of Drupal to build your new website with? because of the automated updates that it makes possible because of the headless support that it ships with because of the robust multilingual capabilities because of the improved performance: your web pages will load faster thanks to the BigPipe technology because it removes a lot of the legacy code because of its layout features because of its extensibility: you get to incorporated third-party systems quick and easy because of its media library and robust media functionality because of the new, Twig-based theme engine because it's easier to use: you can make the most of its in-place editing (CKEditor) And particularly because there will be no more major re-builds (aka "major pains to upgrade"). Instead, a set of new features gets released every 6 months, including new improvements and additions to be incorporated seamlessly into your Drupal 9 build. 2. Most Drupal 9 Modules Don't Change at All So, stay assured: you won't be having a hard time finding compatible modules for your new Drupal 9 website. Many of the modules on Drupal.org have been, are being made, and will be made compatible with Drupal 9. There's a collective effort coming from the Drupal community in this direction. And where do you add that the process is pretty straightforward: Same code, but without the deprecated APIs. 3. But What About Those that Do Need Changes? For there have been changes under Drupal 9's hood. Changes in coding with a direct impact on some modules and APIs. Which means that some modules have turned from Drupal core modules to... outside dependencies: this is good news, considering the performance gains you get but also a challenge if you were relying precisely on those modules for your Drupal 9 website Luckily, you have at least 2 helpful tools at hand that you can use to: identify the Drupal modules that still need to get updated apply the fixes needed to make those modules compatible with Drupal 9 3.1. The Upgrade Status Module Why use it? Because it offers you a view of all that has been changed in Drupal. Source: Drupal.org You have links to the modules' pages there, that you can access to review those changes. 3.2. The Upgrade Rector Module The great thing about this tool is that it provides you with automated code fix suggestions to help you make your target modules Drupal 9 compatible. Source: Drupal.org 4. Some Module Get Removed from Drupal 9 Now, there are a few Drupal modules that didn't get the chance to grow into Drupal 9 modules. And I'm talking here about: Simple Test, that's now replaced by PHPUnit Place Blocks, now replaced by the Layout Builder As you can see, in both cases you get to use better alternatives. So, it's just a matter of favoring more powerful solutions. Good to know! Expect other modules and themes (i.e. the Classy theme, the Stable theme) to get deprecated and removed by the time we reach Drupal 10. 5. What About the Contributed Modules? What if you need more than the out-of-the-box Drupal 9 modules to build your new website? What if you depend on particular contributed modules? Or on... many contributed modules? Well, then things get a little more challenging... Because many of the contributed Drupal modules still need to be made compatible with Drupal 9. They need some time to catch up with the new version of Drupal. Take for instance: updating tests to PHPUnit or updating deprecated API usages. Now, what you can do is give a helping hand to accelerate the updating of these modules. And the steps/best practices to follow are pretty simple, as suggested in this guide on Drupal.org : use the patch referred to here, create an issue in the module project (first, make sure it doesn't exist already), and choose a title suggestive enough to let the maintainer know that it needs to be tested for Drupal 9 deprecations add an explanation for the signaled issue ... and follow all the other steps suggested in that Drupal.org guide. Tip! Ask that contributed module's maintainer how he/she would like to address the issues you're signaling. Because the guidelines available for Drupal core aren't always relevant for addressing contributed module issues, as well. The END! Now, assuming that: you only need a limited no. of contributed modules for your new Drupal 9 build it's not a heavily customized website that you're building ... how do you get it up and running in? We're here to help. Just drop us a line! We've been building Drupal websites since... Drupal 5. Image by Siggy Nowak from Pixabay ... Read more

Adriana Cacoveanu / Aug 28'2020

How to Hire Drupal Developers: 5 Ways to Find the Right Drupal Talent for Your Project