How to Interview and Validate a Shopify Developer Before You Hire

Hiring a Shopify developer without a structured validation process is one of the most expensive mistakes a growing store can make. The right framework takes less than a week to run, surfaces real skill gaps before a contract is signed, and protects your store from the kind of technical debt that quietly kills conversions. Here is exactly how to do it.

Key takeaways

• Generic interview questions do not reveal platform depth. Shopify-specific scenarios do.
• The 2026 platform has changed enough that skills from 2022 hires are often partially obsolete.
• Checkout Extensibility, Shopify Functions, and the GraphQL Admin API are now non-negotiable checkpoints.
• A small paid test project reveals more than any interview round.
• Red flags are as important as green lights. Know what ends the conversation.

Why hiring for "Shopify" is no longer one thing

If you hired a developer in 2022, you were mostly screening for Liquid templating and CSS. That bar no longer reflects the platform. As of 2026, Shopify Functions replaced Scripts for custom pricing, discounts, and shipping logic, while Checkout Extensions replaced checkout.liquid for custom checkout UI. Hydrogen, Shopify's React-based headless framework running on the Oxygen edge network, is now the recommended path for brands that need full frontend control.

The result: "a Shopify developer" is no longer one role. You need to know which specialization your project requires before you write the job brief, let alone run an interview.

And the urgency is real. Since April 15, 2026, merchants can no longer create, edit, or update Shopify Scripts. Stores that did not migrate risk losing custom discounts, B2B pricing, shipping rules, and payment controls. Any developer you bring on who does not understand Shopify Functions is already behind the platform.

Step 1: Define the role before you open the brief

Before any interview, map your actual project needs to the correct developer type. Hiring a theme specialist for an app integration project wastes time for everyone.

In my 6+ years building and delivering 65+ stores, the single most avoidable hiring mistake I see is a merchant posting a vague "Shopify developer wanted" brief and getting a theme tweaker when they needed someone who could rebuild checkout logic. Define the role first. Everything else follows.

Step 2: The 2026 platform checkpoint questions

These are the questions that separate developers who are current on the platform from those who are not. Run them in three tiers: foundational fluency, current architecture, and how the developer works with your team. Each question has a strong answer to listen for and a red flag that should end the conversation.

Foundational fluency

Q: Walk me through the difference between a section and a block in Online Store 2.0.

Strong answer: sections are the top-level containers with their own schema, blocks are nested, repeatable child elements within a section. They name a real use case (like a testimonials section with quote blocks). Weak answer: confuses sections with templates or talks about the old sections/ folder without mentioning JSON templates.

Q: How do you approach performance on a product page with a heavy image above the fold?

Strong answer: they mention LCP as the Core Web Vital at stake, describe preloading the hero image, using correct width and height attributes to prevent CLS, and lazy-loading everything below the fold. They may reference Shopify's image CDN and image_tag Liquid filter. Weak answer: "I would compress the images."

2026 architecture (non-negotiable for any serious hire)

Q: A Plus merchant is still running custom discount logic in Shopify Scripts. What is your migration path?

Strong answer: Shopify Functions is the official replacement, offering better performance, reliability, and scalability. A senior developer will outline an audit of active Scripts, note that as of April 15, 2026, no merchant can edit, update, or publish new Scripts in the Script Editor, meaning every Script currently running in production is frozen code, and describe rebuilding discount logic as a Function in JavaScript or Rust inside a WebAssembly sandbox. Weak answer: "We can keep Scripts for now."

Q: What is Checkout Extensibility and why does it matter for non-Plus stores right now?

Strong answer: The August 26, 2026 deadline applies to all non-Plus plans including Basic, Shopify, and Advanced. Shopify will auto-upgrade stores that have not migrated and remove all legacy checkout customisations in the process. A sharp developer will also flag the analytics risk: what breaks is the analytics layer underneath the checkout, and that is where the commercial damage accumulates. Weak answer: confusion between the Scripts deadline and the checkout.liquid deadline (they are two separate deprecation tracks).

Q: A store you built scores 45 on mobile PageSpeed. Walk me through your diagnosis.

This tests real diagnostic thinking, not textbook knowledge. Strong answer: they start with Chrome DevTools or PageSpeed Insights to identify the specific failing Core Web Vital (LCP, CLS, or INP), then check render-blocking scripts, third-party app JavaScript, unoptimized images, and excessive Liquid loops. They will mention the Shopify theme inspector and waterfall analysis. Weak answer: "I would remove some apps."

Collaboration and process

