Most engineers know what to build. Fewer know why it matters — or how
to fight for the right thing when timelines, stakeholders, and competing priorities all
pull in different directions.
I spent two years as a Product Manager at Anglepoint before returning to
engineering as an SE3. That stretch — sitting in user research sessions, writing specs,
defending roadmap decisions to leadership, and watching features live or die in the
market — fundamentally changed how I write code. I build things I've personally seen
users struggle with. I scope features with the delivery pressure of someone who's been
accountable for the timeline. I review PRs knowing what the feature is trying to do, not
just whether the syntax compiles.
On the technical side, I've spent five years as a full stack engineer on an enterprise Software Asset Management platform — the kind of product where correctness
matters, scale is a given, and "it worked in dev" is never a good enough answer. I led a
full AngularJS-to-Angular migration with one other engineer, built REST APIs consumed by
thousands of users, and acted as the frontend subject matter expert across multiple
subsystems during a major .NET solution migration.
I'm currently a Software Engineer at Filevine — a legal operations
platform built for law firms — working on the frontend with Svelte and TypeScript. It's
a different domain than enterprise SAM, but the same discipline: complex data, real
users, and software that has to work.
I'm also open to what's next.
When I'm not at a keyboard: Road biking · Mountain biking · Trail running ·
Paddle boarding · RV travels · Opinionated beer tasting