Most Shopify developer hiring goes wrong in the first 24 hours — at the brief stage, not the interview. By the time you're talking to candidates, you've already shaped your decision space.
This is what we'd tell ourselves if we were hiring a Shopify developer cold today. The four questions. The take-home brief. The red flags.
Hourly vs dedicated vs project.
Pick the wrong engagement model and you'll over- or under-pay regardless of who you hire. The rule:
-
Hourly · £45–£140/hr
Defined sprints, bug fixes, audits. Anything you can describe as "this thing, by then".
-
Dedicated monthly · £2,200–£6,500/mo
Continuous backlog. >80 hrs/month for three months running. Same person every week.
-
Project contract · 30/40/30
Defined-scope deliverable. Migration, app build, theme rebuild. Fixed price, not hourly meter.
Where to find candidates.
The honest hierarchy, ordered by quality (best to worst):
- Specialist UK Shopify developer networks / boutique studios (us included). Vetted, with PM oversight in UK working hours. £45–£140/hr. Highest signal.
- Shopify Experts directory. Variable quality but Shopify-vetted at minimum.
- Toptal / Lemon.io. Strong generalist engineers; Shopify specialism is rarer. $150–$250/hr.
- LinkedIn outbound. Higher effort, lower noise. Senior UK Shopify devs are findable here.
- Upwork / Fiverr. Wide pool at low rates ($20/hr median). Workable when you have in-house tech leadership to vet, brief, and PM developers yourself.
The four interview questions.
Skip the LeetCode. Skip the "tell me about a challenging project". Ask these four. Listen to specifics.
- "Walk me through how you'd migrate a Shopify Script to a Function — pick a discount script." Tests: do they know Functions exist, do they understand Rust/JS deployment, do they know the GraphQL Admin shape. Bad answer: "I'd Google it." Good answer: walks through `cargo shopify` workflow and discount eligibility logic.
- "What's the difference between section groups, sections, and blocks in OS 2.0?" Tests: theme architecture fluency. Bad answer: confusion. Good answer: clear hierarchy, plus opinion on when to use each.
- "How do you debug a checkout extension that's not firing?" Tests: real production debugging. Bad: "console.log". Good: mentions extension targets, App Bridge, the specific permission scope issues, dev console behaviour.
- "What's a Shopify project where you said no to a client request?" Tests: judgement, not just compliance. Bad answer: "I always say yes." Good answer: a specific story about pushing back on a misguided spec.
The take-home brief.
Take-homes are extractive when they're 9 hours. They're useful when they're 90 minutes and reflect actual work. Here's the brief we use:
90-MINUTE TAKE-HOME
Given a Shopify dev store (we provide), build a custom OS 2.0 section that displays related products on the PDP. Filter by tag. Limit to 4. Use metafields where appropriate. Provide 30 minutes of written commentary on your trade-offs.
Things this catches: theme dev fluency, metafield instinct, ability to write about technical decisions. Things it doesn't catch: long-form architecture skills (use the interview for those).
Red flags.
- Portfolio of brands you can't verify. Ask for the URL. If the brand can't be reached, it didn't happen.
- "I do Shopify and WordPress and Magento and Webflow." Generalists exist; great Shopify generalists are rare. Specialism is the moat.
- No questions about your business. A senior dev asks about your customers before your codebase.
- Time-zone hand-waving. If they can't commit to a 4-hour UK overlap, the engagement will degrade.
The £45 vs £200/hr question.
The honest answer: skill exists at every band. Reliability and accountability cluster in the middle. Below £45/hr, you're hiring against your own time as the project manager. Above £150/hr, you're funding agency overhead — not better engineering.
Most UK mid-market work belongs at £85–£120/hr for senior. That's where the supply is best, the accountability is real, and the cost-to-output ratio is sane.
