Ship the whole slice
A feature is not done at the API boundary. Schema, endpoint, state and the pixel someone actually clicks are one unit of work, and I would rather own all four than hand off half.
I build the whole system: schema, API and interface. I care how every layer feels to use, because the interesting problems live between them, where a query shape decides whether a screen can ever feel instant.

MD. Rafiuzzaman Rion
Software Engineer

24
Shipped
0+
Years building for the web
0
Projects shipped to production
0+
Enterprise modules delivered
0
Roles held
I work across the full stack because the interesting problems live between the layers. Most of my time goes to enterprise modules that real teams depend on every day: task and goal management, employee portals, marketing suites, file systems. The work is less about novelty than about making complicated things feel ordinary to use.
I have shipped 24 projects to production since 2022, and the ones I am proudest of are the ones nobody had to be trained to use.

MD. Rafiuzzaman Rion
Software Engineer
A feature is not done at the API boundary. Schema, endpoint, state and the pixel someone actually clicks are one unit of work, and I would rather own all four than hand off half.
Query shape and aggregation strategy decide whether an interface can ever feel instant. Performance gets designed in at the data layer, not filed as a ticket after launch.
The next engineer is a user too. Clear naming, honest boundaries and comments that explain the why outlast any clever abstraction.
A request travels down through the interface, the service boundary and the data model. Each layer constrains the one above it, which is why I would rather own the whole path than optimise a slice of it.
Component systems, state that stays predictable under load, and motion that explains rather than decorates.
L1 · What people touch
REST and async boundaries in Python and Node, authentication that fails closed, and integrations that degrade gracefully instead of taking the page down with them.
L2 · What holds it together
Schema design and aggregation pipelines: the layer that quietly determines whether the interface above it can ever feel fast.
L3 · What decides the ceiling
Client platforms, internal tools and product surfaces, built end to end and then maintained through the part nobody photographs.
He took the inventory module from a vague brief to something our warehouse staff could use without training. When the stock reconciliation logic turned out to be wrong in an edge case, he found it himself and shipped the fix before we noticed.
Nadia Karim
Product Lead · Northwind Systems
We handed him a Python service and a React front end that had drifted apart over two years. He reconciled the contracts between them, wrote the schema once and used it on both sides, and the whole class of validation bugs disappeared.
Tanvir Hasan
Engineering Manager · Meridian Labs
What stood out was that he pushed back. Twice he told us a feature we had asked for would cost more than it returned, explained why, and proposed something smaller that solved the actual problem. That is rarer than the code.
Sarah Whitfield
Founder · Kestrel Digital
Three roles, all full-stack, all measured by what actually reached users.
Next Level Media BDonsite
Lipika AIremote
Hit solutiononsite
Client work, internal tools and the experiments that never shipped. Most of it is private or unglamorous; the point is the consistency, not the star count.
50
Public repositories
4+
Years on GitHub
5
Languages in use
What it is written in
World University of Bangladesh
Focused on software engineering, data structures, algorithms, and web technologies.
Tell me what you are trying to ship and where it is stuck. I reply to everything within a day.
+8801751073892