UX researcher and interaction designer
Pursuing human-AI interaction, agentic UX, creative tools, and research-heavy product work.
Current fit
I am open to UX research, interaction design, human-AI interaction, agentic UX, and scoped consulting roles. The proof is concrete: a 15-participant moderated mobile usability study, a 56-criterion NPR WCAG audit with 74 versus 7 axe issues and 78 versus 12 WAVE issues, a SensorSynthFM physical-device build, and ten years of Pittsburgh Ableton User Group leadership.
My background includes English writing, electronic music production, community leadership, UX research, and AI systems work. I bring the domain knowledge into the research question, then keep the claims tied to artifacts and observed limits.
How the pieces connect
This is the clearest way to see how the pieces connect: music, community work, UX, and AI systems design.
Music, community, UX, and AI systems
Each domain supplies methods and constraints for the next. The connection is practical, not a destiny story.
Music taught pattern recognition. Community work taught me where people get stuck. UX gave me a way to see that clearly. AI systems design is where those threads meet.
§Interactive map
Tap a ring or node to explore
How I work
I learn the domain, learn the users, and make the decision boundary visible. My English writing and music background help me notice language, timing, and creative intent. My UX training gives those observations a research method.
I am building this site with Clarence, the public name for my long-running AI collaboration system, and AI coding tools. I review the hierarchy, copy, artifacts, and claims. AI tools contribute code and drafts, and I do not claim sole authorship of AI-assisted copy.
What is Next
I complete the Kent State MS in December 2026. I am pursuing roles where research, interaction design, human-AI interaction, and agentic UX can inform a real product decision.
Practical Links
The main site hierarchy is Work, Lab, Writing, and About. The practical pages live here.
Building This Site
I built the first version in late March 2026 and have kept rebuilding it as the evidence changed. The stack is Next.js, TypeScript, and CSS Modules, deployed to GitHub Pages with Cloudflare in front of it.
It is a collaboration between Clarence and me. I make decisions about design, voice, layout, information architecture, evidence, and public claims. Clarence and other AI coding tools help with code generation and build work.
The portfolio pairs AI-assisted drafts and code with research artifacts, process records, public graphs, and build evidence. Some projects still need stronger visual documentation, and those gaps remain visible.
The git history tracks the site changes. The working question is how to build useful systems while keeping human judgment and failure evidence visible.