Twenty plus years running large web and email platforms across Amazon, Rosetta Stone, and James Madison University, turning platform work into measured outcomes and building the tools, in Python and Ruby, that remove the manual work.
Twenty plus years across Amazon, Rosetta Stone, and James Madison University turned platform work into measured outcomes. Starting as an Amazon software engineer built a root-cause-first, customer-first habit that carried into every role after. Today that means owning quality, uptime, and cost for a 34,000 page platform serving 500 plus content owners.
At JMU, retiring two paid platforms by building their replacements in-house eliminated roughly $90,000 a year in vendor and manual cost. Redesigning three strategic pages around request-information and schedule-a-visit lifted prospective-student conversions 42 percent. Minute-level homepage monitoring and a daily 404 report have sustained availability with no known downtime in 12 years, surfacing issues before the system administrators.
Every cell is a month held up on a 34,000 page platform. Brighter cells mark the year a paid tool was retired, a mobile platform was rebuilt in-house, or legacy risk was cleared. Select a year to see what shipped.
Hover or tap a year column to see the platform milestone that shipped that year.
Owning quality, uptime, and cost for a 34,000 page platform serving 500 plus content owners, retiring paid tools by building in-house replacements, and governing the CMS to 71 canonical object types.
Coordinating online and mobile product delivery for teams of up to 45 across engineering, QA, and stakeholders, and shipping the Rosetta Stone Kids product.
Leading a 5-person engineering team delivering 13 production services and 24 libraries, and replacing Adobe LiveCycle Collaboration with an in-house build in 9 months.
Building the org's first developer training program and owning 42 code packages across 11,863 files, earning Outstanding, the highest rating.