How to Hire for Retail Technology Roles
Retail technology used to mean one IT generalist keeping the website online. In 2026 it means a stack of specialized platforms, and most companies are still hiring for the org chart they had three years ago.
Retail technology used to mean one IT generalist keeping the website online. In 2026 it means a stack of specialized platforms, and most companies are still hiring for the org chart they had three years ago.
Ten years ago, "retail technology" was one job description covering a website, a POS system, and whatever inventory spreadsheet held the business together. That job does not exist anymore, or rather, it has split into six or seven jobs. The ecommerce platform, order management, product data, point of sale, and customer data now each run on their own dedicated software, often from different vendors, and each one increasingly needs someone who actually understands it rather than a generalist stretched across all of them.
That fragmentation is exactly why retail technology hiring feels harder than it used to. Hiring managers are not just competing for engineers, they are competing for engineers who understand commerce, and the pool of people who check both boxes is smaller than the pool for either skill alone.
Retail technology has moved decisively toward what the industry calls composable or MACH architecture, meaning microservices, API-first, cloud-native, and headless. Instead of one monolithic platform trying to do everything, retailers now assemble a stack from best-in-class tools for each function and connect them with APIs. That shift gives retailers more flexibility, but it also means a single all-purpose IT hire can no longer credibly own the whole thing. Someone has to own the order management layer specifically. Someone has to own product data specifically. The generalist role has not disappeared, but it has moved up a level to oversee specialists rather than do the specialized work directly.
Before writing a job description, it helps to know which layer of the stack you are actually hiring for, since the skill sets and the software each role touches are genuinely different.
| Stack Layer | Who Typically Owns It | Popular Software |
|---|---|---|
| eCommerce Platform | VP / Director of Digital Technology | Shopify Plus, Salesforce Commerce Cloud, BigCommerce, commercetools, VTEX |
| Order Management (OMS) | eCommerce IT Manager | Manhattan Active OMS, Fluent Commerce, IBM Sterling OMS |
| Product Information (PIM) | eCommerce IT Manager | Akeneo, Salsify, inRiver |
| Point of Sale (POS) | Retail Systems / IT Manager | Lightspeed, Square, Oracle Retail Xstore, NCR Voyix |
| CRM / Customer Data | Digital Technology Manager | Salesforce, Klaviyo, Bloomreach Engagement, Segment |
| Search, Merchandising & CMS | Developer | Algolia, Constructor, Contentful, Contentstack |
A few of these layers overlap with practice areas we place for separately. Warehouse management and fulfillment technology sit closer to Supply Chain & Operations, and marketplace or retail media tooling sits closer to Marketplace Management. The layers above are the ones that live squarely inside a Retail & Digital Technology hire.
Across the retailers we work with, this practice area tends to break into three tiers rather than a flat list of titles.
VP / Director of Retail, Digital, or Omnichannel Technology. This person owns the overall architecture and the vendor relationships, decides what stays in-house versus what gets bought, and is accountable for uptime and roadmap across every layer above. They rarely write code day to day, but they need to know enough about each platform to evaluate whether a proposed integration will actually hold up.
eCommerce IT Manager. This is the role most directly responsible for the platforms themselves, administering the OMS, PIM, and CRM, managing integrations between them, and troubleshooting when a sync breaks between the storefront and the warehouse. It is the hardest of the three tiers to fill well, since it needs both technical depth and enough commerce fluency to know why a broken integration matters to the business, not just to the system.
Developer. Frontend, backend, or full-stack, building and maintaining the custom logic that connects platforms the out-of-the-box integrations do not cover. Increasingly this means API work and headless frontend development rather than theming a single monolithic platform.
The fastest way to misfire on a retail technology hire is writing a job description for the stack you had two years ago. Audit what is actually running today, then hire for that, not for the platform list on last year's org chart.
Platform certifications and years of tenure are the easiest things to screen for, and also the least predictive. The stronger signal is integration experience: has this candidate actually connected two or more of these systems to each other, and can they explain what broke and why when they did. As retailers keep moving toward composable, API-first stacks, that kind of cross-system thinking matters more than depth on any single platform, because the platforms themselves are designed to be swapped in and out.
It also helps to weight commerce fluency alongside technical skill. A strong engineer who has only worked in fintech or SaaS can learn Shopify's admin in a week, but understanding why a return needs to update inventory, the OMS, and the CRM all at once, in that order, takes longer to pick up and is harder to teach on the job.
If your last retail technology hire is now covering three platforms that did not exist when they were hired, that is usually the clearest sign the role needs to split rather than stretch further. Map which layer of the stack is actually under-resourced, whether that is architecture and vendor strategy, platform administration, or integration development, and build the search around that layer specifically rather than a generic "IT Manager" posting.
We place across all three tiers of the Retail & Digital Technology practice, from VP-level architecture hires down to the developers who keep the integrations running.
Retail and digital technology hiring typically spans three tiers: a VP or Director of Retail, Digital, or Omnichannel Technology who owns the overall stack and vendor strategy, an eCommerce IT Manager who owns platform administration and cross-system integration day to day, and Developers who build and maintain the custom logic connecting the commerce platform, OMS, PIM, POS, and CRM together.
The core categories are the ecommerce platform (Shopify Plus, Salesforce Commerce Cloud, BigCommerce, commercetools, VTEX), order management systems (Manhattan Active OMS, Fluent Commerce, IBM Sterling), product information management (Akeneo, Salsify, inRiver), point of sale (Lightspeed, Square, Oracle Retail Xstore, NCR Voyix), customer data platforms and CRM (Salesforce, Klaviyo, Bloomreach Engagement, Segment), and headless CMS or search tools (Contentful, Algolia, Constructor). Most candidates are deep in two or three of these categories, not all of them.
IDC has projected that the global IT talent shortage will cost organizations worldwide 5.5 trillion dollars in 2026, and ManpowerGroup's 2026 Talent Shortage Survey found that 72 percent of employers globally are struggling to fill open roles, with technology named as one of the four industries under the most acute pressure. Retail technology roles sit at the intersection of two already-scarce skill sets, commerce domain knowledge and platform engineering, which narrows the pool further.
Screen for candidates who think in terms of how systems talk to each other, not just how well they know one platform. As retailers move toward composable, API-first architecture, roughly 79 percent of IT leaders say they want to bring more of those principles into their stack, according to MACH Alliance research, which means integration experience across two or more systems is now a stronger signal than deep tenure on a single one.