Hire a BigCommerce Developer: Pick the Stack First, Then the Person
Hiring a BigCommerce developer? Choose Stencil or Catalyst first, then vet API skills, ownership terms and scope so quotes are comparable.
Long Nguyen
Développeur fullstack · Ingénieur IA · Chercheur
The short answer: pick the stack first, then the person
Most people who search for a BigCommerce developer start by comparing hourly rates. That is the wrong first step. On BigCommerce, three different kinds of work all get called development: editing a Stencil theme, building a headless storefront with Catalyst, and integrating the store with other systems through the APIs. They need three different skill sets, and a great theme developer can be a poor integration engineer.
The order that avoids expensive mistakes is: decide which of the three you actually need, shortlist people who have shipped that exact kind of work, test them with a few platform-specific questions, and only then negotiate price and ownership terms. The rest of this guide follows that order.
What a BigCommerce developer actually does
BigCommerce is a SaaS platform, so nobody hosts or patches your store for you to touch. Developers work in three layers around it. Knowing which layer your project sits in tells you what to ask for.
| Type of work | Where the code lives | Core skills to look for | Typical projects |
|---|---|---|---|
| Theme customization | A Stencil theme, usually forked from the Cornerstone base theme | Handlebars templates, Sass/SCSS, JavaScript, Stencil CLI, Page Builder settings | Custom product page layouts, new templates, checkout-adjacent UX, speed and accessibility fixes |
| Headless storefront | A separate Next.js/React app, often built on Catalyst | React, Next.js, TypeScript, GraphQL, hosting and caching | Brand-led storefronts, multi-storefront setups, sites where marketing needs full design control |
| Integrations and data | A backend service or app talking to the REST and GraphQL APIs | REST v3, webhooks, queues, retry logic, data mapping, idempotent writes | ERP, PIM and inventory sync, marketplace and feed connections, catalog migration, order routing |
Most real projects mix two layers. A store redesign usually needs theme work plus a few API calls. A multichannel setup is mostly integration work with a small amount of theme change. When you brief a developer, name the dominant layer.
Stencil or Catalyst: this decides who you need to hire
Stencil is BigCommerce's default theme engine. It is built on Handlebars templates, supports Sass and SCSS, and is developed locally with Stencil CLI, which runs on Node.js. Merchants can then adjust theme settings visually through Page Builder. Catalyst is the other route: according to BigCommerce's Catalyst documentation, it is a headless storefront framework built with Next.js and React components, backed by the GraphQL Storefront API, with Tailwind CSS in its components. The same documentation describes a secure redirected checkout page that can be themed to match the storefront, so payment handling stays on BigCommerce's side.
The practical consequence is a hiring one:
| Question | If yes, lean toward | Developer profile |
|---|---|---|
| Do you need a solid store quickly, with your team editing content in Page Builder? | Stencil | Front-end developer with real Handlebars and Stencil CLI experience |
| Is the storefront a core brand asset with custom interactions and design that a theme fights against? | Catalyst or another headless build | React/Next.js engineer who has also worked with a commerce API |
| Is the real problem data moving between systems, not the look of the store? | Either, plus an integration layer | Backend engineer, ideally with ecommerce integration history |
| Will you have ongoing developer capacity after launch? | Headless is realistic only if yes | Retainer or in-house hire, not a one-off freelancer |
My own rule of thumb: headless is a cost you keep paying. You get design freedom, but you also own a separate application, its hosting, its deployments and its upgrades. If a strong Stencil theme can deliver the design you want, choosing headless anyway means paying for engineering you did not need. If the design genuinely cannot be built in a theme, do not let a Stencil-only developer talk you into forcing it.
Freelancer, agency or in-house developer?
There is no universally correct answer. The right model follows the shape of your work.
| Model | Best for | Main risk |
|---|---|---|
| Freelance BigCommerce developer | Well-defined tasks: a theme change, one integration, a migration script | Single point of failure; no one else knows your codebase when they are unavailable |
| Specialist agency | Redesigns, headless builds, projects needing design, development and QA together | Overhead and premium pricing; the person you meet in sales is not always the person who builds |
| Small dev studio | Mixed work: theme plus integrations plus something custom around the store | Capacity; confirm who exactly is assigned and what happens during their time off |
| In-house hire | Continuous roadmap, many small changes each week | Slow to hire, and a single hire rarely covers front-end, backend and DevOps equally |
If your store runs on BigCommerce and the work is platform or API related, Netalith's eCommerce platform development service covers BigCommerce alongside Shopify, WooCommerce and other platforms, and takes projects of any size, from a single integration to a full build. Whoever you choose, the vetting steps below apply equally.
Which skills to verify, by project type
A résumé that says BigCommerce tells you very little. Match the evidence to the layer of work.
- Stencil work: ask for a live store where they customized a theme beyond colors and fonts, and ask what they changed in the templates rather than in the settings. Look for comfort with Cornerstone's folder structure and the theme's config.json.
- Headless work: ask what they built on the GraphQL Storefront API and how they handled caching, cart state and the handoff to checkout. Someone who has only built brochure sites in Next.js will struggle here.
- Integration work: ask about the last system they connected to a store, how they handled failed writes, and how they avoided duplicate orders or double inventory updates. Reliability thinking matters more than syntax.
- Certification: BigCommerce publishes developer learning plans, including a Developer Foundations certification. It is a useful signal that someone studied the platform, but treat it as a floor. It does not prove they have shipped and maintained a production store.
How to vet a BigCommerce developer in 30 minutes
You do not need to be technical to run this. Ask the questions, then judge how specific the answers are. Vague, confident answers are the warning sign.
| Ask this | A good answer sounds like | A red flag sounds like |
|---|---|---|
| Stencil or Catalyst for my store, and why? | Asks about catalog size, editors, budget for ongoing development, then explains the trade-off | Recommends the same option to everyone |
| What happens when the API returns a 429? | Reads the rate-limit headers, waits for the reset window, queues and spreads requests, and prefers webhooks over polling | Retries immediately in a loop, or has never seen a 429 |
| How do you stop a theme push from overwriting what my team changed in Page Builder? | Syncs the live theme configuration down first, works in version control, and never edits the live theme directly | Edits the live theme in place, or does not know the question matters |
| What can and cannot be customized in checkout? | Explains that checkout is a separate application with limits, and names what they have actually changed there | Promises anything is possible without asking what you need |
| Show me a live store you worked on and tell me exactly what you owned. | Gives a URL, a role, and one problem that went wrong and how it was fixed | Only screenshots, or a portfolio of work by a whole agency |
The 429 question is the sharpest one for integration work. BigCommerce's API rate limit documentation explains that responses carry headers showing the size of the window, the quota, the requests left and the time until reset, and that going over the quota returns a 429 until the window refreshes. The same page notes that an Unlimited plan exists for some Enterprise clients. A developer who builds sync jobs without reading those headers will eventually stall your inventory or order flow at the worst possible moment, usually during a sale.
The theme question matters because Page Builder changes live in the store's theme configuration. Stencil CLI includes a pull command specifically to sync those live settings back into the local config.json, so a later upload does not silently discard your team's edits. It is a small habit that separates people who have maintained a store from people who have only built one.
What drives the cost of hiring a BigCommerce developer
Quotes vary widely because scope varies widely, not because some developers are simply cheaper. Hourly rates differ by region and seniority, but the number of hours moves the total more than the rate does. Rather than quote figures that will be outdated within a quarter, here is what actually moves a price:
| Cost driver | Why it matters |
|---|---|
| Stencil vs headless | Headless adds a separate app, hosting, deployment and maintenance on top of the design work |
| Number of integrations | Each external system brings its own data model, edge cases and failure modes |
| Catalog size and data quality | Messy product data turns a migration or feed project into a cleaning project |
| Custom checkout or B2B rules | Anything outside the default flow needs careful design and testing |
| Design ownership | Whether you supply finished designs or expect the developer to design too |
| Ongoing support | A launch is the start of maintenance, not the end of the project |
To get quotes you can compare, send every candidate the same written brief. Two quotes based on two different mental pictures of the project are not comparable, however similar the totals look.
Contract and handover terms to insist on
Most painful BigCommerce hiring stories are about ownership, not code quality. Put these in writing before work starts:
- You own the store and its accounts. The developer works through collaborator access or API accounts you created and can revoke. Never hand over the owner login.
- You own the code. Theme and app code sits in a repository under your organization, or is delivered to you at defined milestones, with the right to modify it.
- Work happens off the live theme. Changes are built and previewed before they replace what customers see.
- Integration credentials and secrets are documented and rotatable, with a list of every scope the developer requested and why.
- Handover documentation is a deliverable: how to deploy, what each integration does, and what to check when it fails.
- A defined fix period after launch, so bugs found in the first weeks are corrected under the original agreement.
What to put in your project brief
A one-page brief filters out unserious candidates and makes quotes comparable. Include:
- Your current store setup: plan, theme or storefront, and the apps and integrations already running.
- The outcome you want, stated as a business result such as fewer checkout drop-offs or accurate stock across channels, not as a feature list.
- The layer of work: theme, headless, integration, migration, or a mix, with the dominant one named.
- Systems to connect and where their data lives (ERP, warehouse, marketplace, feed, CRM), with API documentation if available.
- Constraints: deadline, launch events such as a sale, and any compliance or regional requirements.
- Who approves work on your side, and how quickly they can respond. Slow feedback is a bigger schedule risk than slow development.
If you would rather have an experienced developer read the brief and tell you which layer you actually need, request a free quote from Netalith. There is no cost or account required, and the reply will say whether the work is a theme job, an integration job or something bigger, so you can decide with the facts in hand.
FAQ
Questions fréquentes
How do I hire a BigCommerce developer?
Decide first whether your project is theme work (Stencil), a headless storefront (for example Catalyst) or an integration with other systems. Shortlist developers who have shipped that exact kind of work, ask for a live store and their specific role in it, test them with platform-specific questions such as how they handle API rate limits, and agree in writing that you own the store accounts and the code.
What is the difference between a Stencil developer and a Catalyst developer?
A Stencil developer customizes BigCommerce's default theme engine, working with Handlebars templates, Sass and Stencil CLI. A Catalyst developer builds a separate headless storefront with Next.js and React on top of the GraphQL Storefront API. The skills overlap only in general front-end knowledge, so a strong Stencil developer is not automatically a good headless engineer, and the reverse is also true.
Should I hire a freelancer or an agency for BigCommerce?
A freelancer suits well-defined tasks such as a theme change, one integration or a migration script. An agency or small studio suits redesigns, headless builds and projects that need design, development and testing together. Choose based on how many people need to understand your codebase and how much ongoing work you expect after launch.
How much does it cost to hire a BigCommerce developer?
It depends on scope more than on the hourly rate. The biggest drivers are whether you go Stencil or headless, how many systems must be integrated, the size and quality of your catalog data, custom checkout or B2B rules, who owns the design, and how much support you need after launch. Send every candidate the same written brief so the quotes are comparable.
Does a BigCommerce certification mean a developer is good?
It is a useful signal that the developer studied the platform. BigCommerce publishes developer learning plans that include a Developer Foundations certification. It does not prove they have shipped and maintained a production store, so still ask for a live example and what they personally owned.
What should be in a contract with a BigCommerce developer?
At minimum: you own the store and its accounts, you own the theme and app code and receive it in a repository you control, work is built and previewed off the live theme, integration credentials are documented and rotatable, handover documentation is delivered, and there is a defined fix period after launch.