Backend engineer with 3.5+ years at Cognizant building high-concurrency FastAPI services, RAG pipelines, and real-time distributed systems. Passionate about clean architecture, semantic search, and systems that actually scale under load.
Three roles. One company. Steady growth from intern to backend owner.
Actual numbers from actual production systems.
AskSOP GenAI assistant cut manual document lookup time for 500+ internal users across departments.
RESTful FastAPI backend for document ingestion and retrieval workflows maintained rock-solid availability.
Semantic Redis caching cut redundant LLM inference — saving ~$2,000/month in inference costs.
Pydantic validation + response guardrails achieved 99% accuracy and eliminated hallucinations completely.
Distributed URL Shortener handles 1000+ req/sec with sub-50ms latency, 10K concurrent users in load tests.
Multi-tier Redis + PostgreSQL smart cache invalidation slashed unnecessary database hits by 80%.
End-to-end GenAI document assistant for 500+ internal pharma users. Semantic search over 100k+ SOPs with compliance guardrails, multi-tenant Azure AD auth, and semantic Redis caching.
High-performance URL shortening service built for scale — 1000+ req/sec, sub-50ms response, 99.9% uptime under 10K concurrent users in load tests.
Actively grinding LeetCode with a focus on patterns that appear in Google, Meta, and top-tier backend interviews. Not just solving problems — understanding the why behind every approach so it maps back to real backend decisions: faster APIs, smarter caches, leaner queries.
Practice Distribution
College days. Tight budget. I had just discovered boAt earphones — incredible bass, 1-year warranty with home pickup for claims. Genuinely in love with the product. So naturally, I did what any backend engineer would do: I ran a conversion campaign. I'd invite friends and family to "just listen to this one song" — picked specifically for the heavy bass drop. The conversion rate? Suspiciously high. Same colour. Multiple invoices. I also made sure everyone knew Amazon Prime would deliver by tomorrow, so keep your invoice handy. One year later, when my earphones showed issues, I claimed a fresh warranty year using a friend's purchase invoice. Fallback planned. Edge case handled. Invoice-as-backup-strategy deployed.