Skip to content
Rahul Nainala

Open to workHyderabad or Bengaluru, hybrid or on-site

Rahul Nainala

Frontend Lead & Full-Stack Engineer at Quantum AI Global

4+ years full-time. I build the whole path a request takes: the interface, the APIs, the data, the containers and the machines underneath.

ResumeSee the work GitHub (opens in a new tab)LinkedIn (opens in a new tab)
[email protected]
years full-time
4+
products shipped from one codebase
3
teams moved off a monolith
4
faster CI builds after moving to Vite
~40%
WealthPilot's overview: total value, risk figures, open issues, allocation and goals for the fictional demo portfolio

On my own · 2026

WealthPilot

99%line coverage on the analytics engine

Selected work

Things I've shipped, and the number that moved.

All 15 projects

Quantum AI Global · 2025–now

Quantum Computing Platform

3products shipped from one codebase

Problem
Three kinds of customers, one codebase to keep sane.
Built
Shared core, hardware execution, licensing and billing, edge appliance.
Result
3 distributions · 50 concurrent students
Next.js · React · Python · FastAPI

On my own · 2026

Building

GymTracker

40+screens across training, nutrition and progress

React Native · Expo · TypeScript

Also at work

Experience

4+ years, one layer deeper each time.

Quantum AI GlobalFrontend Lead & Full-Stack EngineerDec 2025 – Present

The whole platform, down to the hardware

  • Designed one core codebase that ships as three products (Cloud, Academia and a Raspberry Pi edge appliance) instead of three forks. Extracted a shared core layer across 4 backend services and deleted ~3,000 lines of duplicated code.
  • Shipped real quantum hardware execution on IBM Quantum as async submit/poll that never submits a job twice, plus a CUDA-Q error-correction composer, a noise composer and tensor-network simulation.
  • Built identity, licensing and billing end to end: product catalog, per-product licenses with feature bits, org plans, org-scoped API keys and Razorpay checkout with autopay.
  • Delivered the edge appliance on real Raspberry Pi hardware, a GPU dev server, self-hosted CI on GHCR, Redis rate limiting across replicas, 3-tier staging and Helm charts for GPU node pools. Scaled to 50 concurrent students.
  • Hardened auth and CORS across 4 services and added secret scanning to CI.

Next.js · React · TypeScript · Python · FastAPI · PostgreSQL · Redis · Docker · Helm · CUDA-Q

Rubus Digital Pvt. Ltd.Software Engineer IIJun 2024 – Nov 2025

Frontend architecture across four teams

  • Led a monolith-to-micro-frontend migration across 4 product teams with Webpack 5 Module Federation, cutting deployment complexity by 40%.
  • Built a CLI that scaffolds a new micro-frontend (ports, boilerplate, Docker Compose) in under 30 seconds, taking new-team onboarding from 2 days to 15 minutes.
  • Built a Three.js 3D dashboard with live IoT data overlays across 3D asset models, rendering in under 2s at 1080p.
  • Designed a JSON-schema configuration system so non-engineers could configure 3D models, cutting developer dependency by 60%.
  • Migrated the codebase from JavaScript to TypeScript and raised Jest coverage to 75%.

React · TypeScript · Three.js · Webpack 5 · Module Federation · Docker · Jest

Casp AISenior Software Engineer (Contract)Jul 2023 – Jun 2024

Product UI and the build pipeline

  • Built the real-time AI chat UI in React + Tailwind: streaming token-by-token responses with optimistic state, abortable in-flight requests and retry on socket drops.
  • Migrated the team's build pipeline to Vite, cutting CI builds from ~8 min to under 5 min (~40% faster).
  • Refactored the legacy chat frontend into a modular component system: message bubbles, a streaming renderer, tool-call cards and the prompt input.
  • Integrated the chat frontend with FastAPI services.

React · Tailwind CSS · Vite · TypeScript · FastAPI

Hexagon Capability Center IndiaSoftware EngineerJun 2022 – Jul 2023

Dashboards and the API contract behind them

  • Built interactive React dashboards for engineering teams processing 10K+ data points, reducing render load time by 30%.
  • Owned the React–C# microservices integration contract, redesigning REST payloads and resolving alignment gaps that had been blocking two product teams.
  • Established the frontend testing standard and code-review bar for the dashboards group, cutting production defects by 20%.
  • Identified and fixed N+1 query issues in backend workflows, improving API response time by 40%.

React · Angular · C# · REST APIs · PostgreSQL

Hexagon Capability Center IndiaSoftware Engineer InternOct 2021 – Jun 2022

An ML model and the UI around it

  • Built and trained a TensorFlow model to detect symbols in P&ID engineering diagrams.
  • Developed a web UI for model inference and result visualization.
  • Authored technical documentation for the model deployment pipeline.

Python · TensorFlow · OpenCV

