I am Robin Mollah, a software engineer focused on building systems that survive real constraints: limited hardware, high traffic, growing data volume, and production pressure.
My work sits across backend engineering, cloud infrastructure, data systems, and applied AI. I care most about the part where architecture decisions meet operational reality. That usually means performance, reliability, cost, maintainability, and getting systems to keep working when conditions are not ideal.
What I Work On
I design and ship software systems end to end. Depending on the problem, that can mean backend services, APIs, distributed jobs, cloud infrastructure, deployment workflows, observability, or data pipelines.
Typical areas I work in:
- Backend platforms and service architecture
- Cloud infrastructure and deployment systems
- Data processing and analytics pipelines
- Performance optimization under strict limits
- Production debugging and reliability work
- AI integration where it solves a practical problem
How I Work
I prefer clear system boundaries, simple interfaces, and designs that can be defended technically. I am comfortable working from first principles when a system is failing, too slow, too expensive, or too fragile.
I tend to be most useful in environments where the work is ambiguous but the constraints are real. That includes:
- Turning vague product goals into concrete technical plans
- Stabilizing systems already under load
- Reworking legacy architecture without stopping delivery
- Reducing operational complexity and cloud waste
- Mentoring engineers through design and implementation decisions
Engineering Perspective
I value software that is practical before it is fashionable. Tools and frameworks matter, but only in the context of whether they make the system easier to operate, extend, and trust.
I usually optimize for:
- Correctness under real usage
- Sustainable complexity
- Strong debugging visibility
- Measured performance improvements
- Architecture that can evolve without constant rewrites
Beyond The Stack
I am especially interested in hard engineering problems that force tradeoffs: low-resource environments, large file movement, real-time communication, high-throughput APIs, and infrastructure that must stay stable as usage changes.
This site is where I keep a public record of some of that work: selected challenges, technical writing, and the kinds of systems I have spent time building.