The ecommerce jobs you didn't know were jobs

Picture a job in ecommerce and you probably picture someone running a store, listing products and processing orders. Go one step further and you picture the developer who built the site. Those are the obvious answers, and they are real enough. Underneath them runs a whole layer of specialist work that keeps online stores alive, and it looks nothing like either picture. We went through a quarter of our own listings to see which of those roles come through, and the odd corners of the board turned out to be the best part.

If the store owner and the developer are the whole picture for you, here is some of what you are missing: solutions engineers who prove a platform works before a sale closes, implementation specialists who move a merchant from one platform to another without breaking checkout, customer success engineers who keep big merchants live, product-data people who keep catalogs sane across channels, and the occasional developer advocate paid to teach other developers. None of them reads as a classic ecommerce job, and all of them are ecommerce jobs.

First, the numbers. Of the 241 listings we first indexed in the third quarter of 2026, just under half were some version of developer. Fewer than one in ten were the non-developer technical roles below. More than a quarter fit no clean category at all, a group full of ecommerce managers, technical project managers, architects, and business analysts. Once you stop counting only the developers, these overlooked roles are most of the board.

A quick caution before the tour. This is what crosses one curated, Shopify-heavy board. It is not a survey of the whole field, and seeing a role rarely here can say as much about how we source listings as about how common it is. Treat the counts as rough texture. The sample is too small and too particular to be a census.

The solutions engineer

A solutions engineer is the technical half of a sales team, the person who proves a platform will do what a buyer needs before the contract is signed. On the board the titles read "Sales Engineer," "Solution Architect," and "Commerce Integrations Lead / Sales Engineer," six in all last quarter. It rewards developers who can explain a system to a nervous buyer and stand up a proof of concept on demand. Past work that helps: a demo or integration you built to win someone over, and any time spent sitting with customers. These jobs are posted by platforms and vendors, almost never by stores, so you will not find them in store listings.

The implementation or migration specialist

An implementation specialist gets a merchant live, or moves one off an aging platform without losing a sale on the way. One listing we carried was for exactly that, a Shopify data-integration and migration expert. Much of the Magento-to-Shopify work sits here. If you have ever run a replatform or untangled a data migration, that is the exact proof these roles want, more than any framework on your resume. They show up at agencies and on the platforms' own professional-services teams.

The customer success engineer

A customer success engineer is the technical person a large merchant calls first when something breaks, half support and half engineering. We saw one on the board, "Customer Success Engineer, Enterprise Engineering," and it is a well-established role at most enterprise platforms. The work is mostly diagnosing why a merchant's integration broke and shepherding the fix through to done. The transfer is clean for a developer who is good with people: you already debug under pressure, and here you also keep an account calm while you do it. The proof that lands is a story about a production incident you owned end to end. Watch the careers pages of the platforms and the larger vendors.

The product-data or PIM engineer

A product-data engineer keeps the catalog correct everywhere it appears, across every channel a merchant sells on. Our one example, "Akeneo PIM | PHP Engineer," is honestly half developer, which is the point: the role lives in the seam between code and merchandising. It is a real specialization well beyond this board, with its own tools like Akeneo and inRiver. If you have wrangled product feeds or cleaned up a messy catalog, you are already most of the way in, and naming the PIM tools you know is the proof that gets you read. The jobs sit at larger merchants and at the PIM vendors themselves.

The developer advocate

A developer advocate is paid to teach and win over other developers for a platform, through writing and public talks. We saw a single one all quarter, "Developer Relations Engineer: Magento 2 or Shopware 6," though it is a common role across the larger platforms. In practice it means building the sample apps and docs other developers copy from, and fielding the hard questions in the platform's forums. For an engineer who likes writing and speaking as much as shipping, few jobs reward it like this one. The signal that moves a hiring manager is one published technical walkthrough other developers actually use, or a conference talk whose recording still gets shared. It lives at the platforms, so watch their careers pages.

The technical product manager for commerce

A technical product manager owns what gets built and why, for a platform or a large merchant's stack. The board carried "Senior Product Manager - Managed Magento" and "Product Manager, Commerce Platforms & Integration." The transfer signal that works is concrete: a call you owned on what to build next, and how it changed what the team shipped. A developer who can point to one of those, with the outcome attached, reads as a product manager already. These roles post at platforms and at merchants big enough to run their own roadmap.

A pile of roles with no tidy name

The real surprise was the group our rules could not sort at all, more than a quarter of the board. Ecommerce managers and directors, technical project managers, architects and tech leads, business analysts. Many are clearly technical, or spend their days leading technical people, and none fit a one-word box. If you are hunting for a role and searching only "developer," this whole layer is invisible to you.

Why they stay hidden

A few things keep this layer out of view. People search by platform, so "developer" and "Shopify developer" go into the box and the roles named for a function never surface. The jobs themselves sit at the platforms and vendors, whose docs and tutorials speak to store builders and skip past the roles that surround them. And the usual advice on breaking into ecommerce names the same handful of titles, so everyone crowds the same doors.

Why it is worth knowing

Here is what to do with it, for each side of the board. If you build stores and the developer market feels crowded, search the titles above as well as "developer" and "Shopify developer." Bring one piece of specific proof for the role you want, the migration you ran or the demo that closed a deal, and let it do more work than your job title. They are hard to get, and far fewer people compete for them. And if you are hiring, the person you need may be searching for a title you never thought to post.

Before you follow the crowd, it is worth a look at the rest. Next time you search, try the titles above before you add another developer listing to the pile.

Method: counts come from our own listings database, covering the 241 roles first indexed between July and September 2026, classified by title, expired listings included. The categories are approximate, and the sample is small and young and skews to Shopify, so read it as what crosses our board, which is not the same as a map of the market.