Hiring a Shopify Plus Developer in 2026: What to Actually Look For

We have audited more than forty Shopify Plus stores over the last two years. Roughly 70% of the broken builds we inherit come from the same hiring mistake: the merchant hired a generalist Shopify developer to do Plus work, and the work shipped but did not hold up under real Plus load.

A generalist can build a Dawn-based theme, install a stack of paid apps, wire up Klaviyo, and run a competent $1M store. That same developer dropped into a $20M Plus environment with B2B catalogs, customer-tag pricing, Scripts-to-Functions pressure, Checkout Extensibility apps, and multi-region tax will, on average, ship something that mostly works at launch and quietly accumulates bugs for the next twelve months.

These are the non-negotiable technical competencies. A developer missing two of them can still ship competent Plus work with mentorship; a developer missing four of them is a generalist with a Plus headline. Test for each one specifically.

Functions are not optional in 2026. With Scripts deprecating on June 30, every Plus store running custom discount, shipping, or payment logic now runs it through Functions, deployed via the Shopify CLI as part of a custom app. A Plus developer who has never shipped a Function to production has not done Plus work in the last eighteen months.

Most Functions in the wild are written in JavaScript (compiled to WebAssembly) rather than Rust. JavaScript is fine for the typical discount or delivery-customization use case. Rust matters when you hit the CPU-budget ceiling, which happens on larger carts with complex iteration. A developer who can write both, and who knows when to reach for which, is the senior tier.

Verify: can they walk you through a Function they have shipped, including the GraphQL input contract, the deployment pipeline, the test harness, and how they handled the CPU-limit error class? If the answer is theoretical, they have not shipped one.

The checkout.liquid era is over. Custom checkout work in 2026 lives in Checkout UI extensions, written in React, deployed as part of a Shopify app. A developer fluent in Dawn and Liquid can still be lost in the Checkout Extensibility component model, which has its own constraints (limited DOM access, server-rendered components, strict performance budgets).

Real signals: has the developer shipped a custom checkout banner, a custom field with server-side validation, or a third-party API integration through Checkout Extensibility? Can they explain the difference between a Function extension and a UI extension and when each is the right surface?

Plus stores rarely have just one price. They have customer-tag-based pricing, B2B catalogs with separate price lists per company, draft-order workflows for negotiated quotes, net-30 terms, and PO-number capture at checkout. The Plus B2B product has its own data model: companies, locations, catalogs, contacts.

A developer who has only built D2C Shopify will struggle here. The mental model is different: the customer is no longer a single user, it is a contact at a company at a location with a catalog. Pricing, tax, and shipping logic all branch on company context. This is where most of the silent revenue leaks we audit actually live.

In 2020, a Shopify developer could ship most work through theme code, app installs, and Liquid snippets. In 2026, anything custom (Functions, Checkout extensions, admin UI extensions, workflow automations) lives in a custom app, scaffolded with the Shopify CLI, deployed via App Bridge, often hosted on Shopify-managed infrastructure or a Node host the developer maintains. This requires real backend competence: Node or Ruby, OAuth flows, webhook handling, admin GraphQL.

The litmus test: “Walk me through the last custom app you scaffolded with shopify app init. What was in it, where does it run, how do you deploy updates?” A generalist freezes. A real Plus developer has a clear answer and probably a GitHub repo to show.

Shopify imposes hard limits on Functions (a fraction of a millisecond of CPU per invocation, kilobytes of memory) and on Checkout extensions (strict render-time budgets). Code that runs fine in a test cart fails silently on a 200-line wholesale order. Plus developers know these limits, design around them, and write tests that catch them before production.

Most founders start the search in the wrong place. Here is the honest map.

Upwork, Fiverr, and the open marketplaces. Signal-to-noise is brutal. Real Plus developers occasionally show up, but the median profile claiming “Shopify Plus expert” is a generalist who has touched a Plus admin once. If you go this route, screen aggressively on the five competencies before any scope conversation.

Toptal and curated marketplaces. Better screening, higher prices, still hit-and-miss on Plus specifically. The screening is generic-developer screening, not Plus-specific. A Toptal developer can be a strong backend engineer who has built one Shopify store and is now branded as a Shopify expert. Useful for short-term capacity if you run your own technical interview on top.

Shopify Partners directory. The official listing, weighted toward agencies. Filter for “Plus Partner” status. Plus Partners have shipped Plus work and Shopify has vouched for them at some level. Most are agencies with bench rates of $150 to $300 per hour, not individuals. Good for finding agency partners, less useful for finding a hire.

Shopify Unite and Editions community. Developers who present at Unite, contribute to the official examples repo, write in the Shopify dev blog, or answer questions in the Shopify Community Forums are usually doing real Plus work. Slower than posting a job, much higher conversion.

LinkedIn search on specific skills. Search for “Shopify Functions” or “Checkout Extensibility” rather than “Shopify Plus.” These are recent enough as keywords that only people who have shipped that work bother to list them.

Referrals from other Plus merchants. The highest-quality channel by a wide margin. Plus merchants talk. Ask your Plus account manager for two introductions; they will not formally recommend, but they know who the strong builders are.

Founders are bad at interviewing Shopify developers because the conventional questions (“what’s your experience with Shopify?”) are too broad. Plus interviews need to be specific. Here is the signal grid we use, refined across dozens of hiring rounds.

There is no universally right answer. There is a right answer for your store, your stage, your roadmap, and your tolerance for the wrong kind of risk. Here is the framework we walk merchants through.

These are the rates we see in real contracts across the last twelve months. Take them as market signal, not as quotes; rates compress in a soft market and expand when Shopify pushes a deadline that creates demand spikes.

