Selected engagements, each told the same way: the problem, the call I made or led, and what changed. Detail stays at the level I can publish.
LeapSpace: from zero to 1M+ active users
Engineering Manager · Elsevier, Aug 2025 to present
Problem
A new AI platform for research discovery, starting from inception with no team in place.
Decision
I led the platform from inception to production in under 6 months. I built the team, ran the recruiting and designed the team topology.
Outcome
Launched in January 2026. Subscription sales have passed $6.5M, and active users passed 1M in October 2026.
Engineering Village: a $40M+ discovery platform
Lead Software Engineer · Elsevier, Sep 2022 to Mar 2024
Problem
I was accountable for the world's leading engineering information discovery platform. The team sat in Dayton, Ohio, and the big data pipelines ran on an aging on-premises stack.
Decision
I managed two teams of 12+ engineers, moved the team from Dayton to Amsterdam, and migrated the big data pipelines to the cloud.
Outcome
About $500K saved per year, and pipelines that are more scalable, more traceable and less error-prone.
Scopus: modernizing a legacy platform
Lead Software Engineer · Elsevier, Sep 2020 to Aug 2022
Problem
Legacy APIs took about 30 seconds to respond, and the author feedback wizard was a JSP application that shipped once a month.
Decision
I rebuilt the wizard on React and Redux, optimized the legacy API, and designed a data-driven author profile curation system as a proof of concept.
Outcome
API responses dropped from about 30 seconds to about 3. Releases moved from monthly to daily. NPS went up.
Zoover: replacing a 15-year-old legacy system
Software Development Team Lead · Zoover, Jan 2019 to Sep 2020
Problem
A black-box system more than 15 years old was slowing both delivery and the website.
Decision
I led the migration to the new stack, built an internal headless CMS, and coached the developers on the team.