Ahmedabad, IST Remote

Backend Cloud AI Systems Reliability

I build LLM pipelines and event-driven backends that hold up when the load arrives all at once. Five years on multi-tenant platforms for enterprise security and data products.

Scroll to enter

Design For The Burst Isolate Every Tenant Trace Every Call Cache What Repeats Ship With Tests

About

Reliability is a design decision.

I'm Het Shah, a backend and AI systems engineer in Ahmedabad with about five years of experience. I architect and deliver AI and application-security platforms for enterprise customers including Armis, Comcast and Splunk. Most of it is multi-tenant, event-driven backends on AWS and the multi-agent LLM pipelines that sit on top of them. I take features from design through testing and deployment, and I've mentored junior engineers on system design and code review. Right now I'm on a team studying how AI agent behaviour can be measured and validated reliably.

I build the parts of a platform that have to keep working under load: ingestion paths, queues, caches, and the LLM stages on top. The method doesn't change. Find where the system breaks in a burst, design that failure out, and leave behind numbers that prove it.

How I build

  • 01

    Design for the burst, not the average

    Average load hides the real problem. One platform ran at 250K findings a day and hit 1.5M on weekly full-scan days. I size queues, workers and caches for that day.

  • 02

    Keep tenants out of each other's way

    In a multi-tenant system, one customer's spike must never become another's outage. Isolation is built into auth and rate limiting from the first commit.

  • 03

    Trace every model call

    An LLM pipeline you can't observe is a guess. Every call is traced, and every stage has its own model, retries and structured output, so failure rate and cost are known numbers.

  • 04

    Ship it with the tests

    Unit, integration and end-to-end suites run in containers before anything goes out. Release confidence in a distributed system is built once, then automated.

Experience

Where I've worked.

2021 to now

  1. Oct 2026 to now

    Software Engineer 2

    Infocusp Innovations · Ahmedabad

    Part of a team on a client engagement studying an AI agent evaluation pipeline: how agent behaviour can be measured and validated reliably. I bring production experience with multi-agent LLM pipelines and LLM tracing to ground the approach.

  2. Dec 2021 to Oct 2026

    Senior Software Engineer

    Crest Data · Ahmedabad

    Architected and delivered AI and application-security platforms for enterprise customers including Armis, Comcast and Splunk, end to end: design, implementation, testing and deployment. Mentored junior engineers on system design, code review and pre-commit tooling. The four projects below come from this role.

  3. May to Jul 2021

    Website Developer Intern

    LearnElectronics · Remote

    Built interactive quizzes and event registration portals with FastAPI, HTML, CSS and JavaScript.

Client Projects

The work that shipped.

04 / Projects

Four projects from my time at Crest Data, 2021 to 2026. Each was built for one of its enterprise customers.

By The Numbers

Five years, measured.

Enterprise tenants on one platform
32
Findings a day at the weekly peak
1.5M
LLM calls a day at 98.5% success
212K
Prompt tokens served from cache
85%

Skills

Backed by the work.

Each group links to its project

Also: JavaScript, React, Bash, C and C++.