North America (US and Canada). $120 to $200 per hour for contract. $130,000 to $200,000 base salary for full-time, plus equity at smaller merchants. The tight band is $140 to $160 per hour for someone with three-plus years of Plus-specific experience including Functions and Checkout Extensibility shipped to production.

Western and Northern Europe. EUR 90 to EUR 150 per hour for contract. Germany and the Nordics are in the EUR 80K to EUR 120K salary range; the UK runs slightly higher in pounds.

Eastern Europe. EUR 50 to EUR 90 per hour. The best price-to-quality ratio currently sits here if you can manage the time zone. Several Plus developers we contract with are based in Poland, Ukraine, Bulgaria, and the Baltics. Vetting matters; skill dispersion is wider than in North America.

South and Southeast Asia. $30 to $70 per hour for senior contract work, with a wider range than any other region because the market is less mature. The best developers here ship at North American senior quality; the median profile claiming Plus expertise is closer to the generalist tier. The premium for verified Plus depth is substantial.

Specialist Plus agency engagements. $150 to $300 per hour blended rate. Fixed-price engagements (audit, migration, replatform) are typically in the $25K to $150K band. Our Shopify Teardown is a 30-day fixed-price engagement at the lower end of this range.

These are the patterns that show up after the contract is signed and the work is in production. Every one of them is preventable with the right interview process.

Theme dev pretending to be Plus. The portfolio is Liquid, Dawn customizations, section settings. No custom app, no Function, no Checkout extension. They talk about Plus in the abstract because they have only ever worked on Plus stores in the capacity of theme work.

The all-app-installer. Every problem gets solved with a paid third-party app. The store ends up with $4,000 per month in subscriptions, none of them cleanly integrated, and the developer cannot explain what custom code would do better. A tax on a Plus store that accumulates technical debt every quarter.

The “I’ll learn it as we go” developer. Strong general developer, no Plus experience, says they will pick it up. They will, eventually. The cost of that learning curve, paid at the contract rate on a production Plus store, is the most expensive education in ecommerce.

The agency with no named developer. You meet the account lead, the strategist, the project manager. You never speak to the developer who will write the code. After signing, the work goes to a junior, the senior reviews on Fridays, and architecture decisions are made by people you have never met.

The “we just need to refactor” closer. Every audit conversation pivots to “the previous developer built it wrong, we need to start over.” Sometimes true. Often a developer’s way of avoiding hard work on someone else’s code. Insist on a written scope of what stays and what changes, with a specific reason for each rewrite.

What to do this week

Three concrete actions. None of them require a contract.

1. Audit your current stack against the five competencies. Whether you have a current developer or are about to hire one, write down which of the five (Functions, Checkout Extensibility, B2B, custom apps, performance limits) is covered today and which is a gap. Most Plus stores are missing at least two.
2. Draft a paid trial task. A 4-to-6-hour scoped piece of real work (ship a small Discount Function, add a Checkout UI banner with validation, document the deploy). This is the single highest-signal screen you can run. Pay for it in advance; the candidates worth hiring expect to be paid for trial work.
3. Get a second opinion on the scope before you sign. Whether it is an audit from us, a peer Plus merchant, or a trusted Plus Partner, do not sign a contract over $25K without a second technical read on the scope. The cost is low and the avoided rebuilds are large.

If you would rather have the audit done for you, the Shopify Teardown is a 30-day fixed-price engagement that surfaces exactly this: where your stack is over-engineered, where it is under-built, and what the right hiring model is for the next twelve months. The deliverable is a prioritized backlog, an effort estimate, and a recommendation on in-house vs contractor vs agency for your specific roadmap. With a $75,000-per-year recoverable-revenue guarantee or full refund.

Probably not. The Plus-specific surfaces are mostly Plus-exclusive. A generalist Shopify developer is usually the right hire on standard Shopify. The exception is if you are planning to migrate to Plus in the next twelve months; in that case start the technical relationship with a Plus-capable developer now.

For a single-Script migration with no Checkout Extensibility coupling, a strong contractor is faster and cheaper. For a multi-Script migration plus B2B history coupling plus a legacy checkout.liquid layer, an agency engagement amortizes the architecture cost better. Under five Scripts and no Checkout Extensibility work, hire a contractor; above that, run an audit first. Background in our Scripts deprecation playbook.

It is a floor, not a ceiling. Plus Partner status confirms the agency has shipped Plus work. It does not differentiate senior depth from junior staffing. Use it as a filter, then run technical interviews regardless.

For a full-time hire, 8 to 14 weeks from job description to start date if you screen properly. For a contractor, 2 to 4 weeks including the paid trial task. Compressing this is almost always expensive.

Two honest options. Either scope smaller (fewer Functions, defer Checkout Extensibility work, run native Shopify rules where possible) and hire at the contract rate that fits, or buy a fixed-price agency engagement that converts the rate question into a scope question. The third option, hiring a generalist at $40 per hour and hoping they stretch into Plus work, is the one we keep being called to clean up.

Senior Plus developers exist who cover all five at working depth. They are uncommon and expensive. A more realistic model is one senior who covers four strongly plus a specialist (often Rust-and-performance) brought in for the gap. Agencies bundle this; an in-house team would hire two people.

The Shopify Partner Academy certifications are real but generalist. They do not specifically certify on Functions or Checkout Extensibility depth. Treat them as a signal of seriousness, not as a substitute for technical interview.

Pay market rate, give them interesting work, do not bury them in app-installation tickets. A developer shipping Function and Checkout Extensibility work at a $5M store gets recruited by $30M stores quarterly. The retention lever is the scope of the work as much as the salary.