Staff-level engineering across platforms, design systems, and internal tooling
I turn shared systems into team leverage.
I lead the platform, design-system, and internal-tooling work that removes delivery friction, reduces repeated decisions, and makes product teams faster.
Currently Staff Software Engineer at KBRA, working across product platforms, design systems, and internal tooling.
Operational credibility
- Platform architecture across product, APIs, search, and delivery systems
- 10,000+ banks and credit unions in KFI product scope
- 40M+ records loaded during off-hours through supporting data pipelines
- Organization-wide design-system stewardship and internal tooling adoption
Operating doctrine
My principles for leverage-focused software development
The operating patterns behind the platform, design-system, and tooling work shown above.
Remove repeated decisions by turning them into shared systems.
Treat design systems as delivery infrastructure, not visual garnish.
Build tools that change how teams ship, not just how one engineer works.
Case studies
Proven impact on product development
Case studies that show how I use shared systems to change delivery speed, implementation cost, and team leverage.
Platform architecture and delivery
KBRA Financial Intelligence
The through-line in this work was product-enabling platform ownership. I worked on the shared foundations that reduced delivery friction, modernized an aging application stack, and enabled richer capabilities like screeners and report-building.
Platform ownership across KFI's application architecture, delivery model, and search/data systems that made a complex product easier to build and ship.
- 10,000+ banks and credit unions in product scope
- 40M+ records loaded during off-hours
Shared UI systems
Design System Infrastructure
I served as the de facto engineering lead for a volunteer-run system where adoption was the primary architectural goal. Tokens became the low-friction entry point that reduced repeated decisions across a highly fragmented frontend environment.
A token-first design system that treated shared UI decisions as delivery infrastructure rather than visual polish.
- 10 teams onboarded and ~30 projects adopted at the token level
- 220+ releases shipped over 3 years with 2 major version bumps
Internal developer tooling
KBRA AI Tooling CLI
I treated the problem as governed distribution into real developer environments, not just storage in a shared repository. That decision drove the product shape: `npx` and zero-setup adoption, editor agnosticism, a progressive-disclosure UX, and reviewed package releases.
An internal CLI that turned shared AI workflow assets from informal file-sharing into a governed, low-friction distribution model.
- Released to KBRA Technology in February 2026
- Regular contributions from 5 engineers across the org
Sole frontend ownership
Klezma MVP
I served as the sole frontend engineer from concept through MVP, building a custom managed-wallet settlement system that abstracted all blockchain friction while maintaining a high-polish interface recognized by NFTHack 2022.
End-to-end Next.js architecture and "Grandma-proof" onboarding for a Web3 creator platform.
- Sole frontend engineer from concept through MVP launch
- NFTHack 2022 Winner