Backend Software Engineer — Python • Django • PostgreSQL • Redis • AWS • Docker

Building scalable backends at GIM Info Solutions (Y Combinator) 🚀

name:      Abhishek Choudhary
role:      Backend Software Engineer @ GIM Info Solutions (YC)
product:   web.gimbooks.com — GST-compliant business platform
location:  Raipur, Chhattisgarh, India
stack:     Python · Django · DRF · PostgreSQL · Redis · Docker · AWS
focus:     scalable backends · payments · AI integration · reliability
ask_me:    Python, Django, Postgres, Docker, AWS, REST APIs, system design

• 💼 Shipping production backend at GIM Info Solutions (Y Combinator) for GimBooks — invoices, payments, e-Invoice / e-Way bill.
• 🐍 Backend-first engineer — Python, Django, DRF, PostgreSQL, Redis, Celery, and REST APIs I can defend line by line.
• ☁️ Comfortable across the deploy path — Docker, AWS, CI/CD, Kubernetes, Linux.
• 🤖 Built an in-app AI agent at GimBooks that drafts invoices/POs and guides users through workflows in natural language.
• 🧠 Solved 400+ DSA problems · shipped 15+ full-stack projects.
• 📚 Currently deep in system design, Kafka, Redis at scale, microservices, and Kubernetes internals.

🏋️ AI Fitness Platform React · Django REST · PostgreSQL · Razorpay · LLM AI-powered fitness coach — personalized workouts, meal plans, and calorie tracking based on the user's body metrics, shape, and goal. Structured LLM prompts + JSON-schema outputs Streaming UI for workout plan generation Auth + Razorpay-backed subscription flow Backend performance tuned by 35–40% 🔗 Live  •  Case study	🏥 Medicare — Appointment System MERN · MongoDB · Express · Razorpay Full-stack medical services platform with online appointment booking, doctor scheduling, and payments. JWT auth + user dashboard REST APIs for services + bookings Razorpay integration for payments Server-side validation as source of truth 🔗 Live  •  Case study
💬 You Chat — Realtime Chat MERN · Socket.io · JWT Realtime messaging on the MERN stack with rooms, presence, typing indicators, and reconnect-safe sessions. Room-based Socket.io namespaces Server-authoritative message ordering Reconnect handshake restores last active room 🔗 Live  •  Code	🎵 Spotify-M — Music Streaming Next.js · Node.js · MongoDB Spotify-inspired music streaming app with auth, playlists, and a persistent audio player that survives navigation. Global player state above the router Next.js Image for optimized cover art Server-truth auth cookies + hydration 🔗 Live  •  Code
🎬 Hianime — Anime Browser Next.js · SSR · Tailwind Discovery-focused anime browser with a big-art gallery UI, ratings, episode counts, and dynamic detail routes. Next.js SSR for fast first paint + shareable URLs Optimized Image loading with priority hints In-memory data cache with TTL 🔗 Live  •  Code	🤖 Whatgpt3 — GPT-Inspired Landing React · Vanilla CSS A polished, GPT-inspired product landing page built as a modular React app with a custom token-based design system. Component-driven section boundaries Design tokens in vanilla CSS (no framework) Small bundle, sharp mobile breakpoints 🔗 Live

📁 More on my portfolio — each project ships with a full case study covering architecture, challenges, and takeaways.

I write about the things I ship in production — payments, reliability, incident recovery, and the tradeoffs that don't make the marketing page.

• 🔥 Surviving the outage: rebuilding Postgres from scratch under fire
• 💳 Wiring GimBooks Pay: from checkout to reconciliation
• 🔁 Building self-healing webhook handlers
• 🚢 From localhost to Kubernetes: shipping web.gimbooks.com safely

📖 Read them all → abhishekchoudhary01.netlify.app/#/blog

• 🧠 400+ DSA problems solved
• 🚀 15+ full-stack projects shipped
• 💼 Backend Engineer at YC-backed startup (GIM Info Solutions)
• 🤖 Built and shipped an in-app AI agent in production
• 🔥 Owned incident recovery for a production DB outage (see the blog)
• ☁️ End-to-end ownership: schema → API → Docker → Kubernetes → AWS

• System Design — patterns for building at scale
• Apache Kafka — event streaming and log-based architectures
• Redis at scale — pub/sub, streams, and caching topologies
• Kubernetes — operators, autoscaling, and production hygiene
• Microservices — service boundaries, contracts, and observability
• Distributed Systems — consensus, replication, and failure modes

The right question isn't "how do we not fail?" — it's "what happens the moment we do?"

• Idempotency isn't a nice-to-have. Any endpoint that touches money or state deserves an idempotency key.
• Treat entitlements as data. Plan-driven behavior in code becomes debt during an incident.
• Backups are only real if you restore them. Untested backups are hopes, not backups.
• Ship a maintenance kill switch before you need one. A remote-config flag is a 1-day project that pays for itself in the first outage.
• Cheap deploys change how a small team ships. Instant rollbacks lower the cost of being wrong.

I'm open to backend / full-stack roles, freelance work, and interesting side collaborations. Expect a reply within 1–2 days.

⭐ If you found something here useful, drop a star on the repos — it means a lot.