I have led product in fields that share one property: being wrong has consequences. Payer claims, where a dropped file is a compliance failure. Pharmacy benefits, where a stale formulary bills the wrong price. Retail pharmacy technology, where a store that cannot ring up a sale is a store that closes for the day. Business-to-business commerce, where quoting, ordering and invoice reconciliation need consistent commercial terms. And pharmacy operations, where the checks I work on support pharmacists’ safe-dispensing decisions.
I have led shared-platform teams and program budgets, enterprise integration work across regions, and pharmacy product work involving compliance, patient safety and applied AI. Those experiences required moving between strategy, technical analysis and the practical needs of the people operating the product.
I am technical enough to read the data model and find the rounding error, to set a latency budget and hold engineering to it, to argue about an evaluation threshold I have actually looked at, and to design the tool contracts an agent is allowed to call. My pharmacy training helps me distinguish a clinical question requiring pharmacist judgment from a data or arithmetic defect. And I am operational enough to know that a launch is not done until the operator is trained, the runbook is written and the seam is instrumented.