To hire a Shopify developer, give every candidate the same short ticket on a development store and read what they build, ask and document. Then check how they diagnose a slow page and how they ship changes with version control, before anyone touches a live theme.
If you want a Shopify Developer already tested on agency tickets, start a Direct Hire brief or explore Managed Teams. Compare both on the pricing page.
Key facts
- Shopify's developer documentation says sections are Liquid files that create reusable modules merchants can customize. JSON templates and section groups can render up to 25 sections, and each section can have up to 50 blocks. Checked 10 November 2026.
- The same documentation says section and block files must define presets in their schema to be added to JSON templates through the theme editor. Checked 10 November 2026.
- Shopify's GitHub integration for themes can connect branches to unpublished or published themes, and commits changes made in the Shopify admin back to the connected branch. Checked 10 November 2026.
- Google's web.dev says sites should aim for a Largest Contentful Paint of 2.5 seconds or less, measured at the 75th percentile of page loads across mobile and desktop. Last updated 4 September 2025; checked 10 November 2026.
- UK workplace advisory body Acas says unpaid work trials should be for a reasonable time, for example 2 hours or a shift, and not usually longer than one day. Updated 30 June 2026; checked 10 November 2026. Acas guidance addresses UK recruitment, so check the rules where you and the candidate are based.
What should the developer own?
Decide the tickets before you recruit. Theme work such as sections, templates, metafield-driven content and app-block integration is a different job from architecture, migrations or custom app builds. Staff Stack's Shopify Developer role takes tickets inside an existing Shopify project, while architecture calls stay with your senior developer. For storefront styling and section work see the Shopify Theme Developer role, and for Shopify Plus work such as Flow, B2B and Markets see the Shopify Plus Architect role.
Write down the five most common tickets from your backlog, who reviews each one, and who may publish to the live theme. Candidates should be judged against that list, not against every Shopify skill.
How do you run a test ticket?
Give each candidate the same ticket on a development store or unpublished theme, with fictional products and content. Tell them the time allowed, the tools they may use and how it will be scored. Never use a live client theme for the test.
A good ticket is small and realistic. For example: "Build a reusable section with a heading, an image and a configurable layout. Add schema settings and a preset so a merchant can add it in the theme editor, then write a short note on what you built and what you would check before release."
Read the result for three things. First, did they ask clarifying questions before writing code? Second, does the section follow Shopify's structure, with a schema and a preset? Third, does the note explain what changed and what remains uncertain?
Keep the sample short. If you want a larger task, treat it as paid work, and never ask candidates to do work that has value to you beyond testing their skills.
How do you test performance thinking?
Ask for a written diagnosis rather than a fix. Give candidates a fictional product page with a slow Largest Contentful Paint and ask what they would measure, in what order, and what they would change first.
Strong answers name the metric, say how they would measure it with tools such as PageSpeed Insights or Lighthouse, and separate lab results from field results. web.dev lists these as field and lab tools for measuring LCP. They also describe the likely causes they would check, such as the hero image, render-blocking scripts and third-party app code, and say what they cannot tell without access to real data. A one-line answer such as "compress the images" is a weak result.
How do you check version control and deployment?
Ask how they would ship a change without editing the live theme. A sound answer uses a branch, an unpublished or development theme, a review step and a named person who approves publishing.
Shopify's GitHub integration shows one way to do this: connect a branch to an unpublished theme so code changes and admin edits stay in sync. Ask what they would do if a merchant edits the theme in the Shopify admin while they are working on the same file. Shopify's documentation warns that the code editor has no conflict alerts and that its version of a file overwrites the GitHub version, so a candidate should know to coordinate edits.
Which interview questions should you ask?
Ask the same core questions of each person, then follow up. Acas says it is a good idea to ask each applicant the same questions where possible.
- "What is the difference between a section and a block, and when would you use each?"
- "How would you let a merchant add your section to a page from the theme editor?"
- "A product page has a poor Largest Contentful Paint. Walk me through your diagnosis."
- "How do you deploy a change so the live theme is never edited directly?"
- "Tell me about a ticket that went wrong. What did you miss and what changed afterwards?"
- "What would you ask me before starting this ticket?"
Listen for specific steps and honest limits. Candidates who name tools but skip checks, or who would edit the live theme to save time, are a warning sign.
How do you score the candidates?
Agree the criteria before you see any work and score everyone on the same scale, using a range wide enough to separate candidates. Have a second reviewer score independently and record the evidence for each score.
Code and structure
- Evidence: The section follows Shopify's structure, uses a schema and a preset, and is readable.
Questions and scoping
- Evidence: They asked what they needed before building and said what they assumed.
Performance reasoning
- Evidence: They name a metric, a measurement method and an order of investigation.
Release discipline
- Evidence: They use a branch, a non-live theme and a review step.
Handoff
- Evidence: Their note says what changed, what to test and what is unresolved.
How do Direct Hire and Managed Teams compare?
Compare both options against the same role, schedule and support needs. With Direct Hire, discuss the placement and the responsibilities your agency will take on. With Managed Teams, discuss the ongoing support and how responsibilities are shared. Staff Stack lists the Shopify Developer role at USD 3,200 to 4,800 per month, which is the role's current monthly pricing band; your quote depends on the operator and scope. Estimate a team budget with the operator cost calculator, and ask Staff Stack to confirm the employment, payroll, management and review arrangements before you choose.
For how Shopify agencies use operators, see Shopify agencies and the Shopify agency page. For handoffs and review across time zones, see offshore team management.
Frequently asked questions
How do I test a Shopify developer before hiring?
Give every candidate the same short ticket on a development store, such as building a reusable section with schema settings and presets, plus a written diagnosis of a slow page. Score code quality, questions asked, documentation and handoff against criteria set in advance.
What should a Shopify developer know?
For theme work, expect fluency with Liquid, JSON templates, sections and blocks, and app blocks. Also check how they measure page speed and how they use version control. Match the list to the tickets your agency actually has.
Should a Shopify developer test be unpaid?
Acas, the UK workplace advisory body, says an unpaid work trial should be for a reasonable time, for example 2 hours or a shift, and not usually longer than one day. It says the minimum wage must be paid if the trial is not genuinely for recruitment. Treat any larger task as paid work, and check the rules that apply to you.
Should a new developer edit the live theme?
No. Start them on an unpublished theme or development store, and connect a branch so changes are reviewed before anything goes live. Keep production publishing with a named approver.
Should I choose Direct Hire or Managed Teams?
Compare the responsibilities and support your agency wants, then ask Staff Stack to confirm the terms of each arrangement for your role. Review pricing before you decide.
Ready to describe the role? Start with Direct Hire or explore Managed Teams.