Kesean Woodhouse

Software Engineer · Solutions Implementation, Cloud & API Integrations

I build and integrate the systems that connect engineering teams to the customers, analysts, and stakeholders downstream of them.

About

Six years across Microsoft and Stripe building backend systems, data pipelines, and integrations — most recently on Microsoft's cloud security team, where I built Azure ingestion pipelines, automated risk management tooling, and production monitoring for a small team of internal analysts. Earlier at Microsoft, I shipped C#/XAML features for the Tips app on 1B+ Windows devices.

I started in tech retail at Microsoft's flagship NYC store before transitioning to engineering, and that customer-first lens has shown up in every role since. My strongest work has lived in the connective tissue between systems — pipelines that make things talk to each other, integrations that get used, tooling that takes manual work off engineers' plates. I'm comfortable across C#, Python, JavaScript/TypeScript, and modern cloud platforms (Azure, Vercel, Railway).

Currently wrapping a self-directed period focused on rebuilding fluency with modern AI tooling and full-stack production deployment. Open to remote and hybrid roles in the Seattle area. You can also see this story compressed onto a single page → Resume

Projects

A full-stack developer support chatbot, built as a learning project.

Python Flask React TypeScript Clerk Convex Qdrant Voyage AI Redis Railway Vercel GitHub Actions Playwright

After two years away from full-time engineering work, I needed a project that would force me back into the rhythm of shipping — and force me to learn the modern infrastructure I hadn't touched yet. Golem is the result.

It's a developer support chatbot that answers technical questions in a structured format: summary, root cause, debug steps, and relevant docs. Users sign in, ask questions, and get streaming responses. History is saved per-user. Under the hood, it pulls relevant documentation chunks from a vector store before generating each response.

The tech: Python/Flask backend, React/TypeScript frontend, Clerk for auth, Convex for the database, Qdrant for vector search, Voyage AI for embeddings, Redis for rate limiting, Railway for the API, Vercel for the frontend, GitHub Actions for CI, and Playwright for end-to-end tests.

Most of the production-grade pieces were tools I'd never used. The point wasn't to ship a product, it was to get my hands back on modern tooling after time away.