Brian Cheruiyot
I also go by Bryce Cee. I build interfaces for people and tools for engineers.
Frontend roots, platform perspective
I started in product engineering, building web applications across teams in Kenya, South Africa, and Europe. My work includes OfColor's new-user onboarding and an offline-first, multi-tenant education PWA for teachers and caregivers.
For that PWA, I owned frontend flows for attendance, class planning, and student performance and progress across age groups. I extended themed tenant variants and managed offline client state with Redux Toolkit, including a user-facing upload control and real-time synchronization while online.
I joined Microsoft in 2021 and became a Software Engineer II in April 2024. My developer-platform work includes CI reliability, build tooling, test migrations, and AI-assisted engineering workflows in a large JavaScript monorepo.
Two connected interests
I led a Jest-to-Vitest pilot, moved post-build work into a dependency-aware graph, and owned an AI-assisted semver feature from design through implementation, testing, and validation. I also reduced a developer MCP server's tool surface and created a reusable dependency-remediation workflow that I shared at an internal engineering workshop.
Outside Microsoft, I build independent products. RareDraw is a card-game platform I own and build personally. Finexapp, DevKit, and Travel FX explore other practical problems, from personal finance to small developer tasks and offline currency conversion.
My public ts-semver-detector project is a separate, work-in-progress static-analysis experiment. It helped me learn to use AI when developing larger codebases; it was not the production implementation of the Microsoft semver feature.
Clear boundaries, useful evidence
I also write about agent tooling and evaluation. I value explanations that make a technical decision inspectable: what the system needs to do, where responsibility belongs, and how to check the result.
Microsoft work is described through reviewed summaries and approved aggregate outcomes. Internal artifacts stay private. Public projects link to their available implementations, and work in progress is labeled as such.