Full-stack engineer

Hi, I'm Kate.I build AI features, and the workflows my agents run on.

Most of my work is analytics and operations software in Next.js, React, and TypeScript. These days that includes AI features like LLM pipelines and MCP servers. I write code through Claude Code, with my own skills, evals, and verification checks.

Selected work

Real products built for real constraints.

A few projects that show how I work across analytics depth, operational speed, and trust-heavy customer experiences.

StoreHero preview

Ecommerce analytics

StoreHero

Multi-tenant analytics for profitability, LTV, and marketing decisions.

Customer-facing analytics, AI-assisted insights, an MCP server for merchant AI clients, and internal tooling across integrations, exports, and complex workflows.

Next.jsReactTypeScriptPrismaPostgreSQLDynamoDBAWSMUI
Visit project
Matics preview

Manufacturing operations

Matics

Real-time platform for factory-floor planning, monitoring, and response.

High-density dashboards and workflow surfaces built to stay legible in fast-moving factory environments.

ReactTypeScriptRedux ToolkitHighchartsReact Flowi18nextPWA
Visit project
teach preview

AI math tutoring · side project

teach

Turns one homework problem into a short lesson a child solves on their own.

A parent photographs or types a math exercise. The app recognizes it, generates a worksheet, has a second model review it, and sends the child a link once the parent approves.

Next.jsReactTypeScriptSupabaseKyselyVercel AI Gateway
Visit project
bekiPay / Sikoba preview

Fintech mobile product

bekiPay / Sikoba

Local currency and IOU platform built for community-scale financial trust.

bekiPay enables local currency payments in Luxembourg; Sikoba handles peer IOU tracking with automated clearing — both built on a shared React Native foundation.

React NativeTypeScriptReduxReact Navigationbitcoinjs-libi18nextJest
Visit project

How I work

A delivery style built for collaboration and difficult product surfaces.

01

Start with the working surface

I map the decisions a screen needs to support before thinking about polish, so the interface earns its complexity instead of hiding it.

02

Own the full slice

From data shape to UI states, I follow the whole path so integration issues get solved early and the product feels coherent.

03

Ship in meaningful increments

I prefer small, working milestones that create feedback loops quickly instead of long stretches of hidden progress.

04

Keep collaboration visible

Good async notes, explicit trade-offs, and honest status updates are part of the delivery work, not extra admin around it.