Senior product engineer. AI-native products and agentic workflows.

• RepoKernel + engram2026 – PresentSolo, open source, in daily useRead case

  Agent tooling that keeps agents honest.

  Coding agents share a repo but not a memory. Run more than one and they lose track of state between tasks, edit outside their intended scope, and can double-claim the same unit of work. And every agent forgets everything between sessions, unless you let a tool auto-write whatever it likes about you, sensitive details included.

  RepoKernel current release, published on npm

  v1.33.x

  the whole task lifecycle, CLI-only state writes

  7 verbs

  of sensitive memory that never auto-write in engram

  6 kinds

• Confidential client2025 – PresentOngoing · Shared platform librariesRead case

  Cross-microfrontend style leaks, eliminated.

  Independently deployed microfrontends shared one page, so one team's CSS could reach another team's UI, and services kept re-describing the same payload shapes by hand.

  commits to the shared component library

  108+

  prefixed selectors plus token variables, isolation by construction

  2 layers

  cross-microfrontend style leaks after the isolation rollout

  0

• Sunflower Games2025 – 20267 months · concurrent engagementRead case

  Roulette mini-game, missions, and ops tooling.

  Ops and gameplay teams needed better tools while a live dual-currency economy kept moving underneath them.

  commits across four repos in seven months

  294

  architecture iterations before the chip-identity model held

  3

  admin, game UI, and two Node services in one delivery path

  4 repos

• FeatherShark2023 – 202420 months · 2-person teamRead case

  Live govtech migration, no release gaps.

  The app needed a new frontend foundation, but municipal users depended on weekly releases that could not pause.

  migrations on a live product: runtime, language, data, forms, tooling

  5

  commits as sole frontend owner over 20 months

  456

  release gaps across all five migrations

  0

• MongoDB2023 – 202418 months · concurrent engagementRead case

  Design-system fixes on mongodb.com.

  High-traffic marketing pages needed library improvements, but dozens of consumers depended on those packages.

  the fetchPriority change that moved LCP on the top landing pages

  2 lines

  incidents migrating hundreds of marketing forms

  0

  package layers released in sequence, no consumer broke

  3

• Platform92018 – 20234+ yearsRead case

  Shared UI for a private-cloud console.

  The console needed reusable UI building blocks and a predictable way to cache and persist server data, instead of components and fetch logic re-solved case by case.

  one product, one console, one component set

  4+ years

  build migrated, HMR and config simplified

  Webpack → Vite

  server data deduped and persisted across refreshes

  Cached

Where AI already sits inside shipped systems: client delivery, a production feature from 2023, and the tooling I maintain.

• 01

  Agent workflows

  Multi-step workflows where an agent reads context, proposes actions, calls tools, and waits for approval before changing anything that matters.

  Running in client delivery and in RepoKernel review gates

• 02

  Context engineering

  Project rules, reusable instructions, decision records, and memory structured so coding agents follow the codebase instead of guessing.

  Applied on live client work: rule files restructured, docs lazy-loaded

• 03

  Human-in-the-loop UX

  Review, approval, fallback, and correction flows so AI output stays useful, traceable, and safe to ship.

  Shipped 2023: AI-assisted inspection drafting with human review before save

• 01

  Architecture before components

  I map data flow, state ownership, and failure paths before the first component lands. On the multi-team web platform of a listed multinational that meant a two-layer CSS isolation system, prefixed selectors plus design-token variables, which removed cross-microfrontend style leaks as a class of bug.

• 02

  Frontend craft at production scale

  Interaction detail, Core Web Vitals, accessibility, loading states, and the edge cases users find first. On mongodb.com a two-line fetchPriority change produced an LCP win on the highest-traffic landing pages.

• 03

  Product judgment

  I work from vague requirements and argue for the version users actually need. On a govtech product that meant moving tenant configuration out of build-time env files, so onboarding a new fire department became a settings change instead of a redeploy.

• 04

  Codebases teams can live with

  Typed boundaries, migrations that never freeze feature work, and CI that catches regressions before main. 456 commits over 20 months as the sole frontend engineer on a two-person team, across five migrations on a product that never stopped shipping.