Shamimul Haque · Senior Software Engineer
Architecting Intelligent Systems. Engineering Business Impact.
I design and build scalable ERP platforms, secure backend systems, and enterprise solutions that simplify complex operations and deliver measurable business value.
- 10+ Years Experience
- Enterprise Architecture
- Technical Leadership
- Backend Engineering
- ERP Solutions
- Business Process Automation
- System Integration & APIs
- Scalable System Design
- Agile Delivery & Mentorship
About Me
A little about how I work
I’m Shamimul Haque — an Enterprise Software Engineer with 10+ years designing, building and leading the delivery of ERP systems and large-scale business applications. My work centers on software that powers real business operations: ERP platforms, inventory systems, workflow automation and enterprise portals that organizations depend on every day. I own the full lifecycle — translating complex business requirements into system architecture, leading development teams, and engineering for long-term...
Read Full StorySelected Work
A few projects, in depth
Not a project dump — each one links to the problem, the trade-offs, and what shipped.
How I Work
Principles, not platitudes
I write the doc before the code when a decision is hard to reverse
If a decision touches more than one team or would take weeks to unwind, I write a short RFC first — even a half-page one. It forces me to notice the trade-off I'm about to hand-wave past, and gives other people a cheap way to disagree before it gets expensive to.
In code review, I look for the missing test, not the different style
I don't block PRs over formatting or personal preference — that's what a linter is for. I block them when I can't find a test that would catch the obvious way this breaks, or when the change quietly expands what a function is responsible for.
Tech debt gets a line item, not a feeling
When I take a shortcut under deadline pressure, I write down exactly what it costs and when it'll bite — not just "we should fix this later." That's the only way it competes for real prioritization instead of living as vague guilt everyone ignores.
On-call is a design review that happens at 2am
Every incident gets a blameless write-up, but the part I actually care about is the follow-up ticket: what would have made this page not happen at all. If the same class of alert fires twice, that's a backlog item, not bad luck.
Ambiguity gets one clarifying question, not a guess or a meeting
When a ticket is vague, my first move is to write down my interpretation and the assumptions I'm making, then ask the person who filed it to confirm or correct it in writing — not to guess silently or block on a meeting.
Leadership
Beyond my own tickets
Wrote the onboarding guide new backend hires now go through
MentoringAfter the third new hire asked me the same four questions in their first week, I wrote a getting-started doc covering local setup, our deploy process, and "who to ask about what." It's now part of the standard onboarding checklist and has cut first-PR time for new engineers from about two weeks to four days.
RFC: splitting the monolith's reporting workload onto a read replica
RfcProposed and drove the design review for moving analytics queries off the primary database after they'd caused two production incidents. Got sign-off from both the data team and infra, and the migration shipped with zero downtime.
Sat on the backend hiring bar for two years
HiringInterviewed roughly 60 backend candidates and co-wrote our system design interview rubric, pushing us to stop over-indexing on whiteboard algorithms in favor of questions closer to the actual job: reading an unfamiliar codebase and reasoning about a real trade-off.
Changed how the team shipped: PR size limits and a same-day review norm
ProcessOur review queue regularly sat for 3+ days, so big PRs rotted and people batched even more into them. I proposed a soft 400-line PR guideline and a same-day first-response norm; review turnaround dropped to under a day within a month, without anyone being told to "just review faster."
What I Do
Skills & Technologies
The tools and technologies I use to bring ideas to life.
Frontend
4Backend
4Tools
3Services
How I Can Help
ERP & Business Systems
Inventory, production, HR, and accounts as one system instead of five spreadsheets. Custom ERP modules built around how your business actually runs, not how the off-the-shelf vendor thinks it should.
Web Application Development
Custom Laravel applications built to last. Clean architecture, optimised performance, and code your team can actually maintain — from MVP to enterprise platform.
API Design & Integration
APIs that other systems can rely on. Clean REST design, token-based authentication with Sanctum or Passport, and third-party integrations — payments, CRMs, mapping — built with proper error handling and logging.
Testimonials