Online Store 2.0 themes
Builds JSON templates, sections and blocks with sensible schema settings, so merchandisers can rearrange pages in the theme editor without filing a ticket.
Hire · Commerce platforms
Senior Shopify developers who work alongside your ecommerce and marketing teams on themes, custom apps and integrations. Before an introduction, each has rebuilt a section in Liquid, written a discount Function and shipped a checkout UI extension during a paid technical trial.
Tested on themes, apps and checkout extensibility
Experienced engineers only, no trainees
Works in your Partner account and repos
On your team
Builds JSON templates, sections and blocks with sensible schema settings, so merchandisers can rearrange pages in the theme editor without filing a ticket.
Moves legacy checkout.liquid edits to checkout UI extensions and branding settings, keeping upsells and custom fields within what Shopify supports.
Replaces old Scripts with Shopify Functions for discounts, delivery customisation and payment method rules, written in Rust or JavaScript and tested locally.
Connects ERP, warehouse and review platforms through the GraphQL Admin API, webhooks and bulk operations, respecting rate limits and API versioning.
Keeps Liquid render time low, trims app embeds and third-party scripts, and watches Core Web Vitals reported for real shoppers.
Shopify hiring goes wrong when a theme specialist is expected to build apps, or the other way round. Theme work is Liquid, sections, metafields and front-end performance. App work is OAuth, the GraphQL Admin API, webhooks, Functions and extensions. Decide which half carries most of your roadmap, then interview for it directly.
A useful screening question is how the candidate would replace a Shopify Script. People with current experience will talk about Functions, input queries and testing them before deploy, rather than editing a script in the admin.
Vetting
Section rendering, metafield and metaobject access, predictive search and translation keys, with no logic duplicated across templates.
Scaffolds apps with the Remix-based template, manages app extensions in one repository and handles OAuth and session tokens correctly.
Writes efficient queries within cost limits, uses bulk operations for large exports and pins an API version with a plan for each quarterly release.
Understands input queries, the instruction budget and how Functions interact when several discount apps are installed.
Builds on Hydrogen and Oxygen or another framework with the Storefront API, and can say honestly when headless is not worth the upkeep.
Knows the App Store requirements for billing, GDPR webhooks, scopes and embedded app behaviour, so submissions are not bounced.
Work sample
The candidate turns a static landing template into an Online Store 2.0 section with blocks and settings a merchandiser can edit.
They implement a tiered discount as a Shopify Function with tests for edge cases such as mixed carts and gift cards. This is a paid task with a fixed time limit.
On a development store they add a delivery note field through checkout extensibility and save it to an order metafield.
They explain to a store manager what scopes an app requests and why, in plain language.
Levels
Ships theme sections, Functions and integrations within your store setup, and reviews other developers’ pull requests and app extensions.
Sets the theme workflow, app approval rules, API version upgrades and the boundary between Shopify and back-office systems.
Decides whether Hydrogen or a custom storefront is justified, owns the Storefront API contract and plans multi-market and Shopify Plus expansion.
Other options
If you need complex B2B pricing, many store views or full control of hosting, a Magento developer is the closer match.
Open registerWhen most of the work is a bespoke Next.js front end, with Shopify only as a back end, hire a Next.js developer.
Open registerIf editorial content leads and the shop is secondary, a WordPress developer may serve you better.
Open registerShopify releases a new API version every quarter and retires old ones on a published timetable. A strong developer pins versions, reads the changelog, runs integrations against the next version on a development store and upgrades before warnings turn into failures.
Hydrogen gives full control over the storefront, but it also means owning hosting, caching, previews and every feature the theme editor gave you free. Hire a headless lead only when there is a clear reason, such as content from several systems or interactions a theme cannot support. Otherwise a senior theme developer will move faster.
Give your new developer collaborator access to the store and a development store seeded with real products. Keep the live theme connected to GitHub so every change is reviewed and can be rolled back.
Ask for an inventory of installed apps and the scripts each one injects. Removing apps that nobody uses is often the quickest speed improvement a store sees.
FAQ
Yes. They audit what the old checkout does, map each change to checkout UI extensions, Functions or branding settings, and flag anything Shopify no longer allows so you can decide early.
Both. For a public listing they work to the App Store requirements from the start, including billing API use, mandatory privacy webhooks and performance checks on the storefront.
Only if you are on Plus or heading there. We say during shortlisting which candidates have worked with Plus-only features such as expansion stores, B2B on Shopify and Launchpad.
Works alongside
To design collection, product and cart patterns that the theme editor can then reproduce without custom code.
Open registerFor middleware that syncs Shopify orders with fulfilment, accounting or a loyalty platform.
Open registerTo turn order and session data into merchandising and retention decisions.
Open registerProduct delivery
Primary sources
Dated official documentation, standards, and research that support the factual claims on this page.
How Functions customise discounts, delivery and payments.
Sections, blocks and JSON templates in Online Store 2.0.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.