I started on the support team — everything from minor client customizations to production bugfixes. It was a great way in: it forced me to understand every component of the system, and what merchants actually expect from it.
Next I joined the team integrating a company we'd acquired (RubyHas, running on Deposco WMS). I had to understand both sides' business processes and design an integration that wouldn't disrupt operations. We split it in two:
The first half was the hard one — re-implementing every integration the customers had built against the old system, and a significant redesign of the internal ShipMonk system so it could drive multiple WMS backends instead of just our own. During this I touched basically every component in the ShipMonk system. We migrated ~200 customers with zero disruption; I spent months on-site in US warehouses keeping the cutover smooth.
As the migration wrapped, I joined the WMS team. From there I bootstrapped ShipMonk's first B2B domain inside a historically D2C business — defining the customer and compliance requirements, building the EDI integrations and routing-guide compliance flows, and taking the B2B key metric from 55% to 95% in a year.
I relocated to the US and embedded on the warehouse floor, partnering directly with operations. The standout: turning around a struggling Amazon Vendor account — fixing the compliance and process problems driving chargebacks, and saving the customer roughly $80k a quarter.
Today I lead the B2B engineering team. A lot of recent work is about leveraging AI across the role — bootstrapping new projects quickly, developing code across multiple services, managing several projects at once, and preparing product specifications in a complex domain.