Skip to main content

00 / DevOps Engineer · Dhaka → Remote

Making complex systems run like they should.

DevOps Engineer and Software Engineer building the pipelines, platforms and guardrails that let product teams ship ten times a day without paging anyone at 3am.

shanto@platform:~
$
type a command, try help
scroll ↓
AWS
Google Cloud
Kubernetes
Docker
Terraform
GitHub Actions
Argo CD
Helm
PostgreSQL
Redis
NGINX
Prometheus
Grafana
HashiCorp Vault
Ansible
Cloudflare

01 / The work

Hands-on systems engineered with production-grade standards.

Distributed Microservices · Cloud-Native CI/CD GitHub

OrderFirst — Distributed Microservices & Zero-Downtime CI/CD Platform

A distributed restaurant ordering and table reservation system engineered with an event-driven microservices architecture, schema isolation, and automated zero-downtime deployment.

Tech Stack

  • React
  • TypeScript
  • Tailwind CSS
  • Vite
  • Node.js
  • Express.js
  • PostgreSQL
  • Prisma
  • RabbitMQ
  • Docker
  • Jenkins
  • Nginx
  • Linux

Deployment Flow

01
Commit
02
Diff Detect
03
Build & Test
04
Deploy
Full-Stack Platform · DevOps Delivery GitHub

DevTalk — Developer Community & CI/CD Platform

A LinkedIn-inspired community where developers solve coding problems, publish blogs, and connect through jobs.

Tech Stack

  • Next.js
  • React
  • Tailwind CSS
  • Zustand
  • Node.js
  • Express.js
  • MongoDB
  • Redis
  • Jenkins
  • GitHub
  • Docker
  • SonarQube
  • Trivy
  • Linux

Deployment Flow

01
Push
02
Test
03
Security Scan
04
Deploy
Serverless Platform · 100% Terraform IaC GitHub

Serverless URL Shortener — Hexagonal AWS Architecture & IaC Delivery

A high-throughput, enterprise-grade serverless URL shortening and link management platform on AWS featuring pure functional hexagonal architecture, 100% Terraform IaC, and automated sub-second CI/CD.

Tech Stack

  • AWS Lambda
  • Terraform
  • DynamoDB
  • API Gateway v2
  • CloudFront
  • Amazon S3
  • GitHub Actions
  • TypeScript
  • React 19
  • Tailwind CSS
  • Vite 8
  • Vitest
  • Zod

Deployment Flow

01
Push
02
208 Tests
03
Terraform IaC
04
Edge Deploy

02 / Experience

Years spent keeping systems honest.

2 roles · since 2022
  1. a3f9c21

    Front-End Engineer

    HEAD

    Universal Machine Inc. · Remote · Full-time

    Jan 2024 → Jun 2026
    • Built a carbon credit management platform handling end-to-end project workflows — methodology creation, project setup, and inventory management — serving enterprise clients in sustainability.
    • Engineered scalable front-end architecture using Next.js (SSR/SSG), React.js, TypeScript, Jotai, and Tailwind CSS to ensure high performance and maintainability.
    • Contributed to Minipay wallet application (200K+ users), implementing smart contract interactions via Ethers.js and wallet authentication via RainbowKit.
    • Designed and implemented RESTful APIs with Node.js and Express.js, architecting relational database models with PostgreSQL and Prisma ORM.
    • Built CI/CD pipelines with GitHub Actions for automated linting, unit testing, and zero-downtime deployment on merge to production.
    • Next.js
    • TypeScript
    • Node.js
    • PostgreSQL
    • Prisma
    • GitHub Actions
    • Docker
  2. 7be41d0

    Junior Web Developer

    InnovexIT · On-site · Part-time

    Jun 2022 → Feb 2023
    • Created and maintained responsive web interfaces for appointment and workforce management platforms using React.js, Next.js, TypeScript, and Tailwind CSS.
    • Collaborated on front-end architecture and UI implementation, improving usability, load performance, and accessibility.
    • Contributed to feature enhancements and bug fixes across multiple client projects, ensuring reliable user experiences.
    • React.js
    • Next.js
    • TypeScript
    • Tailwind CSS

03 / The toolchain

Every layer, deployed with intent.

18 tools

GitHub Actions

workflows

Jenkins

pipelines & automation

Git

version control

GitHub

scm & collaboration

Terraform

modular iac

Ansible

config management

Kubernetes

orchestration

Docker

container runtime

NGINX

ingress & proxy

AWS

cloud platform

PostgreSQL

relational db

MongoDB

document database

Redis

in-memory cache

RabbitMQ

message broker

Prometheus

metrics & alerting

Grafana

dashboards

Linux

systems & kernel

GNU Bash

shell automation

04 / Verified skills & honors

Recognitions & Credentials

Bangladesh Blockchain Olympiad

Top 10 Finalist

Digital Sharecropper (Team Block-bit)

Year · 2023

Docker — Hands-on Containerization

Certified

Container workflows, multi-stage builds, volumes, networking & Docker Compose.

Year · 2024

GitHub Actions — CI/CD Automation

Certified

Automated workflows, composite actions, caching, artifacts & matrix builds.

Year · 2024

05 / Process / Execution model

How I work from incident to system.

  1. $ runbook understand --incident

    1. Understand

    Map failure domains, SLO targets, and real developer bottlenecks before touching YAML.

    ✓ failure domains mapped · 3 bottlenecks identified
  2. $ plan review --blast-radius

    2. Plan

    Draft small, reversible architecture plans with explicit blast-radius and rollback bounds.

    ✓ architecture approved · rollback verified
  3. $ scaffold golden-path --module=core

    3. Delegate / Build

    Codify golden paths, reusable Terraform modules, and automated CI/CD workflows.

    ✓ 3 modules codified · pipeline green
  4. $ chaos test --dry-run --policy=strict

    4. Review

    Enforce policy-as-code checks, dry-run diffs, and failure-injection drills in staging.

    ✓ policy checks passed · 0 violations
  5. $ slo verify --p99 --window=30d

    5. Measure

    Verify deploy lead time, error-budget burn, and p99 latency against production SLOs.

    ✓ p99 < 85ms · 99.95% SLO held
  6. INCIDENT RESOLVED
    SYSTEM STABLE
    3
    bottlenecks resolved
    0
    policy violations
    < 85ms
    p99 latency
    99.95%
    SLO held

06 / Principles

Calm systems are monitored systems.

  1. 01

    Design for reliability

    Assume every dependency fails. Budget errors, rehearse recovery, and make the safe path the default one.

  2. 02

    Automate the repeatable

    If I've done it twice by hand, the third time is a pipeline. Toil is a bug with a ticket number.

  3. 03

    Keep changes reviewable

    Small diffs, readable plans, versioned everything. Production should never surprise the person who changed it.

07 · CONTACT
shanto@portfolio:~
whoami

> DevOps Engineer · open to DevOps roles & freelance

$ cat contact.txt

Let's ship something that doesn't page anyone.

© 2026 Hasibul Islam Shanto · Dhaka, Bangladesh
BST · Bangladesh