Co-Founder
Rafid Mohammed
Co-Founder · Chief Design Officer
Design systems partisan. Shapes how Amirus looks, feels, and moves.
Product DesignDesign SystemsBrand
◆ AMR / STUDIO / EST. 2017
SIX PEOPLE · THREE CO-FOUNDERS · DHAKA + REMOTE
A studio for the long-form
work most agencies skip.
Amirus was started in 2017 by engineers who wanted to build software the way serious architects build buildings — in the open, measured, owned. Nine years later, we are a studio of six, in Dhaka and wherever the network has pulled us. This page is the honest version of what we are.
§ 01 — What we believe
Six tenets. We rewrite them every year — these hold for 2026.
(01)
Legible beats clever
A system a junior engineer can reason about is worth more than a system only one person can maintain. We optimize for the handover, not for the commit graph.
(02)
Prototype in production code
We do not ship Figma screens as specification. If a decision matters, we prototype it in real code against real data, then discuss. Lorem never leaves our machines.
(03)
Own the runbook, not just the repo
Every engagement ends with docs, architecture diagrams, deploy procedures, and an on-call schedule. If you can't run it without us, we haven't finished.
(04)
Instrument the promise
Latency, uptime, and error budgets are not acceptance criteria — they are the product. We publish dashboards for every system we operate.
(05)
Small teams, end-to-end
Four engineers on one problem will ship faster than twelve on six problems. We staff thinly on purpose; every person on your engagement can ship to production.
(06)
Say no generously
We turn away more work than we take. If we don't have the taste for your problem, we say so and refer you to someone who does. This is part of the deal.
§ 02 — Timeline
Nine years, in chronological order.
2017
Founded in Dhaka
One room. First client.EST. 2017
Started to build software the way serious architects build buildings — in the open, measured, owned. First client: a family-owned exporter.
2019
First retained client
From fixed-bid to retainersMODEL · RETAINER
First proof the studio model worked — long-term retained work instead of fixed-bid project churn. Carried a pager for the first time.
2020
Remote-first reorg
Pandemic, distributed teamMODE · ASYNC
Rebuilt our operating cadence around written communication, async reviews, and weekly in-public demos. Never looked back.
2023
Applied-AI practice
Evals before demosPRACTICE · APPLIED AI
We stopped pretending "AI" meant wrapping prompts. Built an internal eval harness and shipped our first RAG-backed product.
2025
Operations wing
On-call, formalizedOPS · ON-CALL
Formalized the operations side of the studio — we carry the pager for the systems we still run, with dashboards shared privately with each client.
2026
Amirus Labs kicks off
Small product experiments, no clientsLABS · INTERNAL
An internal bet: a small research arm funded by studio profits, exploring tools we wish existed.
§ 03 — The team
Six people. Three co-founders. Senior on average.
Small, end-to-end, accountable. Every person on your engagement can ship to production — no juniors shipping alone, no hand-offs to people you've never met.
Co-Founder
Shakil Ahmed
Co-Founder · Chief Operating Officer
Operating cadence and delivery rhythm. Keeps every engagement on rails.
DeliveryOperationsProcess
Co-Founder
Amantu Khan
Co-Founder · Chief Technology Officer
Backend architecture and engineering lead. Owns the pager.
BackendArchitectureCloud
Ragib Intiser Shoumik
Lead Frontend Engineer
UI engineering specialist — where pixel-craft meets performance budgets.
UI EngineeringSveltePerformance
Mohammad Zabir
Chief Marketing Officer
First conversation with every client. Owns the funnel end to end.
GrowthSalesPartnerships
Mashiur Ahmed Hridoy
Associate Full-Stack Engineer
Full-stack with a frontend lean. Newest to the studio, hungriest to ship.
FrontendFull-StackUI
Join the studio.
We hire for depth and taste. Senior on average, no juniors shipping alone.
§ 04 — How we work
The shape of a studio week.
A representative board — not a live feed. The cards are modeled on how work actually moves through a week here and advance on a timer to show the flow; real boards stay private to each engagement.
§ 05 — How we hire
Slow. Suspicious of polish. Obsessed with taste.
- 01 No take-home tests We pair on a real problem from a real engagement, on the clock, paid.
- 02 Read your code, not your CV A commit history tells us more in 20 minutes than a CV does in 2 hours.
- 03 We hire for depth One thing, very well, with opinions. Generalists come later, in the third year.
- 04 Writing matters Async-first means your RFC, your runbook, your post-mortem carries the weight. We grade on clarity.
- 05 Taste is the tiebreaker At the end, we ask: would I be proud of the last thing this person shipped? Yes or no.
We are a studio, which means we are an argument about how software should be made. Nine years in, the argument holds: small teams,end-to-end, legible,measured . Everything else is scaffolding.
— The Amirus co-founders FILED / INTERNAL / v2026.03
Work with us, or for us.
Currently hiring — 2 senior engineers, 1 designer · Accepting 2 engagements for Q3/Q4 2026
Get in touch ◆ Tweaks
Accent
Logo variant