Joshua Tscheschlog

Shared systems / product platforms / developer tooling

I build shared systems that make product teams faster.

I work across product platforms, design systems, and internal tools, with a focus on reducing complexity and increasing leverage.

Currently Staff Software Engineer at KBRA, working across product platforms, design systems, and internal tooling.

Platform ownership

Owned platform architecture and delivery for KBRA Financial Intelligence across product, search, and supporting systems.

Design systems as infrastructure

Built shared token and component foundations that reduced repeated frontend decisions across teams.

Developer tooling

Shipped internal AI-tooling workflows, including a versioned CLI for reusable prompt and skill customizations.

Selected contexts

  • Financial intelligence platform architecture
  • Organization-wide design system stewardship
  • Internal AI tooling and developer workflows
  • Frontend, backend, search, infra, and delivery systems

Recent scope

Platform delivery, design system stewardship, senior-level interviewing, retrospectives, and internal AI-tooling work across KBRA Technology.

Featured projects

Proof, not a project grid

Compact previews of the work I would want an interviewer to read first.

Internal developer tooling

KBRA AI Tooling CLI

An internal CLI that turned shared AI workflow assets from informal file-sharing into a governed, low-friction distribution model.

I treated the problem as distribution into real developer environments, not just storage in a shared repository. That decision drove the product shape: `npx`, editor agnosticism, guided discovery, reviewed package releases, and later lifecycle improvements.

  • Released to KBRA Technology in February 2026
  • Regular contributions from 5 engineers across the org
Read case study

Platform architecture and delivery

KBRA Financial Intelligence

Platform ownership across KFI's application architecture, delivery model, and search/data systems that made a complex product easier to build and ship.

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.

  • 10,000+ banks and credit unions in product scope
  • 40M+ records loaded during off-hours
Read case study

Shared UI systems

Design System Infrastructure

A token-first design system that treated shared UI decisions as delivery infrastructure rather than visual polish.

The most important decision was to treat adoption as part of the architecture. Tokens became the low-friction entry point that reduced repeated decisions without forcing teams to abandon their preferred frameworks or component libraries.

  • Style Dictionary pipeline with multi-target outputs
  • Roughly halved average frontend complexity across the organization
Read case study

How I work

Applied engineering heuristics

A few heuristics that shape how I approach product platforms, shared UI systems, and internal tooling.

I use shared systems to remove repeated decisions.

I treat design systems as product infrastructure, not decoration.

I prefer tools that increase team leverage over local cleverness.