Software Engineer · BRAC IT Services Ltd.
I build Java and Spring Boot systems around explicit business rules, transactional correctness, safe retries, concurrency control, authorization, reliable messaging, and observable failure handling.
Flagship engineering case study
A deliberately fragile order API repaired one production-style incident at a time. Instead of presenting a clean CRUD demo, the repository preserves the failure, root cause, trade-offs, remediation, regression test, and evidence for each incident.
SQL performance
A 20-order page generated 42 prepared statements because DTO mapping traversed lazy order items and products after pagination.
Idempotency
A timed-out client could retry a successful request and create a second order because the API had no durable command identity.
Concurrency control
Two buyers read the same final unit and both succeeded through a classic lost-update race, even though the final stock value still looked valid.
Application security
The baseline trusted a caller-controlled customer header and allowed arbitrary order access, administrative actions, and operational endpoints.
Messaging reliability
A database commit and broker publish are separate side effects. A crash between them could leave a durable order with no integration event for downstream systems.
Professional experience
My production work centers on translating changing business rules into clear service boundaries, traceable state changes, and reliable operational behavior.
Built backend capabilities across accounts, contacts, leads, opportunities, quotes, campaigns, territories, products, and configurable pipeline boards.
Spring Boot · PostgreSQL · Flyway · Redis · RabbitMQ · OpenAPI
Developed backend flows for intake, triage, comments, forwarding, team operations, notifications, metadata, and service-performance tracking.
Spring Boot · PostgreSQL · Redis · RabbitMQ · Quartz · JPA/Hibernate
Selected systems
I use independent projects to make architecture choices inspectable and to explore failure modes that are difficult to demonstrate safely in production systems.
Distributed transactions
Event-driven order coordination across order, inventory, and payment services with autonomous data ownership, idempotent consumers, explicit failure events, and compensation.
Event-driven delivery
Notification delivery and latency simulation with durable delivery records, asynchronous fan-out through RabbitMQ, and live per-user status updates over WebSocket/STOMP.
Capabilities
Framework knowledge matters, but the harder part is designing behavior that stays correct when requests repeat, transactions overlap, dependencies fail, and systems evolve.
Define invariants, transactional boundaries, ownership, and failure semantics before optimizing throughput.
Reproduce the failure, measure it, compare alternatives, and keep regression evidence close to the code.
Retries, queues, backlogs, logs, metrics, health checks, and recovery paths are product behavior.
Java 25 · Spring Boot 4 · Spring Security · Spring Data JPA · Hibernate · REST · OpenAPI
DDD · CQRS · Saga · modular monoliths · microservices · transactional outbox · idempotency
PostgreSQL · MongoDB · Redis · RabbitMQ · Kafka · Flyway · indexing · query design
JUnit 5 · Mockito · Testcontainers · Docker · GitHub Actions · Actuator · Prometheus · Grafana · Linux
Background
Computer-science training, production backend ownership, and research discipline.
Dec 2024 — Present
BRAC IT Services Ltd. · Dhaka, Bangladesh
Backend engineering for CRM, ticketing, workflow, and messaging-heavy systems.
2024
Chittagong University of Engineering and Technology (CUET)
CGPA 3.59 / 4.00
2024
Machine-learning fraud detection and an IEEE-published insurance-awareness application.
Academic portfolio ↗Contact
I am interested in Java/Spring backend roles involving distributed workflows, reliability, data consistency, security, and production-scale systems.