Experience

Built R&D organizations and products from the ground up.

I have spent my career building computational R&D teams, software and data systems, and diagnostics products that had to survive the full path from research through validation, commercialization, regulation, and launch.

What that means

I know what works because I have also seen what fails.

I have seen teams scale too fast, architecture chosen too early, systems over-engineered, testing left too late, evidence strategy bolted on at the end, and process added before it was useful. I have made some of those mistakes myself. That experience is part of what I bring now: practical judgment about what to build, what to defer, and how to get a real product to market without creating avoidable drag.

ArcherDX
Boulder, Colorado

Built and led the computational R&D organization behind a broad oncology portfolio.

I joined ArcherDX when it was an eight-person startup and helped build the computational and software foundation behind products spanning solid tumors, hematologic malignancies, liquid biopsy, immune repertoire, and companion diagnostics. Over time I led the R&D organization supporting product families including FusionPlex, VariantPlex, LiquidPlex, PCM, Immunoverse, and disease-specific panels across RUO, IVD, and LDT settings.

Invitae
Boulder, Colorado

Scaled the organization and carried products through commercialization.

I continued leading oncology software and bioinformatics through the ArcherDX acquisition and ultimately led a 70-person oncology software organization. The work spanned laboratory-developed tests, distributed research products, companion diagnostics, LIMS, bioinformatics, validation, and regulated product development across US, European, and Japanese pathways. PCM was one of the products I helped take from inception through launch, but it sat inside a much broader product and R&D portfolio.

Adela
Remote / Foster City, California

Built another product and another R&D organization from near-greenfield.

I helped take Guidepoint, a tissue-free liquid-biopsy MRD product, from inception to launch while building the surrounding software, data, scientific systems, and computational R&D organization needed to support it. I also helped bring a second product to its final commercial assay and algorithm configuration and built internal platforms used to develop, test, and learn from both.

Adela next generation
Assay, computation, software, and IP

Expanded beyond computation into the whole product system.

For the next-generation platform, I had a substantial role in assay architecture and wet-lab development as well as algorithms, data, and software. I also set patent strategy, worked with counsel, and authored core filings. That experience reinforced how tightly chemistry, computation, product decisions, team structure, regulatory evidence, and intellectual property are connected.

Regulatory experience

FDA and MolDX, including the hard lessons.

I have worked through FDA and MolDX submission efforts and seen firsthand how technically strong products can still run into problems when evidence strategy, validation, documentation, product scope, and regulatory expectations fall out of alignment. Some of those efforts did not succeed. I learned a lot from them.

What I learned

Regulatory thinking cannot be bolted on at the end. Assay design, software, provenance, validation, clinical evidence, and product claims need to stay aligned as the product evolves.

Why it matters for R&D

Teams move faster when downstream evidence and validation needs are considered early enough to prevent avoidable rework, rather than late enough to become a surprise.

Perspective

The failures are part of the value.

Successful launches are useful credentials. The harder-earned perspective comes from everything that nearly went wrong on the way there. I have lived through poor technology choices, premature scaling, brittle systems, overbuilding, under-testing, and organizational complexity that arrived before it was needed.

What I try to prevent

Building a platform before there is a workflow, hiring ahead of clarity, choosing architecture for imagined scale, automating a bad process, or mistaking technical sophistication for product progress.

What I try to enable

Small teams making clear decisions, simple systems that can evolve, disciplined testing, strong evidence, and technology that helps scientific and product talent get to market faster.

Intellectual property

Invention is part of product development.

I have helped shape invention capture and patent strategy, managed outside counsel, and contributed as a named inventor across three public US patent families spanning RNA technologies, ctDNA MRD, and integrated blood-based cancer detection methods.

Product + IP together

I do not treat patents as paperwork that happens after engineering. The interesting questions often sit at the boundary between assay design, algorithms, workflows, and product architecture.

Why it matters for AI

Agentic systems can expose new workflows, analyses, and scientific insights. Teams need to think about value creation, provenance, ownership, and invention at the same time they think about automation.