Q: How do you handle deployments to a live Shopify store?

Strong answer: they describe a theme versioning workflow using GitHub, a staging environment (Shopify development themes or a separate store), and a release checklist. No Git or version control process means live store deployments without version control are an accident waiting to happen. Weak answer: edit the live theme directly.

Step 3: The paid test project

No interview question replaces a small, scoped piece of real work. Two to three days of real work reveal more than any interview round: code quality, communication style, deadline reliability, and how they handle ambiguity.

Good test project formats:

• Theme task: Add a sticky announcement bar with a dismissal cookie and a schema-configurable message. Scope: 3-4 hours. You are evaluating Liquid quality, schema structure, and whether they write clean, commented code.
• Performance task: Audit a provided theme and produce a written report with specific LCP and INP recommendations. Scope: 2-3 hours. You are evaluating analytical depth and whether they can communicate technical findings to a non-technical stakeholder.
• API task: Write a simple Shopify Admin GraphQL query that fetches the last 10 orders with line items and total price, then explain the pagination approach. Scope: 1-2 hours. You are evaluating GraphQL fluency and API thinking.

Pay fairly for the test (a day rate pro-rated to the scope). Developers who decline an unpaid test are signalling professional standards, not avoidance.

Step 4: Portfolio and certification validation

Portfolio review is not about aesthetics. You are checking for proof of the work, not the appearance of the result.

• Ask for a GitHub repository or theme export from a real project (with client permission).
• Look at commit history: are commits atomic and well-labelled, or one giant push with the message "updates"?
• Check the code for hardcoded values where schema settings belong, inline CSS where a stylesheet exists, or JavaScript that modifies the DOM on page load without deferral.

On certifications: Shopify Partner certifications signal that a developer has completed structured training and understands platform fundamentals. They are a useful baseline signal, particularly for junior developers, but should not replace portfolio review and technical assessment for senior hires. Treat a certification as a floor, not a ceiling.

Red flags that end the conversation

After running this process across 65+ projects, these are the patterns that predict a bad hire:

• No answer on Shopify Functions. Any developer billing themselves as Shopify-capable in 2026 should know that Scripts are gone. Blanks here mean they have not shipped anything that touched checkout logic recently.
• "I work directly on the live theme." No staging, no version control. One bad push costs more to fix than the developer saves in setup time.
• Rates that seem too low for the scope. Offshore developers in India and Eastern Europe typically cost 40-60% less than US-based rates with comparable technical quality, and that can be a smart structure. The red flag is rates that are implausibly low even for those markets, which usually signals either junior skill mis-sold as senior, or a developer juggling too many clients to give your project real attention.
• Vague portfolio. "I built lots of Shopify stores" with no links, no repositories, and no named metrics is not a portfolio. It is a claim.
• Can't explain a trade-off. Strong hires document trade-off notes on the calls they made, including the option they rejected and why. They have an opinion on what NOT to do with Shopify, backed by an example.

What the current platform demands in 2026

The skills baseline has shifted materially in the past two years. Shopify's 2024-2026 platform evolution has fundamentally changed what development means. The Unified Commerce Platform merges online, retail, B2B, and wholesale into a single backend. Agentic Commerce lets AI agents discover and purchase products through the Storefront API.

For any hire touching app or headless work: the 2026 Shopify ecosystem is React-first for everything outside the Liquid theme layer. A developer without React fluency is limited to pure theme work.

For API work, note that Shopify deprecates API versions after 12 months, and apps that hard-code a specific version and never update will break. Ask candidates directly how they handle API versioning. The answer tells you whether they build for longevity or for the sprint.

The skills you need for a competent Shopify theme developer are distinct from what you need for a Shopify Plus build. Conflating them is where projects stall.

The full validation checklist

Use this before you sign any contract:

1. Role type confirmed against project scope (theme, app, Plus, headless)
2. Checkout Extensibility and Shopify Functions fluency verified verbally
3. Core Web Vitals diagnostic approach tested with a real scenario
4. Git/version control process confirmed
5. Paid test project completed and reviewed
6. Portfolio code inspected (not just screenshots)
7. API versioning approach discussed
8. Communication quality assessed across async written exchanges during the process itself
9. References from at least one past client or agency
10. Rate validated against role type and market (not just cheapest available)

If you want to skip the process entirely and work with someone who has already been through it, see the case studies for examples of what a structured Shopify engagement looks like in practice.

If you are evaluating developer candidates for a specific project and want a second opinion on scope, skill fit, or what the build should actually cost, the details are on the hire page.