01
Shaping mabl for agent-driven software development
I help lead mabl’s evolution from traditional test automation toward a product built for a world where more software is created and changed by agents.
Read case study →Krista Rose King
Put me close to the problem, surrounded by good people.
Most of what I know about a product I picked up on customer calls, in support threads, or by breaking something myself. I like working through those problems with coworkers I trust, and we usually have fun doing it. I move fast when someone is stuck and slow down when a decision deserves it. And when the same problem keeps showing up, I build automation to catch it so nobody has to waste their noggin energy on it again.
Selected work
02
Taking mobile testing from 0 to 1
I led mobile testing from early customer discovery through product definition, design, pricing inputs, launch planning, and release. It grew to roughly $1M in revenue in its first year.
Read case study →03
Automating product operations as shipping velocity scaled
As agentic development increased shipping velocity and PM bandwidth stayed thin, I built connected systems for prioritizing customer issues, turning scattered signal into backlog decisions, and pushing what shipped back to customer-facing teams.
Read case study →Little noggin nuggets
Who checks the work when software starts writing more software?
Coding agents can move quickly, but speed does not answer the harder question: did the change actually do what it was supposed to do?
Read the excerpt →What changes when the market moves faster than your planning cycle?
When assumptions keep moving, the plan has to separate the outcomes that should stay stable from the bets that should be easy to change.
Read the excerpt →Better tools still need good product design
More capable systems still need clear states, useful constraints, understandable recovery paths, and deliberate places for people to stay in control.
Read the excerpt →Changing a mature product without breaking what already works
Evolving an established product means making room for the new model without forcing existing customers to absorb all of the disruption at once.
Read the excerpt →About
I started in civil engineering, moved through UX and quality engineering, and eventually landed in product. That path made me pretty systems-oriented: I like understanding how things work, finding the real problem underneath the obvious one, and working closely with technical teams.
Currently I’m at mabl, working on software quality, developer workflows, and what changes as more software gets built by agents. I care about good product judgment, strong engineering partnerships, and useful products without a lot of jargon.