Correctness-first architecture
Service boundaries, APIs, data flow, idempotency, and state transitions that keep high-value product flows predictable.
Backend Systems · Distributed Systems · Reliability · Mentorship · IIT Hyderabad
I’m Vaibhav Garg. I work on distributed backend systems where correctness, reliability, and operational clarity matter. I care about simple contracts, visible failure modes, pragmatic technical decisions, and teams that can confidently own what they build.
About Me
I’m drawn to systems where correctness, failure handling, and human operability matter. Across commerce, customer engagement, healthcare, and resilient networks, the lesson has stayed the same: the hard part is rarely the code path that works.
My default approach is to turn ambiguity into clear contracts, observable behavior, defensible tradeoffs, and systems the next engineer can reason about without heroics.
Focus Areas
I’m most useful when correctness, scale, reliability, product constraints, and cross-team coordination need to move together.
Service boundaries, APIs, data flow, idempotency, and state transitions that keep high-value product flows predictable.
Failure-aware design, observability, rollout safety, debugging paths, and reducing ambiguity before incidents become customer pain.
Pragmatic tradeoffs, clear written reasoning, architecture reviews, and quality bars that help teams move faster with less rework.
Mentoring engineers through design reviews, debugging habits, ownership, communication, and the next step in their career trajectory.
Engineering Principles
The best systems are understandable before incidents, observable during incidents, and calm after they scale.
Strong systems expose failure modes, recovery paths, and ownership boundaries before the incident channel fills up.
Narrow interfaces reduce coordination cost and make migrations possible without dragging every team through the same decision.
Debuggability, observability, backfills, and rollout behavior are part of product quality, not cleanup work.
Good technical direction makes constraints, risks, and decisions easy for product, engineering, and operations teams to evaluate.
Experience
A backend systems path across reliability-critical products, distributed workflows, data contracts, customer-facing systems, and operational ownership.
Backend ownership in Uber’s order platform and commerce-processing layer, where the core responsibility is storing, managing, and serving order lifecycles across lines of business. The platform keeps order state and commerce context available so downstream consumers can process orders reliably and on time.
Backend leadership for the streaming and orchestration systems behind personalized mobile and web campaigns, where predictable latency and cost efficiency mattered as event volume grew.
Backend systems for healthcare workflows where reliability affected clinics, doctors, and patients directly. Focused on storage efficiency, workflow resilience, and offline-capable product behavior.
Operations platform for genomics and healthcare workflows. Built search, filtering, notification, and workflow systems used by hospital operations teams, and helped migrate the product experience to SPA architecture.
Graduate research in post-disaster ICT systems: networks and software designed for environments with limited infrastructure, unreliable connectivity, and real operational constraints.
Research
Graduate research on communication and information systems for post-disaster environments. Building networks that work without infrastructure sharpens how you think about failure.
IEEE WiMob · Wireless and mobile computing · Oct 2015 · pp. 125-131.
View paperICNS · Networking and services · May 2015 · pp. 17-23.
View paperIEEE Region 10 Humanitarian Technology Conference · Aug 2014 · pp. 58-63.
View paperContact
LinkedIn is the best starting point. GitHub has code. Codementor is where I mentor engineers on backend systems and architecture.