/system/overview  ·  v1.0

CHITRANGKUMAR JAIN

Backend EngineerPlatform Systems BuilderAI Product Developer

Building scalable backend infrastructure, distributed systems, and AI-powered applications — engineered for reliability, observability, and outcomes.

status: AVAILABLE · region: ap-south-1 · uptime: 99.97%
network · live
hover to ping
/metrics/engineering

Numbers that scale with intent.

A snapshot of the systems shipped, traffic shaped, and tooling adopted.

01 / 5
0+
Years Experience
Backend & Platform Engineering
02 / 5
0+
Daily Transactional Emails
AWS SES infrastructure
03 / 5
0+
Production Systems
Built, shipped, observed
04 / 5
0+
Projects Delivered
Backend, AI, platform
05 / 5
0+
Technologies
Across the full stack
/engineering/dna

The four lenses I build through.

How I approach systems, AI, and the boring parts in between.

01

Platform Engineering

Building scalable internal systems and automation infrastructure that compound team velocity.

Internal tools · Automation · SDKs
02

Distributed Systems

Designing reliable backend services and microservice communication with strong observability.

Queues · Schedulers · Idempotency
03

Applied AI

Building LLM-powered workflows, retrieval, and intelligent applications that ship to production.

RAG · LLM · Vector Search
04

Product Thinking

Engineering solutions aligned with business outcomes — not for the sake of architecture.

Outcomes · Trade-offs · Iteration
/mission/history

Mission history, not a resume.

Each role, the systems owned and the outcomes delivered.

Owning platform reliability and AI integration across an email & engagement infrastructure that processes 10K+ daily transactional emails.

  • Designed an AWS SES delivery pipeline with bounce/complaint handling and adaptive throttling.
  • Shipped scheduling engines for batched campaigns with retry, dedupe and idempotency guarantees.
  • Instrumented end-to-end observability: structured logs, metrics, traces, on-call dashboards.
  • Integrated LLM workflows for assisted operations and content generation pipelines.
/featured/builds

Three builds, opinionated.

Each project: the problem, the architecture, the trade-offs, the impact.

VOLUME$1.42MP95 LAT184msGUARD100%ENCRYPTIONAES-GCM · JWTcashflow · 30d+18.4%
FINTECHvisual · interactive
FINTECH

Finance Aggregator Platform

Secure financial analytics platform.

Problem

Finance teams needed a unified view of cross-account balances, transactions and analytics — without compromising on encryption, auditability or auth hardening.

Architecture

Spring Boot service layer fronting PostgreSQL with JPA, JWT-secured REST APIs, an analytics engine for aggregations, and AES-GCM envelope encryption for sensitive fields. React frontend deployed to AWS.

Challenges
  • Strong encryption without killing query performance
  • Multi-tenant data isolation and JWT-based session hardening
  • Reliable, idempotent ingestion of transactional data
  • Reproducible financial aggregations across time windows
Solution
  • AES-GCM envelope encryption with per-tenant data keys
  • Read-replica friendly analytics queries with materialized rollups
  • JWT auth with short-lived access + refresh + revocation list
  • Strict input validation, structured audit logs and metric tracing
Impact
  • Sub-200ms p95 on key analytics endpoints
  • Production-grade encryption with zero plaintext at rest
  • Auditable change history for every financial mutation
Spring BootPostgreSQLReactAWSJWTAES-GCMJPA
/architecture/playground

How systems actually talk.

Interactive system diagrams — data flowing through real services.

ClientAPI GatewayAuth · JWTFinance SvcAnalytics EngineAES-GCMPostgreSQLAudit Log

API gateway → service mesh → encrypted PG, analytics rollups, audit log.

/stack/ecosystem

The toolkit, organized.

Not a skill bar in sight. Tools I reach for to ship reliable systems.

Backend6 tools
01 / 5
JavaSpring BootREST APIsMicroservicesGraphQLgRPC
Applied AI6 tools
02 / 5
OpenAIRAGLangChainVector SearchFAISSEmbeddings
Databases5 tools
03 / 5
PostgreSQLMySQLMongoDBRedisElasticsearch
Cloud5 tools
04 / 5
AWSDockerLinuxTerraformNginx
Platform5 tools
05 / 5
ObservabilityMonitoringLoggingReliability EngineeringCI/CD
Java ·Spring Boot ·PostgreSQL ·AWS ·Docker ·Linux ·OpenAI ·RAG ·LangChain ·FAISS ·MongoDB ·MySQL ·Microservices ·Observability ·Reliability ·Monitoring ·
Java ·Spring Boot ·PostgreSQL ·AWS ·Docker ·Linux ·OpenAI ·RAG ·LangChain ·FAISS ·MongoDB ·MySQL ·Microservices ·Observability ·Reliability ·Monitoring ·
/engineering/principles

Principles I refuse to ship without.

The non-negotiables behind every system I touch.

P-01

Reliability First

Build systems that fail gracefully. Retries, timeouts, idempotency and clean rollbacks are not optional.

P-02

Observability Matters

Logs, metrics and traces are first-class citizens. If you can’t see it, you can’t operate it.

P-03

AI as a Capability

AI should enhance workflows, not replace thinking. Ground every model output in real data and clear UX.

P-04

Scale Through Simplicity

Simple systems scale better. Pick the boring, reliable tool first. Add complexity only when measured.

/system/status

Live control center.

Real-time metrics from this portfolio's backend — pinged from your browser, served by FastAPI.

connecting…
region: · refreshed every 6s · t+0
Services
Uptime
Emails Processed
AI Requests
Avg Latency
Service 1
operational
··
Service 2
operational
··
Service 3
operational
··
Service 4
operational
··
Service 5
operational
··
Service 6
operational
··
Service 7
operational
··
Service 8
operational
··
services healthy: 100%
/contact/initiate

Open channel. Let's build.

Hiring, collaborating, or comparing notes on distributed systems — I'm listening.

system status · available

Available for

  • Backend Engineering
  • Platform Engineering
  • Applied AI Engineering
  • Distributed Systems
> initiate_contact()

Send a transmission

Encrypted in transit · stored in Mongo · no spam.