Abid Al Amin

About

Abid Al Amin

I write down what I learn while building backend systems — the concepts underneath, the trade-offs behind the architecture, and how AI actually fits in.

I am a senior software engineer with 7+ years of building backend and frontend systems, currently at Technovative Solutions. Most of my work sits where architecture meets operations: designing the service, then making it deploy, scale and stay observable once real traffic arrives.

Along the way I have led frontend and backend teams, moved slow work onto event-driven pipelines, and built the delivery platforms other engineers ship on. These days I am also working out where AI fits into that picture.

This site is the notebook I keep alongside that work: 28 entries covering the concepts I rely on, the system designs I have worked through, and what I am learning about AI. Pages appear when I understand something well enough to explain it, and get revised when I realise I did not.

Experience
7+ yrs
Companies
6
Based in
Dhaka, Bangladesh
Notes written
28

What I work on

The threads that keep showing up, whichever company or stack I am in.

  • Backend architecture

    Services with clear boundaries — business logic that does not know about the database, and APIs shaped around what clients actually ask for.

    Clean Architecture backend · graph query engine

  • Event-driven systems

    Taking slow work off the request path with queues and workers, and designing for the retries and partial failures that come with it.

    S3 → SQS → ECS video pipeline

  • Platform and delivery

    Deploys that are boring and repeatable, and production that tells you when something is wrong before you go looking.

    GitOps on Kubernetes · Prometheus alerting

  • Leading teams

    Setting the architecture a team builds on, then keeping it maintainable as the product and the team grow.

    Frontend and backend team lead

  • Applied AI

    RAG, LLMs and MCP — and how they fit into a backend that already has to be reliable, observable and cheap to run.

    The AI section of this site

Experience

From first APIs to leading teams — most recent first.

  1. Apr 2024 — Present2 yrs 6 mos

    Senior Software Engineer

    Technovative SolutionsNow

    40%faster deploys

    Leading the frontend team while owning backend architecture and the delivery platform underneath it.

    • Built a GitOps pipeline — GitHub Actions, Helm and Argo CD on Kubernetes — that cut deployment time by 40%.
    • Wrote a graph query engine on top of the ORM, so clients can fetch deeply nested, relational data in a single query.
    • Designed a Node.js backend on Clean Architecture, keeping business logic independent of infrastructure.
    • Set up Prometheus and Grafana monitoring with alerting rules, shortening time to recovery in production.
    • Node.js
    • Kubernetes
    • Helm
    • Argo CD
    • GitHub Actions
    • Prometheus
    • Grafana
  2. Dec 2022 — Apr 20241 yr 5 mos · Part-time

    Software Engineering Lead

    Lookarond GmbH (Eaaasy)

    Led both the frontend and the core backend teams for a video-first product.

    • Moved video uploads to an event-driven pipeline — S3, SQS and ECS workers — so encoding and transcoding run asynchronously.
    • Replaced static MP4 playback with HLS adaptive-bitrate streaming that holds up on unreliable networks.
    • Drove backend architecture decisions and built the NestJS APIs; set the Next.js, Redux and RTK Query frontend architecture.
    • Shipped the backend in Docker on EC2 and the frontend on Amplify, both with automated CI/CD.
    • NestJS
    • Next.js
    • AWS S3
    • SQS
    • ECS
    • HLS
    • Docker
  3. Sep 2022 — Apr 20241 yr 8 mos

    Software Engineer

    Venturas

    2M+records collected

    Full-stack engineering across several real-estate platforms.

    • Built around 60 Python crawlers and the pipelines behind them, collecting over 2 million records.
    • Designed backend APIs, database schemas and scheduled jobs with NestJS and MySQL.
    • Built Next.js frontends with Google Maps integration, plus a CV portal in React and Express.
    • Python
    • NestJS
    • MySQL
    • Next.js
    • Redux Toolkit
    • Tailwind CSS
  4. Apr 2022 — Aug 20225 mos

    Software Engineer

    Bevy Commerce

    Worked on a Shopify app built to handle millions of product records.

    • Designed and built storefront pages in Next.js, including an ETA feature for running campaigns.
    • Next.js
    • Shopify
    • Bootstrap
  5. Apr 2021 — Mar 20221 yr

    Frontend Engineer

    Audiohook

    Built the CMS the team used to run campaigns, subscriptions and authentication.

    • React and Redux throughout, with unit tests as part of the definition of done.
    • React
    • Redux
  6. Sep 2019 — Mar 20211 yr 7 mos

    Software Engineer

    ELO

    Where it started: APIs and frontends for test automation, EdTech and food delivery.

    • NestJS APIs for a test-automation product.
    • Django and Django REST Framework backends for an EdTech platform and a food-delivery app.
    • Frontends in React, Redux, MUI and TypeScript.
    • NestJS
    • Django
    • React
    • TypeScript

Toolkit

What I reach for, grouped by where it lives.

Languages
  • TypeScript
  • Python
  • Go
Backend
  • Node.js
  • NestJS
  • Django
  • Express
  • MySQL
Frontend
  • React
  • Next.js
  • Redux
  • RTK Query
  • Tailwind CSS
Cloud & infra
  • AWS EC2
  • S3
  • ECS
  • SQS
  • Amplify
  • Cloudflare
  • Docker
  • Kubernetes
Delivery
  • GitHub Actions
  • Helm
  • Argo CD
  • Prometheus
  • Grafana
AI
  • RAG
  • LLMs
  • MCP

Education

BSc in Computer Science & Engineering

Daffodil International University · 2015 — 2019

Certified: Database for Software Developers

About this site

Three layers, one model

Each layer depends on the one above it. Select a layer to see what belongs there.

Concepts

Single ideas, explained once and properly. A concept page exists because I had to look the idea up more than twice, or because the explanations I found skipped the part that actually mattered.

  • Authentication and tokens
  • Networking and protocols
  • Databases, indexes, caching
  • Distributed systems primitives

How pages get written

  • Explain the mechanism

    If a page cannot say what actually happens on the wire, in memory, or on disk, it is not finished.

  • Show the numbers

    Capacity, latency budgets and failure rates decide architecture. Designs without arithmetic are opinions.

  • Name the trade-off

    Every choice costs something. The page should say what, not just recommend the winner.

  • Revise in public

    Pages get corrected as I learn more. The updated date is meaningful, not decorative.