Build / Integration
Systems Integration
Connecting commerce to everything around it — PIM, OMS, pricing, payments — with contracts that hold under load.
Commerce is never one system. It is a storefront surrounded by a PIM, an OMS, an ERP, a pricing engine and a payments provider, and most outages start at a boundary between two of them rather than inside either.
The discipline is to treat every integration as a contract with an owner, a failure mode and a backpressure story — not a nightly job somebody wrote once and left. Where the volume justifies it that means events and queues; where it does not, a well-bounded synchronous call is honest and cheaper to run.
Kafka and RabbitMQ for messaging, custom loaders where a vendor connector does not exist, and pricing engines written from scratch when the platform could not express the rules.
Where this has been done
Sr. Developer
Designed and built the ATG Loader that ingested PIM data into the commerce platform.
ATG Developer
Custom ATG pricing engines at item and order level, driving dynamic B2B pricing.
Senior Associate Technology
Messaging and caching layer — RabbitMQ, WebSocket, Oracle Coherence — across a distributed commerce stack.