Engineer Manager, Commerce Solutions

About this role

About Nexcess

Nexcess provides specialty cloud solutions for organizations where performance and compliance have to coexist. We serve businesses worldwide, from agencies scaling client sites to enterprises running mission-critical operations. We've built our reputation on deep technical expertise and genuine partnership with every client we work with. Behind every environment we manage is a team of people who take the craft seriously and keep showing up when it matters.

About Commerce Solutions

Commerce Solutions builds and operates the application layer of Managed Applications, Sites & Stores products: the WordPress, WooCommerce, Magento and other application stacks our customers actually run their businesses on, the automation that keeps those applications current and safe to upgrade, and the tooling and images the platform uses to create and manage them.

The Role

You will run and own one engineering team end-to-end: its architecture design, its delivery, and its roadmap. This is a hands-on engineering role, and you are the one person who answers for what the team lands.

The work in flight is the visible part. The job is the machine around it: how work is scoped and cut each month, what stands between a change and production, how much of it is AI-assisted, and how much of the team's week goes to things that are not engineering.

How we work

•
Business alignment and focus come first. Engineering here exists to move the business, not to be busy. You will pick the few things that matter most, say no to the rest out loud with the Product counterpart, and deliver them on dates the business can plan around, at a quality that does not come back as an incident or a customer escalation. Predictable, reliable delivery of quality software is the output of this job, and everything below is in service of it.

•
This job is hands-on, and more so every quarter. Management layers here are deliberately thin, and a manager who has stopped reading code cannot lead a team whose code is mostly AI-generated. You will write specs, review pull requests yourself, run the AI harness daily, and ship real work. Not the critical path, but enough that your technical judgment is current rather than remembered.

•
Whoever ships it owns it, regardless of who wrote it. Most code is AI-generated now, so the judgment moved to either side of it: specifying exactly what to build, and verifying that what came back is correct, secure, and operable. Managers are more accountable in the AI era.

•
You will be Product's best friend. The managers who succeed here are the ones their Product counterpart wants in the room: you shape the roadmap together, turn business need into something the team can credibly commit to and deliver as expected, and make the trade-offs legible early. Enabling the business is the point of the job; the technology and process and your team is how you do it.

•
Your team goes on call for what it builds, and you take your turn on the rotation. Engineering declares risk and timelines in writing for the business to accept.

What we'll measure

•
Speed: DORA High, with Elite as the target. You get there through engineering excellence and a performance-driven culture, not through just pressure. Baseline where your team actually sits, publish it, and move it.

•
Predictable, reliable delivery of quality software. Planned versus delivered every month, dates renegotiated early rather than missed quietly, defects reaching customers and incident recurrence falling.

•
AI adoption and its impact. Measured by AI-assisted outcomes.

What you’ll do

•
Own architecture design, delivery and roadmap for your team. Build the partnership with Product that makes the roadmap real: shape it together, commit to it, and then deliver it. ● Own the engineering outcomes for Commerce Solutions' product space — the WordPress, WooCommerce, Magento and other application stacks customers run their businesses on, plus the automation, tooling, and images that keep those applications current and safe to upgrade — building deep understanding of its customers, architecture, dependencies, integrations, and operational risks. Ensure the team is accountable not just for delivering work, but for the long-term health and evolution of the products it owns.

•
Stay in the work. Write the specs, review pull requests yourself, and ship real changes. Your call on a design or an estimate has to be current, not remembered.

•
Run the AI harness yourself, and make your team run it. Agentic tooling every day, specification-first working, automated review in the pull-request path, and reusable skills you build and share rather than leave on your own laptop. You cannot drive adoption you do not practice.

•
Scope and cut the work. Turn roadmap items into scoped, estimated work with the unknowns named, run it on a monthly cycle with an explicit cut line, and report status honestly, including bad news, before it is asked for.

•
Clear cross-team engineering dependencies before they block you. Find what your team will need from another team, agree it directly with that manager, and land it ahead of the work rather than escalating once it is late. Kill the ones that keep coming back.

•
Hold the engineering bar that gets your team to DORA High and beyond. Know your four numbers and remove what actually slows a change down: review latency, build time, environments, handoffs, approval loops. Tests with every change, coverage gating on changed code, and evidence on the pull request rather than an assurance that it works. Release go/no-go is yours, made on evidence.

•
Grow your engineers. One-to-ones actually held, a current growth plan for each, and direct feedback given early, including the feedback nobody wants. Own hiring end to end and hold the bar.

•
Own what you run, not only what you ship. A fair rotation, incidents written up with actions closed on dates, toil removed rather than absorbed, and no bus factor of one left standing.

What you’ll…