Bengaluru
I'm Gururaj.
Frontend engineer building developer platforms, design systems, and products people actually use.
- Working
- IBM Carbon Design System
- Building
- KnotCMS
- Learning
- Platform infrastructure
- Seeking
- Frontend platform roles
About
Systems, platforms, and craft.
I care about the systems behind the interface — shared components, documentation platforms, and tooling that makes other engineers faster. At IBM I work on Carbon Design System, the UI infrastructure thousands of developers depend on. Outside of that, I build KnotCMS end to end: a Cloudflare-based platform that keeps Notion content and Framer CMS in sync without manual work. I enjoy owning hard problems from architecture to polish.
Selected work
Where attention goes.
IBM Carbon Design System
Frontend Developer2024 — Present
Shared UI components, documentation infrastructure, and platform upgrades used across thousands of product teams — with a focus on reliability for tens of thousands of weekly NPM consumers.
KnotCMS
Founder & Engineer2026 — Present
A SaaS platform that automates Notion → Framer CMS synchronization. Event-driven architecture on Cloudflare Workers, with OAuth, billing, webhooks, and a self-service dashboard — owned from idea to production.
ReactNext.jsTypeScriptCloudflareDesign systemsWeb Components
Principles
Principles
- Software should feel invisible.
- Developer experience is a product.
- Build systems, not features.
- Ownership matters more than titles.
- Ship. Improve. Repeat.
Timeline
A few markers.
Building KnotCMS
Launched a production SaaS for Notion and Framer CMS sync.
IBM Carbon Design System
Joined India Software Labs to work on shared UI platform infrastructure.
Started building frontend professionally
Began at Wipro modernizing enterprise applications for Wells Fargo.
Outside work
Where curiosity goes.
01
Independent products
KnotCMS is how I practice full ownership — product, architecture, onboarding, billing, and launch — not just the frontend slice.
02
Design systems craft
I spend a lot of time thinking about component APIs, documentation platforms, and the invisible infrastructure that keeps product teams consistent.
03
Platform engineering
I'm deepening how serverless systems, webhooks, and developer tooling fit together — the layer that makes product surfaces possible.