How to Hire a Shopify Developer

Why this role matters

A Shopify developer changes the store your customers buy from. Good work makes product pages faster, checkout cleaner and merchandising easier for your team to run without code. Poor work leaves you with an edited theme that breaks on the next update, slow pages full of leftover app scripts and customisations nobody else can maintain.

Where to find candidates

• The Shopify Partner Directory, which lists agencies and freelancers by service, region and specialism
• Shopify Community forums, where active developers answer technical questions in public
• Freelance platforms such as Upwork, Toptal and Contra, filtered for Shopify and Liquid work
• GitHub, searching for public Shopify themes, apps or Hydrogen projects
• Referrals from other Shopify merchants in your category, and from the app vendors you already use
• Ecommerce agencies if the project needs design, development and ongoing support together

Skills to look for

Red flags

• Wants to edit your live theme directly instead of working on a duplicate or a development store
• Asks for your owner login rather than a collaborator or staff account with limited permissions
• Suggests installing several apps for jobs a few lines of theme code would handle
• Portfolio links point to stores they cannot explain their own part in
• Cannot say how their changes will survive a theme update
• Vague about who owns the code for a custom app or private theme

The interview process

1. 1

   Scope the work

   Write down what you need: theme changes, a new theme, a custom app, integrations or a migration. Note your Shopify plan, current theme, key apps and any deadline such as a sale launch.

2. 2

   Portfolio and code review

   Ask for two or three stores they worked on and what they personally built. Where possible, ask for a code sample or a public repository so you can see how they structure sections and settings.

3. 3

   Technical conversation

   Ask how they would handle a real request, such as adding a size guide that merchandisers can edit per product. Listen for metafields, theme editor settings and testing on a duplicate theme.

4. 4

   Paid test task

   Give a small, paid task on a development store or a duplicate theme, such as building a custom section with editable settings that works on mobile. Review the code, the editor experience and how they handed it over. A job simulation of the real work is one option if you are comparing several developers.

5. 5

   Terms and references

   Agree scope, store access level, code ownership, support after launch and how changes are deployed. Speak to one or two past merchants about reliability and communication.

How to evaluate

• Changes built so non-developers can edit them in the theme editor
• Clean, commented Liquid and no edits to core files without reason
• Mobile behaviour and page speed after their changes
• Use of version control and a safe deployment route to the live theme
• Sound judgement on app versus custom code
• Clear communication on cost, scope changes and timelines

Onboarding

• 1Add them as a collaborator or staff account with only the permissions the work needs
• 2Duplicate the live theme or set up a development store before any changes start
• 3Connect the theme to a GitHub repository so every change is tracked
• 4List your installed apps and which ones are critical to sales
• 5Agree a release checklist covering mobile, checkout, analytics tags and speed before going live

Common questions