Loading
About
Long form
I'm Subham Bhattacharya, a backend engineer working mainly in Python and a Computer Science student at BITS Pilani. The parts of a system I care about are the ones that have to stay correct under pressure — APIs, data models, authentication, and the service logic that decides what a system is permitted to do.
Most of what I write is service and pipeline code: Protocols at the interfaces, generics for what moves through them, strict mypy across all of it, nothing computed until something asks for it. I would rather understand one stack deeply enough to defend every trade-off out loud than collect frameworks I have touched once.
I design for the failure case before the happy path. That habit came from four years running a manufacturing operation — production, quality, procurement, finance — where a tolerance drifting means a batch is scrap and a supplier slipping means a line stops. Physical systems teach you quickly that a process which fails loudly is cheap and one that fails quietly is expensive. The ordering carried straight into how I write software.
Graph search and C take up much of the rest of my time, and both changed how I design in Python — one for how I reason about structure, the other for what an operation actually costs. The degree formalises this, with a concentration in computing systems and systems programming.
Longer term I'm building toward AI/ML systems. Serving, data pipelines, evaluation and behaviour under load are infrastructure problems with a harder correctness story — which is exactly the kind of work I want to be doing, and exactly why the foundation matters.
Everything on my GitHub is meant to be read: clean repositories, honest documentation, and projects I can stand behind in a technical conversation.
Facts
- Name
- Subham Bhattacharya
- Role
- Backend Engineer, building toward AI/ML Systems
- Location
- West Bengal, India · UTC+05:30
- Studying
- BSc Computer Science, BITS Pilani (2026–2030)
- Languages
- English (native / full professional) · Bengali (native) · Hindi (professional working)
- [email protected]
How I work
Failure modes first
Before the happy path, I want to know what breaks it, what happens when it breaks, and whether it breaks loudly. A process that fails quietly is the expensive kind.
Depth over breadth
One stack understood well enough to defend every trade-off out loud, rather than a list of frameworks touched once. Breadth comes after, and it comes faster from a real foundation.
Written to be read
Code and documentation both have a second reader — usually a later version of me. Clean repositories and honest READMEs are part of the work, not paperwork after it.
Short versions
- One line
- Backend engineer working in Python, building toward AI/ML systems.
- Short bio
- Subham Bhattacharya is a backend engineer working in Python and a Computer Science student at BITS Pilani. He came to software from manufacturing operations, and builds APIs, data models and service logic designed to stay correct as systems grow.
- Elevator
- I build backend software in Python — APIs, data models, authentication, the service logic that has to hold as a system grows. I came to engineering from operations: four years running production, procurement and finance at a feed manufacturer in West Bengal. That work taught me to think in systems, constraints and failure modes before I could write one line of production code. I'm formalising the fundamentals through a CS degree at BITS Pilani, and I'm building toward AI/ML systems — because that work runs on exactly the kind of reliable infrastructure I'm focused on now.