MRTEN — the platform a business runs on

This is the clearest answer I have to "can he own a system and still ship".

The platform covers what a retail operation actually touches: orders, payments and transactions; inventory, stock transfers and shipments; suppliers, supplier invoices and supplier payments; a storefront, flash sales, coupons and gift cards; and the delivery app with the people who use it. Fifty-six modules, built and maintained without the thing collapsing into one unmaintainable service.

The first decision was the one that mattered. The domain is modelled around how the business already works — the sequences the operations team already followed, including the awkward ones — rather than around the screens someone had sketched. Software that ignores that gets rejected by the people meant to use it, however good the architecture underneath is.

Money forced the discipline. Orders, payments, transactions and supplier payments all have to agree at the end of the day, so state transitions are checked against what the record already says rather than against what an incoming request assumes. Background work runs through BullMQ, where a job can fail and be retried without applying twice.

It runs on Azure, and I own that too — the VMs it is deployed to, the container setup, and the OpenTelemetry monitoring that tells me when something is wrong before a customer does. Object storage sits on S3. Owning a platform end to end means owning where it runs, not handing it over at the repository boundary.

What I would point at in an interview is the duration, not the launch. A year of continuous work is a different claim from a launch announcement: it means the thing survived contact with real use, real money and real edge cases, and somebody stayed to look after it.