I became a researcher because I love sitting with people, listening for what they're not saying, and using that truth to change how products get built.

I studied Computer Science at Ball State, which shapes how I approach research: I can read code, talk to engineers in their language, and understand what's actually feasible. That background keeps my research grounded in reality instead of wishes. I started at OneAmerica Financial running A/B tests and analyzing user behavior. Then I moved to direct community research, learning to recruit from Reddit, synthesize unfiltered feedback, and turn patient needs into design signals.

Today I research high-stakes problems for underserved communities. SFN patients managing chronic pain. Retirees protecting their savings. Kentuckians filing for unemployment during their worst weeks. I dig through app store reviews, Reddit threads, and survey data to surface the insights that change how teams move. The common thread: people who've been let down before need research that earns trust, not research that assumes it.

If your team has a messy, high-stakes problem and needs a researcher who can synthesize signal from noise and turn community insights into products that move metrics, let's chat!