See the whole picture
I like understanding how applications, services, data, infrastructure, and people interact before deciding what to build.
I design platforms, connect systems, automate repetitive work, and turn rough technical ideas into practical solutions.
“The interesting part is usually between the systems.”
My background is in software engineering and research, but the part I enjoy most is understanding the whole problem before choosing the technology.
01 · How I think
I like understanding how applications, services, data, infrastructure, and people interact before deciding what to build.
Incomplete requirements don’t bother me. I enjoy turning rough ideas into something concrete, testable, and maintainable.
If a process keeps repeating, I usually start wondering whether software should be doing it instead.
I care about reliability, observability, usability, supportability, and what happens after the prototype becomes production.
02 · What I explore
Not a checklist of buzzwords. These are the areas where I naturally spend time designing, building, testing, and improving things.
Services, data flows, APIs, integrations, deployment, monitoring, and the decisions that make a platform coherent instead of accidental.
Python, C#, JavaScript/TypeScript, REST services, desktop and web applications, and integration-heavy systems.
AWS, Lambda, API Gateway, databases, event-driven design, monitoring, and production operations.
Using AI where it adds practical value, especially around workflows, analysis, monitoring, and reducing manual work.
Making APIs, applications, devices, services, and operational processes work together reliably.
I care about the last mile. Responsive interfaces, accessible interaction, clear information design, and front ends that feel deliberate.
03 · Research foundation
My graduate research was already sitting at the intersection of machine learning, pattern recognition, computational analysis, and bioinformatics.
That research mindset still shapes how I work: question assumptions, test ideas, and look for evidence before deciding what the system is actually doing.
Biological Protein-protein Interaction Prediction using Binding Free Energies and Linear Dimensionality Reduction
Domain-domain Interactions in Transient and Obligate Protein-protein Complexes
Analysis of Obligate and Non-obligate Complexes using Desolvation Energies in Domain-domain Interactions
Analysis of Relevant Physicochemical Properties in Obligate and Non-obligate Protein-protein Interactions
Protein-protein Interaction Prediction using Desolvation Energies and Interface Properties
04 · Foundation
University of Windsor
2010–2011Khulna University of Engineering and Technology
2003–200705 · The path so far
Research, software engineering, integration work, cloud systems, and now broader platform and solution design.
Platform design, solution architecture, automation, AI, cloud systems, Python, monitoring, and technical problem solving.
Production systems, integration, operations, and solution development in the utility sector.
Web, desktop, services, APIs, databases, integrations, and digital systems.
Machine learning, pattern recognition, bioinformatics, programming, and academic research.
06 · Still curious
Some ideas become platforms. Some become automation. Some turn into experiments that take much longer than expected.
That process is usually the interesting part.
07 · Connect
Technology, platforms, automation, an idea that needs figuring out, or simply something unusual you’re building.