What we actually do
We run and maintain WooCommerce stores and everything sitting behind them: ERP, CRM, warehouse and accounting integrations, order and stock sync, custom admin tooling. Some of it we inherited. Some of it we built. Right now we’re moving store backends off WooCommerce/PHP onto NestJS, service by service, without taking anyone’s shop offline.
It’s real, messy, revenue-carrying infrastructure. Not a greenfield playground, and not a body-shop ticket queue either.
The role
We’re looking for one or two people who are somewhere between a very strong senior and a fractional CTO. Concretely, that means you can:
Read a broken system and explain it. To another engineer, and to a client’s finance director, in the language each of them needs.
Own scope. Break vague requests into estimable pieces, give a number, and defend it when reality pushes back.
Lead people. Review code, mentor mid-level devs, run a small team without turning into a bottleneck.
Decide. When to patch the PHP, when to strangle it out into a Nest service, when to leave it alone because the ROI isn’t there.
What you’ll work on
Maintaining and extending production WooCommerce stores (plugins, hooks, custom order flows, performance)
Designing and building NestJS services that progressively replace Woo backend functionality
Integrations with ERP, CRM, payment, logistics and accounting systems — REST, SOAP, webhooks, queues, whatever the vendor forces on us
Data migration and dual-run strategies where old and new systems have to agree for a while
Technical discovery with clients: audits, estimates, roadmaps.
What we need from you
7+ years building and running production web systems
Deep PHP — WooCommerce/WordPress internals specifically, not just “I’ve used Laravel”
Deep Node/TypeScript — NestJS in production, module architecture, queues, testing
MySQL/PostgreSQL performance work: you can read a slow query log and know what to do next
Comfort with legacy: you’ve untangled someone else’s code without rewriting everything out of spite
You work with AI tooling daily — Claude / Claude Code, Cursor, or equivalent — as a real part of your workflow, not a demo. You know what to delegate, how to review what comes back, and where it will confidently lie to you.
