Denver, Colorado · MPH · Open to new roles
UX Researcher & Research Technologist
Clinical researcher. UX practitioner. I've spent six years embedded in the problems most designers only read about.
I came up on the science side of healthcare — managing clinical research programs, designing longitudinal study infrastructure, and working daily alongside physicians, nurses, and coordinators in regulated, high-stakes environments. That foundation gives me something most UX researchers don't have: I understand the clinical context, the data behind it, and the systems that have to hold it. I'm looking for roles where the research is serious, the users are complex, and getting it right actually matters.
I came up on the science side of healthcare — managing clinical research programs, designing longitudinal study infrastructure, and working daily alongside physicians, nurses, and coordinators in regulated, high-stakes environments. That foundation gives me something most UX researchers don't have: I understand the clinical context, the data behind it, and the systems that have to hold it.
Over six years at the LEAD Center (University of Colorado Anschutz), I've owned the full research and product lifecycle for health data platforms — from stakeholder discovery with clinicians and scientists, through data architecture and delivery, to the automated systems that keep complex multi-site studies running. My work sits at the intersection of UX research, cardiovascular health, and regulated research infrastructure.
BS in Public Health with a minor in Chemistry (pre-med track), followed by an MPH in Environmental & Occupational Health — earned while working full-time as a researcher. Formal training in epidemiology, health systems, and research methods, combined with six years of applied research in cardiovascular and chronic disease.
Six years embedded in regulated clinical environments — conducting discovery, designing systems, and turning user input into better products.
I conduct stakeholder interviews, usability evaluations, contextual inquiry, and literature reviews to understand what users actually need. I've led discovery sessions with MDs, NPs, and research coordinators — translating clinical workflows into design requirements.
Six years of daily collaboration with physicians, nurses, investigators, and research staff across Colorado, Ohio, and South Carolina. I understand clinical roles, workflows, and the institutional constraints that shape what's usable in practice.
I document, track, and act on user feedback in continuous cycles. I maintain formal update logs capturing stakeholder requests, rationale, implementation status, and site-specific context — turning ongoing user input into a living design record.
I've built data products from scratch — starting with stakeholder interviews, translating clinical needs into requirements, and owning execution through delivery. I define what gets built and why.
REDCap database architecture, SAS-based ETL pipelines, QAQC automation, and multi-site data governance. I build the infrastructure and write the logic that keeps it honest.
I've driven buy-in from PIs, site coordinators, and leadership across Colorado, Ohio, and South Carolina — getting teams aligned on tooling, process, and priorities without direct authority.
Tableau dashboards for study metrics, SAS automation for monthly PI reports, and a 30-year legacy data migration to enable longitudinal analysis. I turn messy research data into decisions.
IRB compliance, audit readiness, biospecimen chain-of-custody, and NIH reporting standards. I understand what it means to build in a regulated context — and how to ship within it.
I translate complex data systems and research operations into clear narratives for PIs, leadership, and funders. Monthly reporting, stakeholder documentation, and the ability to make technical work legible to the people who make decisions about it.
Five years at the intersection of health data, clinical research, and regulated infrastructure.
Direct experience with cardiovascular signal data from the SEARCH CVD study — including SphygmoCor pulse wave velocity, central blood pressure, echocardiogram data, and HRV. I understand what these measures mean clinically and what it takes to collect, validate, and analyze them at scale.
Five years managing data infrastructure for longitudinal adult cohort studies focused on type 1 and type 2 diabetes. I understand the complexity of long-term follow-up, multi-site coordination, and the data quality demands of federally funded chronic disease research.
MPH concentration in Environmental & Occupational Health. Research background includes climate resilience and indigenous food systems work. I bring a systems-level perspective on how environment shapes health outcomes.
Published research on socioeconomic status and obesity in youth. I approach health data work with an equity lens — understanding that the communities research represents must be centered in how products are designed and deployed.
Deep familiarity with IRB protocols, human subjects protections, and NIH/CDC compliance requirements. I've operated in regulated research environments where data governance isn't a checkbox — it's a core product constraint.
I've built the data infrastructure behind biological sample collection — tracking custody, reconciling records across sites and systems, and catching discrepancies before they become compliance problems. I know what it takes to keep lab data clean, auditable, and trustworthy at scale.
The methods I reach for — chosen to fit the question, not the other way around.
Selected projects from five years of research data product work.
Led end-to-end UX research and platform design for a multi-site cardiovascular study following adults with diabetes. Conducted stakeholder interviews, workflow analysis, and iterative discovery sessions with MDs, NPs, and site coordinators to design a clinical data system that 3 sites actually use. I was the entire research and product team.
"The biggest product mistake in research is building the database after the study design is locked. I pushed to get the database team into planning early — so when the data started coming in, the system could actually hold it. That decision alone saved months of rework."
Designed and built Tableau dashboards to give PIs and site coordinators real-time visibility into recruitment progress, visit completion, and study metrics across three sites. Before this existed, progress updates required manual compilation. I identified the reporting gap through stakeholder conversations and built the solution.
"The reporting gap wasn't a data problem — it was a communication design problem. PIs didn't know what was happening across sites because no one had designed a way to show them. I asked the right questions, then built what the answer required."
Built a fully automated QAQC pipeline reconciling biospecimen records across three systems and three sites — catching discrepancies before they became audit findings. This is what data governance looks like when it's built into the product, not bolted on afterward.
"Most research teams treat QAQC as a manual review step at the end. I built it into the pipeline so discrepancies surface automatically — before they become protocol deviations or audit findings. That's the difference between reactive data management and proactive product design."
Things I built because I saw a gap and wanted to solve it.
Libby is an app I use constantly for library ebooks and audiobooks. I noticed three gaps that make the experience frustrating for heavy readers: no way to remember what you've read, no way to avoid already-read titles in search, and no in-app path to support your library. I defined the problems, designed a three-layer solution in Figma, and wrote a full product pitch for the OverDrive team.
Interactive mockup showing the full Rate & Review flow — post-completion prompt, star rating, shelf tags, and reading log entry.
"The most engaged readers Libby has — the ones borrowing dozens of titles a year — currently keep their reading logs in spreadsheets, on Goodreads, or not at all. That's an unserved need sitting inside an already-captive audience. I noticed the gap as a user, defined it as a researcher, and designed what closing it would look like."
In 2025, Libby patrons borrowed over 820 million titles. When they finish a book, the app offers nothing — no rating, no note, no memory. The most engaged readers keep logs in spreadsheets or on Goodreads. That's an unserved need sitting inside an already-captive audience.
90% of US public libraries are on OverDrive. The infrastructure exists. The audience exists. The trust exists. Libby doesn't need to become a social network — it needs to give its most loyal patrons a way to remember what they've read and give something back to the institutions that make it possible.
Post-completion prompt for a star rating, shelf tag (Loved it / Recommended / Want to reread), and optional short review. Lives in the existing Timeline — no new tab, no new infrastructure. Fully private by default. A profile stats card surfaces reading totals at the top of the Shelf screen.
"Hide already read" filter in Search prevents wasting holds on already-borrowed titles. Recommended tag unlocks a native share flow — a deep link to the title with your rating and an optional note, sent via text. Recipient goes straight to the hold queue.
Voluntary donations split across the patron's active library cards. Prompted at earned moments — 50th book, one-year anniversary — never pushed. A nonprofit pass-through model, not an upsell. Optional public profiles and social reading feeds are later-phase, always opt-in.
Borrowing records and review activity are stored in separate, non-joined systems. A review is text + rating + timestamp — never linked to a library card without explicit per-item consent. Reviews default to private. This keeps Libby aligned with library confidentiality law and removes the most significant legal risk from the feature entirely.
Goodreads is owned by Amazon, identity-required, and trust-compromised. StoryGraph requires a separate account with no connection to library availability. Libby is already where readers are, anonymous by default, and connected directly to the holds queue — making its ratings immediately actionable in a way no third-party app can replicate.
Autret, K., & Bekelman, T. A. · Journal of the Endocrine Society · 2024
doi.org/10.1210/jendso/bvae176 ↗Bekelman TA, Knapp EA, Wu G, Autret K, et al. · Journal of Pediatrics · Under review
Diaz Barreiro R, Dabelea D, Autret K, et al. · Healthy Start Study · Under review
Poster presentation · 2025 Cannabis Research Conference · Portland, Oregon
Open to PM roles, research partnerships, and science program management opportunities — especially at the intersection of health data, equity, and technology. Based in Denver, Colorado. US/French dual citizen, open to relocation.