A bit more.
I call myself a software designer because I think it's the more honest name for what I actually do. Most of the typing happens through a model now — what I bring is the part that's still hard: judgment about what to build, how the pieces fit, and what's worth keeping.
I went to UC Berkeley four times. An M.S. in Industrial Engineering & Operations Research (with a focus on data science and machine learning), a B.S. in Electrical Engineering & Computer Science, a B.S. in Industrial Engineering & Operations Research, and — the one I'm proudest of, honestly — a B.A. in Music. I conducted the Berkeley Philharmonia and assisted with the Symphony.
Most of my engineering work has been at the messy edges where data, ML, and infrastructure all touch. Fetch Rewards, NHERI SimCenter, Amazon Web Services. Each role taught me something different about what makes software work for the people stuck using it.
If you'd rather skim the formal version, here it is — the rest is below.