Senior Software Engineer  ·  Dhaka, Bangladesh

I build the layer between a language model and software that already exists.

Five-plus years on the same stubborn question: how do you take something that works in a notebook and make it survive real users? Mostly that has meant backend systems, production machine learning, and the harness layer in between. Lately a fourth thread has crept in, machine learning for biology, where the datasets are small, the labels are noisy, and being honest about your numbers matters more than beating a leaderboard.

Read the writingSee the projectsGitHub

Shamsuddin Ahmed, photographed in Dhaka

Now

  • Since Aug 2026

    Senior Software Engineer, Mevrik

    An AI customer-experience platform used by telecom operators and several hundred smaller businesses. I work on the AI side: agents, retrieval, and the serving infrastructure underneath.

  • Since 2024

    Founder, AlgolyzerLab

    A small studio for applied AI that does not fit a product roadmap: sports science for elite cricket, clinical software for doctors, agriculture AI, and research engineering.

What I think about

  1. 01

    Agent harnesses

    A model is only as useful as the surface you hand it. Most teams give an LLM raw tables and generated specs instead of the intent-named operations their own code already has.

  2. 02

    Machine learning for biology

    Anti-inflammatory peptide prediction, and structure-aware virtual screening of natural products against understudied viral proteases. Both taught the same lesson: the dataset you choose decides the result long before the model does.

  3. 03

    Systems that stay explainable

    Small, readable, zero-magic tools I actually use: perceptual image compression, a terminal system monitor, actor-model agent swarms. Single binaries, no framework underneath.