Full stack engineer who
speaks business too.

A daily automation that reads every client's preferences and sends each person exactly the content they asked for, at the rhythm they chose.

Clients set what they want and how often they want it — real time, daily, twice a week, weekly — plus the topics they care about. A job runs every day, and for each user it checks their chosen frequency, pulls everything published inside that window that their permissions entitle them to, and sends it. Nobody assembles anything; nobody presses send.

I built both halves: the preference center where those choices are made, and the email that comes out of it — grouped by content type, with real titles and summaries, designed to pull people back into the platform rather than just notify them.

The engineering

The email HTML is generated server-side from our C# project and had to render correctly across desktop clients and webmail alike — a constraint closer to 1999 than to modern CSS. I validated it by hand, client by client, until it held. It held well enough that when the company built its next content email, my template became the model for it.

Results

The digest on its own now drives about as much portal traffic as the entire previous email program did — and it seeded a family of three.

Took a publishing chain that crossed three systems by hand and made it run on its own.

A Faculty Poll is a question a client brings to IANS that several faculty experts answer. Publishing one used to mean moving it manually between Salesforce, the CMS and the search index. I built a daily job that picks each poll up once the answers are confirmed, assembles the content and the downloadable document, and pushes it live.

Same stack as the rest of my work here: C# endpoints for the Salesforce connection and the Sitefinity content, a Node.js endpoint for Elasticsearch indexing, React and JavaScript for the published page above.

Turned a content library into a path people follow — and come back to.

The material already existed — on-demand sessions, video insights, learning pathways — but it sat there as a catalogue. I built the layer that turns it into progress: an active roadmap with live completion, the pathways and sessions inside it checking off as they're finished, the other roadmaps available with progress on each, a goal tracker, and badges and certification that accumulate as people work through it. The content team got the tools to organize the tracks themselves.

The part I'm proudest of

Completion is tracked against the content itself, not the route someone took to reach it. Wherever a person finishes a session, their roadmap knows. It would have been far simpler to only count activity inside the dashboard — and it would have quietly lied to users.

Results

Relaunched a full product section and rebuilt its operational framework into something people use again.

Two pieces shipped together. First, a homepage for the Privacy Operations section that surfaces everything in it — framework guides, cheat sheets, slides, toolkits, briefings — grouped so you can see what exists instead of having to search for it, with the content team owning what appears and in what order.

Second, the framework itself: nine domains, each holding a set of principles. I built and rebuilt the main framework page, the navigation between domains, and the detail page for every individual principle — downloads, ratings and comment threads included — plus a ready-to-use workbook covering all domains and principles. Structure was the whole point: the previous framework had fallen to a fraction of its former use, and reviving it meant giving people something they could work through one principle at a time.

Results

Section consumption had been sliding for roughly a year. The relaunch doubled it against the pre-launch months and reversed the trend, with framework activity up an estimated 83% year over year.

Gave the product a front door. Before this, users landed on a search box.

The portal's entry point was a search page — you arrived and you searched. I built a landing page in its place: one surface that shows the different products the company offers, with articles streaming in live and the content team able to update text, thumbnails and ordering themselves.

One of my first projects here, built before AI assistance existed. The page has evolved since — the architecture I chose has held.

Results

Total portal traffic rose 25–30% year over year across the period. Other work shipped in the same window, so I separated out its contribution and quote only what the homepage itself earned.