How I build

From the button to the box.

Every layer a request crosses, each backed by something I shipped.

One request · illustrative

POST/orgs/:id/upgrade

A plan upgrade passing through the interface, the API, the data layer and a background worker on the cluster in 212 ms.

  1. L1Interface

    Frontend architecture that lets several teams ship without stepping on each other.

    • click “Upgrade” web212 ms
    • server action next198 ms

  2. L2API

    Services and contracts that other teams can build on.

    • rate limit redis5 ms
    • auth + org scope api14 ms
    • check feature bits licensing12 ms

  3. L3Data

    Queries and shared state that hold up under replicas.

    • insert order postgres22 ms
    • create subscription payments94 ms
    • enqueue provision queue4 ms

  4. L5Cluster

    Deployments with a staging step and room to scale.

    • grant license worker26 ms
    • render receipt web8 ms

  1. L1Interface

    Next.js · React · TypeScript · Three.js

    Frontend architecture that lets several teams ship without stepping on each other.

    • Led a monolith-to-micro-frontend migration across 4 teams on Webpack 5 Module Federation
    • Streaming chat UI: token-by-token responses, abortable requests, retry on socket drops
    Micro-Frontend Platform MigrationRubus Digital · 2024–25

  2. L2API

    FastAPI · Node.js · REST · WebSockets

    Services and contracts that other teams can build on.

    • Identity, licensing and billing end to end: catalog, per-product licenses with feature bits, org-scoped API keys, checkout with autopay
    • Owned the React–C# REST contract that had been blocking two product teams
    Quantum Computing PlatformQuantum AI Global · 2025–now

  3. L3Data

    PostgreSQL · Redis · SQLite

    Queries and shared state that hold up under replicas.

    • Fixed N+1 queries in backend workflows: API response time down 40%
    • Redis rate limiting that holds across API replicas
    Engineering DashboardsHexagon · 2022–23

  4. L4Delivery

    Docker · GitHub Actions (self‑hosted) · GHCR

    Pipelines that make shipping routine.

    • Self-hosted CI building container images to GHCR
    • Secret scanning added to CI
    Streaming AI ChatCasp AI · 2023–24

  5. L5Cluster

    Kubernetes · Helm · staging

    Deployments with a staging step and room to scale.

    • Helm charts for GPU node pools
    • 3-tier staging before production
    Quantum Computing PlatformQuantum AI Global · 2025–now

  6. L6Hardware

    GPU servers · Raspberry Pi · Linux

    The machines at the bottom of the stack, including ones without a network.

    • Edge appliance delivered and verified on real Raspberry Pi hardware
    • GPU dev server
    Quantum Computing PlatformQuantum AI Global · 2025–now
Delivery · commit → prodillustrative · anonymized
  1. commit

    main · PR

  2. checks

    lint · tests · gitleaks

  3. build

    docker image

  4. registry

    ghcr

  5. staging

    3-tier

  6. prod

    helm upgrade

Engineering notes

Trade-offs I'd make again.

Decisions

  1. 01

    Configuration over forks

    One core with per-distribution config.

    cost · More design up front; every fix ships everywhere at once.

  2. 02

    No retries on paid hardware jobs

    Simulators retry freely. Hardware jobs submit once, poll, and fail safe to the user.

    cost · A failure needs a human click; a duplicate paid run can't happen.

  3. 03

    Licenses as feature bits

    Every service checks the same bits.

    cost · A shared contract to maintain; no special-case code per plan.

● IncidentGymTracker · own project

Failed queries that looked like an empty history

  1. symptom

    A user's workout history rendered as empty.

  2. cause

    A column the app queried was missing from the database. The query failed, and the failure rendered as an empty state.

  3. fix

    Wrote a schema-drift script that lists every table.column the app queries, so drift is caught before it ships.

  4. lesson

    An error must never look like an empty result.

Contact

Hiring for a senior full‑stack role? Let's talk.

I'm looking for Senior Full-Stack / Senior Software Engineer roles in Hyderabad or Bengaluru, hybrid or on-site. Happy to talk about side projects any time.

Email me ResumeOpen to work
POST/hireexample request
{  "role": "Senior Full-Stack / Senior Software Engineer",  "where": ["Hyderabad", "Bengaluru"],  "mode": "hybrid or on-site",  "stack": ["React", "Next.js", "TypeScript", "Python", "FastAPI", "PostgreSQL"]}
200 OK · reply by emailHyderabad · --:-- IST
[email protected]

learning · off the clock

  • Kubernetes CKA (in progress)

    Building on the Helm charts for GPU node pools I shipped at work

  • Designing Data-Intensive Applications

    Working through Kleppmann: replication, partitioning, consensus

education

B.Tech, Computer Science & Engineering · Lovely Professional University, Aug 2018 – Jul 2022