Full-stack developer · Dhaka, Bangladesh
I BUILD FOR Real-world needs.
I connect thoughtful interfaces with the systems behind them. With 4+ years across React, TypeScript, Laravel, and PHP, my work spans travel platforms, payments, cloud media, and AI-powered workflows. The goal stays the same: make complex products feel dependable and straightforward to use.
02 / The human side
Behind the code is someone who likes connecting the dots: between a person’s needs, a product’s constraints, and an idea that could make the whole experience better.
01 / Personality
I like understanding the whole problem, not just my corner of it. From the first screen to the background job, I care about clear decisions, maintainable code, and the details people notice when something feels right.
02 / Curiosity
Working on AI image classification and virtual try-on made me curious about what software can see and create. That curiosity now takes me from backend languages to WebGL, shaders, and 3D experiments.
03 / Motivation
A booking should feel clear. A payment should be accounted for. A useful tool should save someone time. Those everyday moments are what motivate me to turn complex requirements into dependable products.
What keeps me moving
Understand the problem. Own the details. Keep getting better.
Users / illustrative scale
Sustain
Keep releases, integrations, and background work dependable.
An illustrative journey from first commit to one million users, not a claim about the audience of my projects.
Travel products have taught me to think beyond the screen: supplier latency, payment state, queue failures, and data freshness all shape the experience. Good architecture makes those moving parts easier to understand and improve.
Illustrative progression: build at zero users, ship to the first users, scale, optimize, and sustain at one million. Scroll to explore the connected system.
Conceptual architecture / scroll to connect the system
How the work actually happens
01 / The process
Start with the person, the workflow, and what can go wrong.
A hotel search, a payment callback, or a media upload each has different constraints. Understand the need, the dependencies, and the failure states before choosing a solution.
02 / The process
Connect the experience before adding the complexity.
Map interfaces, data relationships, API contracts, and background work. Make business rules and ownership clear so a change in one service does not become a surprise somewhere else.
03 / The process
Make the interface clear and the system dependable.
Bring React and TypeScript together with Laravel, validated APIs, efficient queries, and queues. Keep the code readable, test the important paths, and handle the states beyond the happy path.
04 / The process
Deliver carefully. Learn from what happens next.
Use version control and CI/CD to support reliable releases. Follow the slow requests, failed jobs, and user feedback, then improve the product without making it harder to maintain.
04 / Built through experience
October 2025 — Present
Full-Stack Developer
Building the systems behind hotel bookings and airport transfers: supplier integrations, real-time search, payments, queues, and the customer experience that connects them.
October 2024 — October 2025
Full-Stack Developer
Built media-heavy applications and internal business tools, combining cloud storage, real-time updates, automated delivery, and AI-powered visual experiences.
December 2022 — September 2024
Frontend Developer
Turned product requirements into responsive React and Next.js interfaces, with a focus on state management, real-time feedback, performance, and interaction design.
05 / What I use
The languages, frameworks, and services behind my work. Select a discipline to explore how the pieces connect, from customer-facing interfaces to the infrastructure behind them.
Five disciplines. Shared purpose.
01 / Frontend
From customer-facing travel flows to internal tools, I build responsive interfaces with JavaScript, TypeScript, and a component-driven approach.
Component-driven interfaces and product experiences
Additional frontend frameworks in my toolkit
Interactive behavior and typed application code
Application routing and server-state workflows
Application state and data fetching
Transitions and scroll-based interaction
From semantic HTML and CSS to state, data, and interaction.
06 / What I’ve solved
Real product work means connecting the parts that rarely appear in a screenshot: hotel imagery, payment state, background jobs, discovery pages, and the rules behind customer rewards.
VervTrip / AI image classification
A collection of 6M+ hotel images across 400k+ hotels needed automated classification to make the visual content more useful for the product.
Developed an AI-powered image-classification pipeline using Gemini 2.5 Flash Lite, connecting model processing to the hotel image workflow rather than treating each image as a manual task.
At this volume, model cost, throughput, and output quality all matter. Classification needs to fit the data pipeline, not become another bottleneck.
VervTrip / Booking and payment reconciliation
A payment event and a supplier booking response do not always arrive together. Checkout needs a clear account of what was paid, what was booked, and what still needs reconciliation.
Connected booking and payment workflows with transaction records, validated API responses, webhook-based confirmations, and background reconciliation work.
A successful payment is not the same as a confirmed reservation. Keep those states distinct so delayed responses and exceptions can be handled without misleading the customer.
VervTrip / Queues and asynchronous processing
High-volume image processing, booking follow-up, and payment-related work should not make the customer wait for every task to finish in a single request.
Built backend services, background jobs, queue processing, and Redis-based caching to move longer-running work out of the immediate user journey.
Moving work into a queue changes when it completes. Failures, retries, and job state need as much attention as the request that started the work.
VervTrip / Dynamic hotel pages
Travellers look for hotels by city, popular place, and brand. A growing catalogue needs to support those entry points without maintaining every page by hand.
Built dynamic hotel pages that reuse hotel data and page structure while adapting the content and results to cities, popular places, and hotel brands.
Reusable templates should not make every destination feel interchangeable. Keep the place-specific context and hotel information useful as the catalogue changes.
VervTrip / Cashback and wallet engine
Cashback is more than a number at checkout. Eligibility, campaign rules, wallet transactions, and abuse prevention all need to work together.
Developed automated cashback and wallet functionality around campaign rules, transaction processing, fraud detection, and analytics.
Reward flexibility cannot come at the expense of clear accounting. The engine needs understandable rules and transaction records as campaigns evolve.
VervTrip / Coinbase Commerce
Adding crypto payments introduces another provider and confirmation lifecycle, but the customer still needs a clear and secure booking experience.
Integrated Coinbase Commerce into payment workflows, connecting provider events, webhook confirmations, and application transaction state.
A provider callback is only one part of the flow. Validation, confirmation state, and booking reconciliation still need to agree before the application treats the journey as complete.
Maps integrations / Google Places API
Place lookups can become an expensive, tightly coupled dependency when the same information is requested repeatedly or too early in a user flow.
Optimized Google Places and Maps API usage by reducing repeated requests, reusing relevant results, and reviewing where the product actually depends on external place data.
Request reduction should preserve useful, current information. Cache and lookup boundaries need to follow the workflow and the provider’s data-use requirements.
07 / What I’m exploring
Production work gives me practical questions. Experimenting gives me new ways to answer them: through real-time visuals, 3D craft, backend languages, and AI.
WebGL / Three.js / shaders
Exploring WebGL, Three.js, and React Three Fiber through shaders, particles, lighting, and scroll-driven scenes. I’m interested in motion that gives an interface atmosphere without getting in the way.
How can a real-time scene feel expressive and still leave the interface fast and usable?
Keep experimenting with shader materials, GPU-friendly particles, render budgets, and reduced-motion alternatives.
3D modeling / visual craft
Learning how form, topology, materials, and light work together in 3D modeling, then bringing those assets into an interactive browser experience.
What makes a 3D asset convincing before it becomes expensive to render?
Explore cleaner geometry, UVs, texture quality, lighting, and asset optimization so the model and the real-time scene are designed together.
Backend languages / AI
Alongside my day-to-day PHP and Laravel work, I’m learning Java, C#, Rust, and Python and exploring how to integrate AI into complete backend workflows.
What can a different language teach me about building a clearer, more reliable system?
Build small services and AI experiments to compare type systems, concurrency, persistence, and API design, turning unfamiliar ideas into practical understanding.
08 / The next chapter
A booking flow that needs to work harder. An integration that needs to be reliable. An interface people should enjoy using. Let’s build the right system around your next idea.
Let's talk Explore my work