After a short stint on Feeds, The Athletic pivoted to focus on increasing conversion rate from users who are registered but not subscribers. I was shifted to this new team to work on some more experimental features including adding Storylines, which route users to what our programming team feels are relevant articles in big stories.

eg. https://www.nytimes.com/athletic/6192009/2025/03/10/new-york-yankees-gerrit-cole-season-ending-surgery/

Occasionally published as a curling correspondent.

eg. https://www.nytimes.com/athletic/live-blogs/winter-olympics-2026-milano-cortina-live-updates-day-one-schedule-events-scores-results/gm13ZDCjS3dy/tsePTtMakake/

After a successful major migration during game plan, we shifted back to more normal product work, and I was placed on the Feeds team. I worked on several modules and created the my teams module, which places stories about a user's favorite teams higher, which may have been pushed down due to more national stories.

As a part of our acquisition by the New York Times, we had to move our website from https://theathletic.com to https://www.nytimes.com/athletic.

My main project was to convert our old fonts to NYT fonts, which helped keep a visual consistency with other NYT publications. As part of this project, I worked with designers, game plan project leaders, and other engineers to make sure our new fonts were implemented correctly. As part of the tech lead of this project, I had to take on many PM responsibilities, collecting, prioritizing, assigning, and executing bugs/tasks, among other things.

I am a founding engineer on the newly formed Audience team. Our projects aim to help connect our writers to our users better through various means including better tooling for our writers, SEO, and features for our users

Founding Engineer on the Community Team.

I built tools to build more community among our readers. The largest project I worked on with Community was our Live Rooms product. Live rooms allows our writers to have live audio discussions with our users. We saw our usage scale from small 20 person rooms to over 1,000 simultaneous users.

I interacted with many departments in the development of live rooms. I helped brainstorm ideas for future iterations and worked with editorial staff on any feedback they had on our product