Senior Shopify Developer

Experience:

7–14 years minimum (lead / architect level) Notice period:
Immediate to 15 days Location / work model:
Remote Compensation:
Open to Discuss

We're hiring an architect who has actually shipped headless Shopify — not someone who has read about it. You'll own storefront architecture end to end, across Hydrogen, Liquid themes and custom apps, and you'll be the person clients talk to when the hard technical questions come up.

All five are required. The first three are hard gates with no exceptions.

Production Hydrogen storefronts, not tutorials or proofs of concept. You have built on Hydrogen, queried the Storefront API for customer-facing data, and shipped it live — on Oxygen, or self-hosted on Vercel or Cloudflare Workers as a deliberate choice you can justify. We will ask: which store, and where it was deployed.

Current, hands-on React at depth — component architecture, hooks, state management, data-loading patterns and performance work you personally owned. Type Script expected. Hydrogen runs on Remix, so Remix routing and loaders are a strong plus. We will ask: a performance or rendering problem you diagnosed and fixed yourself.

Deep Liquid on the current theme architecture: sections, blocks, JSON templates, metafields and metaobjects. Hands-on building on Dawn or Horizon as a base, with merchant-configurable components a non-technical team can actually use. We will ask: how you'd add a filterable custom badge to a collection page.

Custom or public apps built on the Admin GraphQL API . Embedded app patterns with App Bridge and Polaris, OAuth or managed install, webhooks verified by HMAC and handled idem potently, and cost-based rate limiting — including bulk operations for large data jobs. We will ask: how the Admin GraphQL API limits requests, and what you do when you hit the limit.

A headless CMS integrated into a live commerce front end — Contentful, Sanity, Contentstack, Strapi or equivalent. Content modelling and schema design, plus an editorial workflow the content team can run without a developer. We will ask: how you modelled the content, and where you drew the line between CMS data and Shopify data.

Architecture for headless Shopify storefronts, from discovery through launch and into production support.

The honest call on whether a project should go headless at all — and the case for a well-built Online Store 2.0 theme when that's the better answer.

Custom and public apps on the Admin GraphQL API, including data-sync jobs that move catalogues, orders and inventory at volume.

Metafield and meta object data models that hold up as catalogues grow past tens of thousands of SKUs.

Integrations with ERP, OMS, PIM and payment systems, and the reliability of those syncs — retries, idempotency, reconciliation.

Core Web Vitals and storefront performance, measured before and after.

Technical discovery with clients: requirements, solution proposals, estimates, and presenting the architecture to their stakeholders.

Engineering standards across the team — code review, branching strategy, mentoring mid-level developers.

Shopify moves quickly and a lot of experience goes stale. Three things we listen for:

Checkout customisation today means checkout extensibility — UI extensions, Functions and Web Pixels. checkout.liquid has been deprecated.

They are custom apps , not "private apps". That terminology was retired when Shopify replaced legacy private apps.

Admin GraphQL rate limiting is cost-based , not a request-per-second cap. Adding a sleep between calls is a workaround, not an understanding.

Pa…