An engineer who adapts to tools rather than being defined by them.

I started out curious about what happens behind the scenes on the web. That turned into a habit of following a problem all the way down — from the interface someone touches to the schema underneath it and the job that cleans up after them.

Day to day I work across the MERN stack and Flutter. Away from work I build and run Study Room, which has taught me the parts of engineering a job rarely does: choosing what not to build, owning an incident at midnight, and pricing something so it can pay for its own servers.

I’ve also folded AI into how I work — automating the repetitive parts of my own pipeline and building with tools like Claude and MCP servers. Useful, but the interesting judgement is still deciding what the system should do.