Hi, I’m Biswajit.
This is the part of the site that isn’t a résumé: where I’m from, how I work, and what I do outside it.
I'm a backend developer from Rourkela, now leading a team at ITMC Digital in Noida. I care about systems that stay easy to change, interfaces that feel considered, and shipping things that are actually good. Outside work, I'm usually planning the next trek.
Where it started
I grew up in Rourkela, Odisha. My dad sold computers, so there were always machines around the house, and I grew up wanting to know how they worked.
I studied in Raipur, Chhattisgarh. In 2022 our team took a UIDAI problem statement to the Smart India Hackathon Grand Finale in Hyderabad and won, after 36 hours without sleep and a jury that told us "better luck next time". I wrote about those 36 hours.
Travelling alone shaped me as much as any of that. Working things out in a place where nothing is booked and nobody knows you teaches you to stay calm when a plan falls apart.
Work
I started as an associate developer at Capricorn Identity Services, a certifying authority, building Python automation with Playwright and Selenium for certificate workflows, testing and compliance.
Since January 2026 I've been a backend developer and team lead at ITMC Digital, building a car-pooling platform end to end. Most days that means Java or Node.js, PostgreSQL and AWS.
How I work
I'm a backend engineer with an eye for design. I notice spacing, copy and the small moments in an interface, and I think the same care belongs in APIs and data models.
I use AI tools heavily to move faster: drafting, exploring, and clearing the boring parts. What I don't hand over is the judgement about what's good.
Where I'm going
In five years I want to be known for delivering good products: considered, reliable, and clearly made by people who cared. Not AI slop.
Outside the code
I travel the raw way: a backpack, a rough direction, and nothing booked that doesn’t need to be. Mostly that means mountains, and the photos below are from treks. I’m also a tech-gadget person and a bit of a cleanliness freak. And I like doing things people don’t quite believe when I tell them afterwards; that look of disbelief is half the fun. I’m fit, and I’ve been planning to join a gym for a very long time.
What I care about
Inside engineering, I keep coming back to backend engineering, system architecture, software design, distributed systems, product engineering, AI and developer infrastructure.
Design the data before the screens
Most products are shaped by their data model long before anyone sees a UI. Getting it right early is the cheapest decision you’ll ever make.
Quality is the point, not the polish
AI makes code cheap. That makes judgement, taste and care the part that actually matters, so that’s where the time goes.
Backend work deserves design sense too
An API, an error message or a table name is an interface. The same eye that notices bad spacing should notice a confusing endpoint.
Boring where it counts
Proven tools for the core, experiments at the edges. Nobody should be paged at 3 a.m. because a system was interesting.
Tools I’m grateful for
The ones that got me started, and the ones I’d miss most.
Right now
What I’m working on and learning this month is on the now page.
I’m hungry.
…for good projects, good problems, and things worth obsessing over.
I’m young, I move fast, I communicate well, and I care a stupid amount about what I build. If something’s worth obsessing over, I don’t care whether it’s 10 a.m. or 2 a.m. Sometimes you just keep going until the damn thing works.
If you’re crazy enough to build something from scratch, I’m crazy enough to join you.
0 → 1 or 1 → 100, I’m up for both.