Full Stack Developer · Dhaka, Bangladesh
Md Shamim Hossain — Full Stack Developer
Shipping production Laravel with measurable impact, building APIs that don’t page you at 3am, solving one bug at a time, teaching Postgres, queues and caches to behave.
Full stack developer specialising in Laravel, Livewire, and developer tooling. I care about the boring parts: migrations that are reversible, queries that scale, and interfaces a new teammate can understand on their first day.
09
Years engineering
30+
Systems shipped
40M
Requests served monthly
12
Engineers mentored
02
Why Hire Me?
Your Ideas, My Engineering Focus.
I build reliable, scalable and maintainable web applications using Laravel and PHP. From APIs to full systems, I focus on clean architecture, real solutions and long-term value.
- Laravel & PHP Core Specialization
- APIs & Integrations Connect & Automate
- SaaS & Web Apps Scalable & Maintainable
-
Backend Engineering
Clean, secure & maintainable code
-
API Development
Integrations & third-party services
-
Scalable Architecture
Modular & future-ready applications
-
Automation & Tools
Save time with efficient workflows
-
Quality & Reliability
Testing, validation & clean structure
-
Client & Team Focus
Clear communication and real solutions
For Companies
An engineer who thinks beyond the ticket. I bring problem-solving, clean architecture and a focus on long-term maintainability.
For Clients
Your requirements, my engineering focus. From ideas to production-ready solutions, I build with clarity, quality and care.
Thinking explorer
03
How this mind works
The demonstration behind the sheet above. Two thinking modes, six disciplines, one connected model — hover a discipline to preview it, select one to open its map.
Thinking mode
System 1 — Fast thinking
Rapid recognition and pattern matching: the calls that arrive before the reasoning does. Signals move fast, short and constant.
Motion reduced by your system setting
-
System 1 — Fast thinking
Rapid recognition and pattern matching: the calls that arrive before the reasoning does. Signals move fast, short and constant.
-
System 2 — Deep thinking
Deliberate reasoning: architecture, trade-offs, debugging under pressure. Signals travel long chains, in sequence, slower.
Select a node to read the practice behind it.
04
AI Workflow
From task trigger to cloud deployment. Coordinate AI agents, track execution, and visualize your entire software delivery pipeline.
Autonomous Engineering
Active agents
08
Tasks completed
248
Success rate
98.6%
5 active
- Task Trigger — Capture ideas & issues
- AI Planning — Analyze & plan solution
- Multi-Agent Encoding — Parallel code generation
- Review & Testing — Verify quality & security
- Cloud Deployment — Release to production
Development Pipeline
AI-powered task orchestration
No tasks
Fully automated demo — the pipeline runs itself in your browser; steer any card by hand.
7 tasks · 1 at deploy
Agent Collaboration
Logic flow & orchestration
- Task input feeds the orchestrator, which fans work out to the agents below; every agent hands its result to deployment.
- Research Agent — Analyzes codebase (Active)
- Planner Agent — Builds implementation plan (Active)
- Coder Agent — Writes & refactors code (Active)
- Tester Agent — Runs automated tests (Active)
- Review Agent — Reviews code quality (Active)
Active — handoff in flight
Idle
Blocked — waiting on a human
Agents running
05
Parallel jobs
12
Pipeline health
Healthy
Execution Logs
Demo stream
Waiting for next event…
Coordinate agents, automate testing, and ship with confidence.
Explore workflowHow I work
05
Two systems, one engineer
Every ability below belongs to one of the two systems: the fast one that spots the shape, and the deliberate one that decides what the shape costs. Hover a hemisphere to preview it; click one to open its cards.
System 1
System 1 — Fast thinking
3 disciplines
-
Rapid Prototyping
Sketch the shape before the shape is a commitment. A throwaway slice that proves one assumption beats a plan that proves none.
-
Pattern Recognition
Most failures are a known shape wearing a new costume. Naming the shape is most of the diagnosis.
-
Quick Debugging
Bisect, instrument, read the plan — narrow before you fix. The fastest debug is the one that rules things out.
fast path deliberate path
System 2
System 2 — Deep thinking
3 disciplines
-
System Architecture
The shape of the whole thing, and the order the parts are built in. Boundaries before implementations.
-
Database Engineering
The part that outlives the framework. Schema, indexes and query plans are the long-lived decisions.
-
Security & Performance
Threat-model the trust boundary, not the endpoint. Authorisation is a property of the flow.
- Primary stack
- Laravel, PHP 8.5, PostgreSQL, Redis
- Comfortable in
- TypeScript, Go, Kubernetes, Terraform
- Worked on
- Payments, developer tooling, public APIs
- Based in
- Dhaka, Bangladesh
- Experience
- 15 years
The defaults underneath all of it
-
01
Make the wrong thing hard to do
A convention nobody can violate beats a convention everyone agrees with. Constraints that live in the type system, the query layer, or the build pipeline keep working when the team is tired.
-
02
Read the query plan before arguing about the abstraction
Most performance debates are really debates about measurements nobody took. The database will tell you what is slow if you ask it directly.
-
03
Write it down while the reasoning is still recoverable
An architecture decision record costs twenty minutes and saves the next engineer a week of archaeology. The value is not the decision — it is the constraint that forced it.
-
04
Delete code before adding a flag
Every configuration branch doubles the surface you have to test. Most features are not optional; they are just unloved, and the honest move is removal.
-
05
Optimise for the second year
Shipping is the easy part. Almost everything that makes a system expensive later was a reasonable decision made in the first month.
-
06
Leave the codebase friendlier than you found it
Not a rewrite. One clearer name, one test that was missing, one comment that explains why rather than what.
06
Capabilities
Where the years went — production depth across the Laravel platform and the tooling that surrounds it.
07
Experience
My professional journey
Company
Lattice Systems
Full Stack Developer
Jun 2025 – Present- Settlement platform — own the event-sourced accounting core behind multi-currency settlement, having replaced a nightly reconciliation batch with a database-backed projection.
- Laravel PostgreSQL Redis Horizon
- Public API platform — designed the query-budget layer that retired a recurring timeout incident class by failing builds, not customer requests.
- MySQL OpenTelemetry Kubernetes
- Developer tooling — author the internal service-scaffolding CLI that makes the platform conventions the path of least resistance for every new service.
- PHP Symfony Console GitHub Actions
Company
Northbrim Digital
Senior Backend Engineer
Jun 2023 – Jun 2025- Multi-tenant platform — owned queue design and backpressure for ingestion workloads, moving slow-path jobs behind explicit budgets instead of retries all the way down.
- Laravel Redis Horizon Redis Streams
- Led the observability rollout: structured logs, traces, and the dashboards that answer what is slow without a debugging session.
- OpenTelemetry Sentry Grafana
- Mentored engineers across three product teams — design reviews, decision records, and the query-plan sessions that settled most performance debates.
- PostgreSQL EXPLAIN
Backend Engineer
Jun 2021 – Jun 2023- Rebuilt the reporting layer around indexed read models, cutting the heaviest monthly report from minutes to seconds without touching the transactional schema.
- PostgreSQL MySQL Redis
- Extracted the first service boundaries out of a growing monolith — REST contracts with versioning discipline the frontend teams could build against.
- Laravel REST PHPUnit
Company
Ravenport Labs
Software Engineer
Jul 2017 – Jun 2021- Built and ran the catalogue and checkout services of an e-commerce platform through two Black-Friday-scale peaks.
- PHP MySQL Elasticsearch Varnish
- Introduced automated testing to a codebase that had none — the suite that eventually let deploys happen on a Friday.
- PHPUnit GitHub Actions
08
Selected work
Some things I've built — each with the decisions and the documentation behind it.
Atlas Ledger
Double-entry accounting engine handling multi-currency settlement for a payments platform.
Laravel
PostgreSQL
Redis
Horizon
Cut month-end reconciliation from 6 hours to 11 minutes by replacing a cron-driven batch with an event-sourced projection built on database-backed queues.
Meridian API
Public REST API serving 40M requests a month across three product teams.
Laravel
MySQL
OpenTelemetry
Kubernetes
Reduced p95 latency from 840ms to 190ms and eliminated a recurring incident class by introducing a query-budget layer that fails builds, not requests.
Forge CLI
Internal developer CLI that scaffolds services with migrations, CI, and observability pre-wired.
PHP
Symfony Console
Docker
GitHub Actions
Brought new-service bootstrap time from two weeks of copy-paste to under an hour, and made the platform team's conventions the path of least resistance.
QueueLens
Open-source metrics exporter that turns Horizon queue telemetry into Prometheus dashboards.
PHP
Prometheus
Redis Streams
Grafana
Gave platform teams a queue-depth SLO out of the box; adopted by four internal teams in its first quarter and now shipped with the default platform image.
P·05 — Design & build
DevFolio
The site you are reading: an editorial portfolio, blog, community feed, marketplace, Developer Lab and Ideas platform in one Laravel application.
Laravel 13
Livewire 4
Tailwind 4
Flux UI
Pest
One codebase carrying six public products, a Livewire-first architecture, and a test suite that treats the interface as the contract — documented from the route map down to the last component.
09
Recent writing
Proof the thinking happens in public
01 06
Databases
The N+1 Query You Ship Every Sprint
Nine out of ten performance regressions I have diagnosed in production were the same bug wearing different clothes: an unloaded relation inside a loop that nobody noticed because the staging database has 40 rows.
- Laravel
- Postgresql
- Eloquent
- Performance
Databases
Stop Using Publish Timestamps as Ordering Keys
Sorting by published_at looks correct until two posts share a timestamp, and then pagination starts silently duplicating and dropping rows.
- Postgresql
- Eloquent
- Performance
Frontend
Server-Driven UI Is Not a Downgrade
The reflex to reach for a SPA has a cost most teams never price in: a duplicated domain model and a second place for authorisation to be wrong.
- Laravel
- Livewire
- Alpine Js
- Api Design
Backend
Your Queue Retry Policy Is a Data Loss Bug
Retrying a non-idempotent job turns a transient network blip into a duplicate charge. The fix is not more retries; it is making the job safe to run twice.
- Laravel
- Queues
- Horizon
- Concurrency
Databases
Reversible Migrations Are a Team Sport
A down() method that drops the column it just created is not reversible. It is a rollback that loses data, which is worse than no rollback at all.
- Postgresql
- Mysql
- Ci Cd
- Deployment
Databases
Indexes Are Not Free and Your Write Path Knows It
Adding an index makes one read faster and every write slower. Most teams only ever measure the first half of that trade.
- Postgresql
- Performance
- Observability
10
Contact
Open to full stack developer roles
The fastest way to reach me is email. I read everything and reply to most things, though not always quickly.