headshot

Hello,
I am
Bhanu

Based in
Toronto, ON


(GMT-5)

Currently working in
Fintech

Thoughtful architecture. Beautiful interfaces.
Engineered to perform. Built to evolve.

  • React
  • TypeScript
  • Next.js
  • Redux
  • Tailwind CSS
  • C#
  • .NET
  • AG Grid
  • Docker
  • AWS
  • Azure
  • Design Systems
  • Real-Time Applications
  • GraphQL
  • WebSockets
  • CI/CD
  • AI-assisted Development

Built to show how I
think.

01 / SHOWCASE

BEYOND THE BUILDTHE DECISIONS BEHIND IT.

01 / 03
Frontend · Real-time trading Application

Pulse

Real-time trading workspace for dense market data, live updates, and long-session enterprise workflows. Built with WebSocket streams, AG Grid transactions, row-level change flashes, compact panels, watchlists, instrument details, and structured client state. Designed for interfaces where speed, clarity, and information density need to work together.

Intent
Built to explore real-time trading workflows
Focus
Dense market data, live updates, speed, clarity, usability, trader workflows
Craft
WebSockets, AG Grid, data-change flashes, performance tuning, compact layouts
  • React
  • TypeScript
  • Vite
  • Tailwind CSS
  • AG Grid
  • Redux Toolkit
  • WebSockets
  • Vercel
Open the live Pulse site in a new tab
02 / 03
Frontend · Enterprise design system

Atlas

Enterprise design system playground for reusable UI foundations, shared patterns, and developer-friendly component APIs. Built with design tokens, themes, accessible primitives, variant patterns, documentation, and implementation notes. Designed to keep enterprise applications consistent, extensible, and easy for developers to adopt without making every product feel custom-built from scratch.

Intent
Built as an enterprise design system foundation
Focus
Reusable Components, Design tokens, theming, accessibility
Craft
Accessible primitives, variant systems, semantic tokens, UI governance
  • React
  • TypeScript
  • Vite
  • Tailwind CSS
  • shadcn/ui
  • Radix UI
  • Design Tokens
  • Vercel
Open the live Atlas site in a new tab
03 / 03
Frontend · Architecture decisions

Decisions

Architecture workspace for the decisions behind scalable React systems. Covers state ownership, abstraction, rendering performance, component APIs, and the moments where simple patterns beat heavier architecture. Built with decision cards, review notes, and then-vs-now examples to make frontend judgment visible.

Intent
Built to show frontend architecture judgment
Focus
Trade-offs across state, performance, and abstraction
Craft
Decision cards, review notes, then-vs-now examples
  • React
  • TypeScript
  • Vite
  • Tailwind CSS
  • shadcn/ui
  • Framer Motion
  • Architecture Notes
  • Vercel
Open the live Decisions site in a new tab

The Toolkit,
curated.

02 / TOOLKIT

THE TOOLSBEHIND THE THINKING.

Frontend Engineering

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • HTML5
  • CSS3
  • Tailwind CSS
  • Material UI
  • Sass

Architecture & Design Systems

  • Component Architecture
  • Design Systems
  • Design Tokens
  • Reusable Components
  • Stencil.js
  • AG Grid
  • React FlexLayout
  • Framer Motion

Data & Integration

  • GraphQL
  • Apollo Client
  • REST APIs
  • Redux
  • TanStack Query
  • WebSockets
  • SignalR

Performance, Testing & Quality

  • Rendering Optimization
  • Virtualization
  • Memoization
  • Lazy Loading
  • Jest
  • Vitest
  • Cypress
  • Playwright
  • Storybook

Cloud

  • Azure
  • AWS
  • Vercel
  • Supabase
  • Firebase

DevOps

  • Azure DevOps
  • Docker
  • Git
  • GitHub
  • GitHub Actions

Identity, Security & Observability

  • OAuth 2.0
  • OpenID Connect (OIDC)
  • JWT
  • Single Sign-On (SSO)
  • OpenTelemetry

AI & Developer Productivity

  • Claude Code
  • Cursor
  • GitHub Copilot
  • OpenRouter
  • Claude API
  • Prompt Engineering
  • Agentic Workflows

Mobile

  • React Native
  • Capacitor
  • Ionic
  • Progressive Web Apps (PWA)

Forms & Validation

  • React Hook Form
  • Zod
  • Formik
  • Yup

Databases & Backend Technologies

  • Node.js
  • C#
  • .NET
  • MongoDB
  • PostgreSQL
  • Snowflake

Technical Leadership

  • Technical Direction
  • Architecture Reviews
  • Engineering Standards
  • Mentoring
  • Cross-functional Collaboration

The curious
mind.

03 / ABOUT

THE PERSONBEHIND THE WORK.

I've always enjoyed software that feels effortless to use. The kind where every interaction feels natural, every detail has a purpose, and users never have to stop and think about the interface. That's what drew me to frontend engineering, where thoughtful technical decisions quietly shape every experience.

The way I build reflects the same mindset. I prefer familiar patterns over unnecessary novelty, clean architecture over quick fixes, and automation over repetitive work. I care about software that's easy to use, easy to maintain, and built to evolve. Good engineering isn't just about shipping features. It's about making the next decision easier than the last.

Curiosity has always been the constant. Whether I'm exploring the latest browser capabilities, experimenting with AI, travelling, playing music, or building smart home projects, I'm usually learning how something works and thinking about how it could be made better.

Expertise

  • Web Applications
  • Mobile Applications
  • UI Engineering
  • Frontend Architecture
  • Design Systems
  • Systems Integration
  • Cloud Services

Education

  • BSc · Computer Science

    York University

    Toronto, Canada

Experience

  • 12+Years building software
  • 20+Enterprise applications
  • 10+Engineering teams
  • Fixed IncomeCapital markets
  • Real-timeTrading platforms
  1. P-01

    Bring structure

    I’m most valuable when complexity starts slowing a team down. I take ownership, establish clear boundaries, simplify the problem, and create a path from uncertainty to delivery.

  2. P-02

    Understand before building

    Delivery matters, but the right solution matters more. I understand the problem before committing to an approach.

  3. P-03

    Engineer what matters

    I use proven solutions where they work and go custom where they add real value. Complexity has to earn its place.

  4. P-04

    Go beyond the requirement

    Meeting the requirement is the baseline. I look for the extra improvement that makes the product noticeably better.

  5. P-05

    Build for change

    Requirements change. Teams change. I build software that’s straightforward for others to extend, maintain, and own.

  6. P-06

    Stay ahead, selectively

    I stay close to where frontend is going and adopt modern technology when it gives the product a meaningful advantage.

04 / Get in touch

Let's build something
together —
hello@bhanu.ca