I’m an instructional designer who also ships code. I built a private AI assistant for iPhone on my own, and I’ve spent four years teaching complex software to people who don’t want to read a manual. Now I’m looking for a role in developer relations or developer education.
Three examples of how I work: building it, testing it, and explaining it.
An iPhone app that answers with sources, writes cited research reports and runs routines, using AI models on servers I own. Anything with consequences waits for your OK. About 150,000 lines of Swift, now in App Store review.
How I built it →
Turning a screen recording into a click-through software simulation used to mean marking every click by hand. I built a Mac tool that finds the steps for you. It runs entirely on the computer and flags anything it isn’t sure about.
How it works →screen changes caught in testing
Software training for 2,000+ accountants, 40+ how-to videos for dental teams, onboarding for new hires, and job-readiness training for adults with disabilities. The tools change; the work is the same: figure out what people need, cut the rest, and show it clearly.
See how I taught each group →The same habits show up whether I’m writing Swift or writing a training script.
Before I build or teach anything, I find out who it’s for, what they already know, and where they get stuck. Then I cut everything they don’t need.
I test what I make: 297 automated tests on Budulai, a 53-for-53 check on the detector, and peer reviews of other designers’ courses.
Good tools and good docs say what they can’t do. My detector flags steps it isn’t sure about, and Budulai says what it keeps instead of claiming nothing.
Day to day, across building and teaching.
BA in Film Studies from Willamette University, which is still how I think about pacing and story in training. More detail in my résumé.
Portland, Oregon. Open to remote work or relocating.