I'm a Software Engineer from Dhaka, Bangladesh with nearly five years of hands-on experience shipping scalable web and mobile products. My home base is the WordPress ecosystem, where I architect custom plugins, power eCommerce stores with WooCommerce, and help move the platform forward for the community that made my career possible.
I care about clean architecture, thoughtful UX, and code that ages well. From a bespoke WordPress plugin to a cross-platform React Native application used by real people every day, I enjoy every step of the journey, from the first sketch on a notebook page to the final production rollout. I am always learning, always iterating, and always hungry for the next meaningful problem to solve.
On the web side, I work primarily with PHP and JavaScript. I build WordPress plugins from the ground up, write custom Gutenberg blocks, extend WooCommerce for unusual business needs, and design REST endpoints that hold up under real production load. I am comfortable inside the WordPress core too. I read the source, I follow the trac tickets, and I try to write code that fits the way the platform thinks rather than fighting it. The best plugin is the one a stranger can drop into a site and forget about.
On the frontend, I work with React and Next.js. I build interfaces that prioritize clarity over cleverness, that respect the user's time and attention, and that hold up gracefully on slow networks and old devices. I have shipped marketing sites, dashboards, internal tools, and consumer apps, and I have learned that the same principles apply to all of them. Good design is invisible. Bad design gets in the way.
On mobile, I work with React Native through Expo. I have shipped apps to both the App Store and Google Play, handled the long tail of platform-specific quirks, and learned how to keep a codebase small and shippable as the product grows. I treat mobile as a first-class platform, not an afterthought. The phone is where most of my users actually live.
I write tests when they earn their keep. I write documentation when someone else will read it. I write small commits with clear messages because I read git history more than I write it. I prefer to remove code over adding it, and I prefer boring solutions over clever ones unless the cleverness is genuinely earning something in return.
I work well alone and well in teams. I am comfortable taking a vague problem and producing a concrete proposal, and I am comfortable taking a concrete proposal and producing working software. I ask questions early, I push back when I disagree, and I commit fully once a decision is made. Disagreement is cheap before the work starts and expensive after.
I read more code than I write. I learn from open source projects, from old codebases, from colleagues who have seen more than I have, and from the long tail of bugs that taught me something I did not know I needed to know. Every project leaves a mark. I try to keep the good marks and discard the bad habits.
I want to work on problems that matter, with people who care, on products that get better instead of worse over time. I want to keep growing as an engineer and as a teammate. I want to build things that outlast the meeting that decided them. That is the short version. The long version is everything above, and the longer version is the work itself.
Thanks for reading. If any of this resonates, reach out. I'm always open to a good conversation about clean code, hard problems, and the craft of shipping software that people actually use.