The working arc
From an unclear problem to a system a team can keep evolving.
I stay with the work as it changes shape—from intent and interaction to architecture, release, and the habits a team carries forward.
- 01
Orient
Clarify the real problem.
I work with product and design to surface the intent, challenge assumptions early, and keep the work grounded in what people actually need.
- 02
Shape
Make the product legible.
I turn that intent into coherent flows, resolve the details that make an interaction understandable, and stay with them through release.
- 03
Build
Create room for change.
I use clear boundaries, reusable components, and focused tests so the frontend can evolve without becoming harder to reason about.
- 04
Multiply
Leave the team stronger.
I turn what we learn into conventions, tools, and shared context so the improvement outlasts the project—and any one engineer.
The proof is in the trajectory
Over time
The StackRox years
One product across startup, acquisition, and open source. The scope grew; staying close to users and implementation remained constant.
- August 2015
I join StackRox as its first UI engineer
I help a small founding team turn an early prototype into the product that defines the company.
- 2016–2020
The product and team grow
I build across the platform, help grow the UI team, and establish the patterns and conventions that let us take on a much larger product surface.
- January 2021
Acquired by Red Hat
StackRox becomes the foundation of Red Hat Advanced Cluster Security.
- May 2021
The platform goes open source
The codebase I helped grow becomes public at github.com/stackrox/stackrox.
- Today
Principal engineer, still close to the product
I lead complex product work, evolve the frontend architecture, and help the team develop better ways of building together.