Technical Architect – Commerce & Omnichannel

Department: Commerce and Omnichannel

Reports to: Managing Director, Commerce and Omnichannel

Type: Full-time, senior

Location: Fully remote, Eastern time zone hours

Time split: Roughly 60% hands-on engineering, 20% architecture and technical direction, 20% pre-sales and client-facing — the real mix moves around week to week depending on what's in flight

The short version

We build and run complex commerce systems for our clients — Adobe Commerce, Shopify, BigCommerce, OroCommerce, and whatever the next one turns out to be. We're looking for an architect who can own the technical design of those builds and still be the person writing the hard parts.

The distinguishing requirement here isn't a platform. It's platform mobility. We need someone who can land in an unfamiliar codebase, work out how it actually behaves, and be productive in days — then do it again next quarter on something else. If you've gone deep on one stack and want to stay there, this isn't your role. If “new platform, six weeks, go” sounds like the good part of the job, keep reading.

What you'd walk into

• ~50 active support accounts and ~5 concurrent implementation projects across the division — you'd own a portion of that book, not all of it
• Clients that straddle the line between mid-market and enterprise — enterprise-grade problems without enterprise-sized teams to throw at them
• A team of senior architects, developers, and offshore contractors staffed as a shared resource across accounts. You'd own your projects end to end and work alongside the other architects, not above them.
• Real integration surface: ERP, PIM, CRM, OMS/WMS, tax, payment, search, and fulfillment systems, plus middleware (Boomi, MuleSoft, Celigo, or services we build ourselves)

The workHands-on engineering (~60%)

• Build the complex backend and integration work: modules and extensions, services, GraphQL/REST endpoints, data synchronization — the parts other people get stuck on.
• Lead debugging and performance work on high-traffic production systems.
• Review code and refactor with intent. The standard gets set by what you ship, not by a document.

Architecture and technical direction (~20%)

• Own end-to-end technical design on your projects: data models, API contracts, extension strategy, integration topology, and failure/reconciliation behavior.
• Contribute to our coding standards and architectural guardrails and hold the line on them in the work you own.
• Mentor developers through pairing and design sessions. The goal is fewer escalations reaching you over time, not more.

Pre-sales and client-facing (~20%)

• Sit in scoping and roadmap conversations and give feasibility and sizing input on proposals.
• Represent the technical position directly to clients — including when the answer is “not the way you've asked for it.”

How we work

We're a consultancy. That means several clients at once, genuine context-switching, and work that ships and then gets supported for years. Some engineers find that energizing and some find it draining; it's worth being honest with yourself about which.

AI-assisted development is part of how we deliver, not a side experiment. We're actively building out internal AI tooling and practice, and this role has a direct hand in shaping how that gets applied to client work.

What success looks like

At 90 days — you've taken technical ownership of at least one active implementation, you know where the bodies are buried across the support book, and you've shipped production code on two different platforms.

At 12 months — the integration patterns you've built are getting reused on the next client instead of rebuilt from scratch. The numbers you put behind a scoping conversation hold up once the work is underway, so your input gets trusted earlier in the sales cycle. And at least one developer on the team is doing work they couldn't have done a year ago.