Harman
Sidhu
I build the internal libraries other teams depend on, the pipelines that get code to production, and the architecture that lets products scale safely.
I build the tools that
let teams ship faster.
Engineers led
Years shipping
Migration incidents
Internal libraries
I started as a frontend engineer and fell in love with building interfaces. But I kept asking “what happens on the other side?” — and never stopped pulling that thread.
Over the years I've grown from building UIs into a hybrid role that spans product engineering, internal platform tooling, and end-to-end delivery. I've designed internal libraries like FormGenerator and WizardBuilder that other teams adopt as standards. I've architected CI/CD pipelines on Azure DevOps, built microfrontend architectures with Vite and Next.js, managed infrastructure with Terraform and Kubernetes, and implemented OpenTelemetry observability — owning config-driven architectures that let teams ship features safely through feature flags.
Along the way, I've led teams of up to 23 developers, coordinated cross-functional rollouts, and mentored engineers through migrations and platform adoption. Leadership for me isn't a title — it's about creating the systems and documentation that help other people do their best work.
I hold an MS in Computer Science from Northeastern University, and today I'm pushing the boundaries of AI-augmented development — building MCPs and playbooks in Devin.AI that accelerate my team's daily workflows, working with Claude Code, driving accessibility standards, and shipping a cross-platform mobile app from scratch.
Career Timeline
View Full History →Full-time, hybrid (Boston, MA). Platform engineering across Kubernetes, Terraform, and Azure. Building microfrontend architectures with Vite and Next.js, implementing OpenTelemetry observability, and driving accessibility (a11y) standards.
Full-stack product + platform engineering. Owned internal libraries, CI/CD pipelines, auth flows, and Azure infrastructure. Built FormGenerator, WizardBuilder, and viewportWatcher. Managed migration across multiple React versions.
Frontend architecture and product delivery for enterprise SaaS. Led legacy Scala/Lift to React modernization across Redux, SASS/SCSS, and multiple React versions. Built feature gating systems, expanded into backend integration and Azure DevOps pipelines.
Web Development (CS 5610). Guided students through full-stack concepts and graded coursework.
What I work with.
Frontend
Backend & Integration
Platform & Delivery
AI & Automation
Testing & Quality: Jest, Vitest, accessibility (a11y) testing, Storybook, TDD, and JIRA-driven workflows for every feature I ship.
Leadership: Team leadership (up to 23 engineers), cross-team enablement, migration strategy, and technical documentation.
Currently Exploring
Building MCPs and playbooks in Devin.AI to accelerate team workflows. Internal developer portals and platform engineering patterns. RAG agent orchestration with n8n, Supabase, and OpenAI.
How I work.
Migrations, not rewrites.
I believe in incremental progress that ships safely. Big bang rewrites are a gamble — phased migrations are engineering.
Build for the next team.
The best code I write is the code that lets other engineers ship faster. Internal libraries, shared patterns, clear APIs.
Config-driven > hard-coded.
Feature flags, backend configuration, environment-aware behavior. Decouple deploys from releases. Always.
Own the full path.
Frontend to pipeline to production. Understanding the full delivery chain makes you a better engineer at every layer.
Lead through systems.
I’ve led teams of 8 to 23 engineers — not by managing calendars, but by creating the patterns and tooling that make coordination effortless.
Document as you build.
Structured technical docs, requirements-driven design, and clear rollout plans. If it’s not written down, it didn’t ship.
AI in My Workflow
I use AI as a force multiplier — not a replacement for engineering judgment. From code review acceleration to migration planning and CI/CD pipeline design, AI tools let me move faster while maintaining the architectural thinking that makes systems resilient.
The line I draw is clear: AI helps me explore solutions faster, but every decision about architecture, security, and team impact goes through human reasoning.
Have a project in mind?
Let's talk.
Always interested in thoughtful engineering challenges, platform problems, and building things that matter.