Holding a tray of seasoned steaks for the grill on a neighborhood sidewalk at golden hour — Steak night with the housemates, Ann Arbor, April 2026.

Curious about how things work.

Welcome to my paper. I'm currently finishing my chemical engineering degree at the University of Michigan, and here's the backstory behind my pursuit of software engineering.

It started in a wet lab. I was doing cardiac fibrosis research, and a surprising amount of the job was manual and repetitive: counting cells under a microscope, over and over, to keep a culture on schedule for differentiation. It had to be done, it had to be done carefully, and none of it needed a person. With a little help from a friend, I built a cell-counting machine to do it for me.

That was the first time I'd used software to fix a problem I actually had, and it changed what I wanted to work on. I've been building software, and more recently machine learning, ever since.

Most recently I was a software engineering intern at Oaklet, where we built direct-to-patient infrastructure for pharma manufacturers. Same principle, larger scale: find the step nobody should be doing by hand, then build the thing that removes it.

The problems I like best sit where the physical world meets software. Lately I've been pointing my own projects in software, machine learning and embedded systems back toward biology and physiology, which is where this started.

Continued on Projects

Building direct-to-patient infrastructure at Oaklet

Software Engineering Intern, Bozeman, Mont.

Oaklet is a white-labeled direct-to-patient platform that lets pharmaceutical manufacturers own and manage their patient relationships directly. I joined as a forward deployed engineer, which in practice meant splitting my time between full-stack software engineering and enterprise sales.

On the engineering side I worked on intake workflows and helped ship a fully manufacturer-owned intake form and payment process. On the sales side I attended conferences across the US, helped shape new go-to-market strategies, and later helped assemble a pilot portfolio worth $5.5 million.

Two of us giving a thumbs up in front of a whiteboard covered in database table sketches — Just a small refactor.

Senior at Michigan, chemical engineering

Expected May 2027

Balancing the last stretch of my degree with a newfound passion for software engineering, mostly through my own projects.

This semester's coursework is ChE 466, process controls and dynamics; ChE 460, chemical engineering laboratory II; ChE 296, a special-topics introduction to materials science; CHEM 261, quantum chemistry; and Guitar 112, advanced guitar.

Outside of class the focus is two projects. I'd like to have a v1 of Propoxity done by the end of the semester, and to start working with pilot coaches on Physioform Labs by the beginning of next year.