How I Work
Most teams need a product manager, a domain consultant, and a senior engineer to get from idea to production. I've been all three in healthcare and life sciences for twenty-six years.
The right problem, not just the right technology
Most projects in healthcare and life sciences fail before anyone writes a line of code because they focus on solving the wrong problems. I've spent twenty-six years between science and software: bioinformatics research at GSK, translational medicine at CHOP, product and engineering at venture-backed startups and AWS. I know which problems are worth solving and what it takes to ship the solution.
Strategy and execution in one seat
I define the product and I build it: requirements, architecture, production code, APIs, data pipelines, integrations, infrastructure. The person who understands the science is the same person who writes the spec and builds the implementation. No handoffs, no telephone game. You move faster with fewer people.
AI-native speed, senior judgment
AI has compressed the time it takes to build software. I use it aggressively as core infrastructure for how I work. One person with the right experience can now deliver what used to take a team of ten. But speed without direction is just expensive chaos. Knowing what to build, what to skip, and what will actually matter to the business is twenty-six years of hard-won human pattern recognition, not a prompt.
If you have a hard problem in healthcare or life sciences, I'd like to hear about it.
No pitch deck, no discovery call script. Just tell me what you're trying to do.