A bit about me.

The short version

I'm a full-stack software developer with 2.5+ years of professional experience at DSi (DS Innovators) in Dhaka. I specialise in the Laravel stack and increasingly work in Java Spring Boot and React (TypeScript).

I came up through competitive programming – ICPC, Codeforces, CodeChef – and that habit of breaking problems into the smallest pieces still shapes how I write production code. I'd rather ship a small thing that works than a big thing that almost works.

The longer story

I started writing code seriously during my BSc in CSE at Daffodil International University, where I graduated with a CGPA of 3.84/4.00. Most of that time I spent in two places: the contest pages of online judges, and the PHP / Laravel ecosystem. The combination taught me two different kinds of discipline – the algorithmic side from solving 500+ problems, the engineering side from building end-to-end web systems.

After an internship at BITM and an industrial training at LEADS, I joined DSi in November 2023 as a Junior Software Engineer. Since then I've designed and shipped two internal products – Qwiz, a multi-role peer-reviewed question bank, and Event Attendance, a real-time attendance tracker – and I'm currently contributing as a developer and support engineer on DMS (DSHE), a national education monitoring system built for the Government of Bangladesh with UNICEF support.

Alongside the day job, I'm finishing an M.Sc in CSE at Jahangirnagar University (expected early 2026). The thread connecting all of it is the same: I like figuring out what something really needs to do, and then building it as plainly as I can.

How I work

Read the system first. Before I touch code, I want to know how data moves, who the users are, and what's actually been promised. Most "bugs" turn out to be misunderstood requirements.

Boring is a feature. I default to the most ordinary solution that solves the problem. New frameworks are exciting; calls at 2am because the new framework misbehaves are not.

Database first, UI second. A clean schema and well-thought-out queries save weeks of work downstream. My time at DMS – writing complex client-specific reports against a live production database – drove this home.

Own the whole loop. I like working across the stack precisely because I can chase a problem from the React component down to the SQL query. Specialists are great, but generalists ship faster on small teams.

What drives me

Two things. First, the small thrill of green tests after a hard bug. Second – and this is the bigger one – the fact that the systems I work on now (DMS in particular) actually touch real institutions across the country. When a report I wrote helps an education officer make a decision they couldn't make before, that's the part of the job that doesn't get old.

Beyond code

When I'm not at a keyboard for work, I'm usually at a keyboard for fun – solving competitive programming problems, exploring AI tooling, or curating things like awesome-free-ai-tools and Bangla-language developer resources like react-bangla-tutorial to give back to the local dev community.