17+ years building products and teams
ENGINEERING
LEADER
$ anoop --status building ✓ learning ✓ curious ✓ still figuring it out
Building customer-facing products and the teams behind them — from writing the code myself to scaling an engineering org 3x. Lately, back to shipping hands-on: the tools below are what I've been building on the side.
Focus areas
Journey
- 2008Engineer — Started building customer-facing products.
- 2012Senior Engineer — Built and delivered enterprise platforms.
- 2019Frontend Architect — Started owning system-level technical decisions.
- 2022Engineering Leadership — Moved from systems to teams.
- 2024Director — Scaled engineering from 20 → 65+.
- 2025Builder again — Returned to building, end to end.
Building now
I stepped back into hands-on development to build things I wanted to understand — and to see what modern AI-assisted development feels like from the builder's side.
- hueglintnpm
Accessible-by-default heatmap library — color scales that hold contrast and colorblind-safety from the start.
- ladderlineCLI
Local-first CLI for engineering managers — 1:1 notes and career-ladder tracking, no dashboard required.
- trailvinenpm
Draws a curved SVG route through a set of milestones — a framework-agnostic core, with thin bindings for React and vanilla JS.
Recent writing
All posts →- When the org chart gets in the way of shipping — A production-critical project needed to ship in a week. The team that could deliver it didn't belong to one team.
- Sometimes the best architecture decision is a hiring decision — The Angular-to-React decision wasn't really about which framework was better.
- 0→1 needs a different operating system — What worked when we were trying to prove a product didn't always work once there was a product, a team, and customers depending on it.