Loading
Available for workWest Bengal, IndiaUTC+05:30
I'm Subham Bhattacharya — a backend engineer working in Python and a Computer Science student at BITS Pilani. I work on APIs, data models and the service logic that decides what a system is permitted to do: the parts that have to hold when something goes wrong.
owning production, procurement and finance
verified — Harvard, Michigan, HackerRank
BSc Computer Science, 2026–2030
Now
I map what breaks a system, what happens when it does, and whether it breaks loudly, before I write the happy path. Four years of manufacturing taught me that the quiet failure is the expensive one.
One stack understood well enough to defend every trade-off out loud beats a list of frameworks touched once. Breadth arrives faster from a real foundation than from a wider surface.
Every system has a second reader, usually a later version of me. Clean repositories and honest documentation are part of the engineering, not paperwork filed after it.
C, memory, data structures, algorithms. CS50x, then continued in C on my own.
APIs, data modelling, authentication, and typed service code. One stack understood properly rather than five sampled.
asyncio, queues, caching and the failure behaviour of distributed components. Formalised alongside the systems track at BITS.
Serving, evaluation, data pipelines and the infrastructure models actually run on — the backend problem, with a harder correctness story.
Core — I defend design decisions in these
In operations, output scales with headcount — you want more, you hire more. Software does not work that way, and AI widens the gap further. I want to work where a good decision compounds instead of being consumed. That is the whole reason for the move, and it is why the direction is systems and infrastructure rather than anything faster to enter.
References on request
The people who can speak to my engineering are the ones who have read the code. Ask and I will put you in touch — or start with the repositories and judge the work directly.