Engineering the systems behind the stories.
Web and mobile engineering for healthcare publishing: connecting reading experiences, structured content, search, and professional communities.
- My role
- Product Engineer · Since January 2026
- Focus
- Web publishing & mobile
- Tools & systems
- React, Next.js, Sanity, GraphQL, React Native, Supabase, AWS
& mobile communities
Oncology
Network
The challenge
A publishing business has to serve readers, editors, and multiple brands at the same time. Content needs to be organized, searchable, and presented in a way that works across devices and formats.
My work at MJH Life Sciences spans healthcare publishing sites and a mobile community product, contributing within an established engineering organization.
My contribution
I joined MJH as a Software Engineer in February 2021 and became a Product Engineer in January 2026. My experience includes both frontend and backend implementation across the publishing stack.
- Developed web experiences using React and Next.js, with Sanity and GraphQL supporting content delivery.
- Worked across healthcare brands including Targeted Oncology, AJMC, Cancer Network, CURE, and dvm360.
- Contributed to search and SEO work, including Algolia integration.
- Built frontend and backend functionality for One Community, a React Native community application backed by Supabase.
- Worked with cloud services, error monitoring, and delivery workflows as part of ongoing product development.
The product behind the page
Think in content systems
A page is one output of a larger publishing workflow. Work across Sanity, GraphQL, and frontend rendering means thinking about how content is structured and how that structure reaches the reader.
Connect web and mobile thinking
Publishing sites and a community application have different interaction patterns. Working across both has expanded my experience from content presentation to application state, user interactions, and backend integration.
Build within a team
Enterprise engineering also means contributing to systems other people maintain. Clear component boundaries, readable implementation, and debugging across services matter alongside the visible feature.
What this work demonstrates
MJH is the enterprise side of my experience: contributing to established products, working across a portfolio of brands, and connecting frontend decisions to content and backend systems.
Good product engineering accounts for the people producing the content as well as the people reading it.