What I Build
I build AI-powered systems, cloud platforms, and backend architecture. My work sits at the intersection of AI engineering and infrastructure — designing systems that are not just functional but production-grade: reliable, observable, scalable, and maintainable.
Currently, I'm focused on LLM-powered applications, RAG pipelines, agent systems, and the platform engineering required to run them in production.
How I Got Here
I started as a mathematics student, which shaped how I think about systems — in terms of structure, constraints, and elegant solutions to complex problems.
I moved into cloud and platform engineering, spending years building CI/CD pipelines, managing Kubernetes clusters, automating infrastructure with Terraform, and shipping software on AWS. I earned certifications not as resume decorations but because I wanted to understand the systems deeply: CKA, three AWS certifications, Terraform Associate, Docker, Jenkins.
That infrastructure groundwork gave me something most AI engineers lack: the ability to build systems that actually survive production. When I build an LLM application, I think about deployment pipelines, container orchestration, observability, cost, fault tolerance, and scale — not just model accuracy.
How I Think About Engineering
I believe the best engineers are systems thinkers. Every technical decision involves trade-offs — latency vs. cost, flexibility vs. complexity, speed vs. reliability. I try to make those trade-offs deliberately.
I care about:
- Architecture over hacks — Building systems that can evolve, not just work today
- Reliability as a feature — If it breaks at 3 AM, the architecture wasn't good enough
- Automation as leverage — Manual processes are technical debt with interest
- Clarity in complexity — The best systems are understandable, not clever
- Shipping over theorizing — Ideas are cheap; running systems are not
Beyond Engineering
I led the Brahmanbaria Science Club as President, where we reached over 4,000 students through science education programs, workshops, and community outreach. That experience taught me something code can't: how to lead, communicate complex ideas clearly, and build teams around shared goals.
I believe engineering leadership is not just about technical decisions — it's about creating clarity, mentoring others, and building systems that outlast any individual.
What's Next
I'm deepening my work in AI systems engineering — building LLM-powered applications with production-grade infrastructure, exploring agent architectures, and developing the platform patterns that make AI systems reliable at scale.
If you're working on something in this space, I'd like to hear about it.