Frontend Architect. I think about interfaces the way an architect thinks about buildings: structure first, finish second. Most of my work sits at the intersection of UI/UX and systems design, how a design language survives contact with a dozen teams, how a component API stays honest as a product scales, how the seams between micro-frontends disappear for the person actually using the product.

Lately that's pulled me into AI-augmented engineering too. I like building the tooling that lets a small team move like a much bigger one, without the codebase paying for it later.

At Deloitte USI I lead architecture on a federated platform (Webpack Module Federation) with a shared design-system library, a cross-MFE event bus, and spreadsheet-grade interactive widgets used across product teams.

A multi-agent pipeline with a dozen specialised LLM reviewers (security, performance, accessibility, test authenticity) running in parallel on every PR. Built on Claude Code and GitHub Copilot, wired into CI.

The org-wide component library used across every product team at Deloitte USI. API contracts, accessibility standards, versioning, and the docs that keep it usable.

A weekly high-protein, low-carb Indian meal planner. React Native, PHP, and Groq for the AI layer.

A personal finance tracker that reads bank SMS/statements and reconciles spend automatically, split across a mobile app, API, and scraper.

A bill-splitting app for groups. React Native up front, PHP API behind it.

Polls Indian retailers for PS5 restock by pincode and pushes a notification the second one's deliverable.

My portfolio, shivarya.dev, has the fuller picture: case studies, the rest of the project list, and how to reach me.

13 years in, across 5 companies. Before Deloitte, I led frontend architecture on a healthcare information platform (MediMention) serving doctors, nursing homes, and patients, a local business directory (CityPata), and a community platform (OmerSamaj). Those were the first professional projects I shipped start to finish as a lead, not just a contributor.

• A design system is a contract, not a component folder. If the API isn't honest, teams route around it, and now you have two design systems.
• Micro-frontend boundaries should be invisible to the user and obvious to the engineer. If either of those flips, something's wrong.
• Accessibility (WCAG) is a correctness requirement, not a checklist you run at the end.
• AI-assisted development is only worth it if it makes the codebase better, not just the sprint. Specialised reviewers beat one generalist model every time.

Certified: Azure Fundamentals, Azure AI Engineer, AZ-204 Developer Associate

📍 Bengaluru, India · shivarya.dev · contact@shivarya.dev · linkedin.com/in/shivarya

_{The best interfaces, like the best buildings, hide the work it took to make them feel inevitable.}