00Senior Software Engineer · Dhaka, Bangladesh
Software engineering leader
Leading platform engineering at BRAC IT
I design and lead backend systems that have to keep working — for products, for teams, and for people who depend on them.
Over seven years I have built .NET platforms, event-driven services, and real-time infrastructure. At BRAC IT I lead the development team behind the platform powering BRAC’s Social Empowerment and Legal Protection programme. Before that I shipped Web3 products at LiquidX Studio and enterprise logistics software at SELISE.
01 About
I am a Senior Software Engineer with over seven years of experience, currently at BRAC IT. My work sits at the intersection of backend architecture, microservices, and the practical leadership that turns a system into something a team can own.
I focus on ASP.NET and .NET-based services: shaping the architecture, tightening the seams between services, reviewing code, and working through requirements until the software matches the real problem. At BRAC IT I designed and built an end-to-end SMS management service and a real-time push notification system using Server-Sent Events.
I studied Computer Science at Rajshahi University of Engineering & Technology, where I competed in national programming contests. I also spent two years in blockchain engineering at LiquidX Studio — NFT staking, minting, marketplaces, and donation platforms. That work still informs how I think about correctness and trust. My center of gravity is high-quality, maintainable backend systems.
02 Engineering philosophy
This is not a stack list. It is the judgment I bring to architecture, delivery, and the people around the code.
01
The most important systems I have worked on are not impressive because they are clever. They are impressive because someone in the field, on a site, or in a clinic cannot afford them to fail. I start from that constraint.
02
Microservices, queues, and real-time channels only earn their keep if the team can reason about them. I care about clear service boundaries, explicit contracts, and the operational story: what happens when this message is late, duplicated, or lost.
03
Code review, requirement analysis, and engineering standards are not ceremony. They are how a senior engineer multiplies. I would rather leave a codebase that a team can change than a brilliant module nobody dares to touch.
04
The strongest work I have done came from understanding the business well enough to challenge the request. Software is a decision, not a transcription of a ticket.
03 Experience
Titles are listed as they were. Leadership is described where the work itself required it.
Apr 2024 — Present
Dhaka, Bangladesh
Backend engineering for platforms that have to hold at organisational scale — with a current focus on the technology behind BRAC’s Social Empowerment and Legal Protection programme.
In 2025, BRAC’s SELP programme served more than 25,000 people through 268 legal-aid clinics in 33 districts. Those figures describe the programme the platform supports — not personal metrics.
.NETASP.NETMicroservicesServer-Sent EventsSMS
Apr 2023 — Mar 2024
Apr 2022 — Mar 2023
Singapore
Previously Software Engineer, Apr 2022 – Mar 2023
Platform and blockchain engineering for player-owned digital products — staking, minting, and on-chain marketplaces in production Web3 environments.
SolidityWeb3NFTERC-721JavaScriptNode.js
Jul 2018 — Jun 2022
Dhaka, Bangladesh
Product engineering for European enterprise operations — construction logistics and railway inspection — with a full-stack .NET and Angular footprint.
ASP.NET CoreAngularMongoDBRabbitMQRedis
04 Selected work
These are products and services I can point to from my professional record — not a gallery of case-study fiction.
The technology behind BRAC’s Social Empowerment and Legal Protection programme. I started as a backend engineer on the platform and now lead the development team. The work is about reliable, scalable systems that field teams can actually use — not a demo that looks complete.
.NETMicroservicesBackend
Designed and developed an end-to-end SMS management service — a dedicated backend capability rather than a feature bolted onto an existing app. The problem is operational: messages have to be sent, tracked, and reasoned about as a system.
.NETSMSMicroservices
A push notification system built on Server-Sent Events. SSE is a deliberate choice: one-way, HTTP-native, operationally simpler than a socket fabric when the product needs the server to speak and the client to listen.
Server-Sent Events.NETRealtime
Enterprise software for large construction sites in Europe. Users manage equipment and materials, book equipment and unloading zones, track vehicles, and direct drivers from web and mobile. Built with ASP.NET Core, MongoDB, RabbitMQ, Redis, and Angular.
ASP.NET CoreAngularMongoDBRabbitMQRedis
Cross-platform mobile application for inspecting railway tracks, junctions, and station buildings. Inspectors capture data and photos on-site; the back office receives that record instead of re-entering it by hand.
Cross-platform mobile
Product engineering on Pixelmon Evolution, part of a player-owned monster universe spanning games, collectibles, and on-chain assets.
Web3Blockchain
NFT staking site and on-chain gachapon for Anime Metaverse — the kind of product where the contract, the wallet flow, and the user journey have to agree.
Web3NFTSolidity
Web3 product work on Pixelmon Trainer and Pixelmon Trainer Adventure, continuing the same franchise surface: on-chain assets connected to a playable world.
Web3Blockchain
05 Technical expertise
Listed technologies are ones I have used in professional or published work. I do not list a cloud, framework, or datastore here unless I can point to that use.
06 AI-driven development
I do not claim production LLM platforms I have not shipped. I do treat AI as part of how a senior engineer should work in 2026: as tooling, as architecture literacy, and as a set of systems that still need humans in the loop.
Coding assistants as a force multiplier for boilerplate, exploration, and review — never as an unexamined author of production code.
Using models to narrow failure hypotheses, draft tests, and challenge my own assumptions. The engineer still owns the verdict.
A second reader for diffs and a first draft for documentation, then a human pass for accuracy, tone, and the things a model cannot know.
The quality of an assistant is the quality of the context you give it. I treat prompts, diffs, logs, and repo maps as engineering inputs.
07 Architecture & system design
These are architectural readings of work I have shipped — the constraints, the choices, and why they were the choices.
01
BRAC IT
02
BRAC IT
03
CLM · SELISE
04
LiquidX Studio
08 Leadership
Leadership, for me, is the work of making a team faster and a system safer — not collecting authority. I wrote about this publicly because I believe it: influence is earned through integrity, consistency, and the space for people to speak.
At BRAC IT I now lead the development team behind the SELP platform. The title on paper is Senior Software Engineer. The job is technical direction, delivery, and the quality of the system the programme depends on.
I have run code reviews as part of how the work gets done — not as a bottleneck. A good review leaves the author stronger and the codebase clearer.
A former manager at SELISE described a product-development mindset and a habit of learning the business, not only the ticket. That is still how I prefer to work with product and domain partners.
Teams that cannot disagree cannot design. I want standards that are strict about the software and generous with the people writing it.
“An exceptional software engineer with a strong product development mindset. His deep business understanding, sharp problem-solving skills, and ability to learn new concepts rapidly make him a standout professional.”
“An amazing researcher and very knowledgeable in web 2 and web 3 technologies. Shafiul can learn new technologies and languages quickly and can consistently deliver high-quality products.”
09 Open source
Selected repositories from @shafiul-nobe. These are public artifacts — mostly blockchain, .NET, and Node — not a substitute for the production systems above.
10 Contact
I am most useful on problems that mix architecture, delivery, and the people who have to live with the result. Email is the most direct way to reach me; LinkedIn works as well.