Md Abdullahil Shafi

About me

Software engineer and technical leader with about ten years of experience building SaaS and web products — nine full-time, plus a part-time start while finishing university. Primarily backend, platform and distributed systems, but I have worked across the full stack throughout my career.

I have repeatedly taken ownership beyond a narrowly defined engineering role: designing architecture, leading implementation, mentoring engineers, working directly with customers and stakeholders, improving developer experience, recovering troubled projects, and owning products from idea through maintenance.

SaaS product engineeringBackend & platform engineeringDistributed systemsEvent-driven architectureMicro-frontendsData ingestion platformsReliability & performanceDeveloper experienceLLMs & AI agents

The arc

About ten years building software — roughly four of them leading engineers, the rest building the systems that leadership is accountable for.

  1. TestReach

    Senior Software Engineer — reporting, data ingestion and reliability platform work.

    Dev lead → platform authority

  2. Durbin Labs · EM

    Engineering manager — recovered the missed projects, rebuilt the team.

    Engineering manager

  3. Japan Travel

    Full-stack engineer — Laravel, Vue and the 100/100 Lighthouse challenge.

    Full-stack engineer

  4. Durbin Labs

    Software Engineer — commercial SaaS across healthcare, education and restaurants.

    Implementer → project lead (restaurant SaaS, team of 5)

  5. BUET

    B.Sc. in CSE — internships, part-time and volunteer code while studying.

    Implementer

MyDokan, my own product, runs in parallel as an independent track — see Products. Role-by-role detail, stacks and achievements live on the CV.

The systems I design & own

A simplified view of how the platform systems I've designed and owned at TestReach fit together — from service instrumentation up to customer self-service. The stories behind these numbers are told in full in the case studies.

+------------------------------------+
|  microservices (Node/TypeScript)   |
+------------------+-----------------+
                   |   type-safe ingestion library
                   |   (designed for engineers)
                   v
+------------------------------------+
|  SQS event queues                  |
|  retries / backoff / fairness      |
|  ~60% fewer processing failures    |
+------------------+-----------------+
                   v
+------------------------------------+
|  DataLake                          |
|  ~2-2.5M ingestion events / day    |
+------------------+-----------------+
                   v
+------------------------------------+     +--------------+
|  self-service reporting            |<----|  customers   |
|  templates ship in ~2 min, 20+ GB  |     +--------------+
|  streamed to S3, ~half the infra   |     self-serve, no
+------------------------------------+     engineering queue

Proof, not promises

The Lighthouse story from Japan Travel, 2020–2021:

Lighthouse Performance: 100/100100Performance
Lighthouse Accessibility: 100/100100Accessibility
Lighthouse Best Practices: 100/100100Best Practices
Lighthouse SEO: 100/100100SEO

Met a COO's challenge for a perfect score at Japan Travel by building custom dependency tree-shaking tooling instead of optimizing by hand. This site is built the same way — static HTML, system fonts, no trackers.

Skills, grouped by depth

No percentage bars — depth is stated in words, with the context where each skill was used. This is also how I answer the question honestly in interviews.

Daily, deep

12 skills

The stack I reach for by default and know at the debugging level.

TypeScriptNode.jsNestJSPostgreSQLMongoDBRedisJestAWS(Lambda · ECS · SQS · SNS · S3)Event-driven architectureMicroservicesDistributed systemsSystem design

Strong, regular use

14 skills

Production experience I keep returning to.

React· Durbin Labs · own projectsNext.js· Durbin Labs · production projectsAngularJS micro-frontends· TestReachVue.js· Japan TravelLaravel · PHP· Japan TravelSupabase· MyDokanFlutter · Dart · Android· MyDokanDockerKubernetesServerless FrameworkElasticsearchExpressMeteorJS· Durbin LabsWebRTC· Durbin Labs

Working exposure

8 skills

Real work, bounded depth — stated plainly rather than padded.

Python(ETL level)Go(open-source tools, built with AI agents)GCPAzureC++Java· AndroidMySQLNuxt

Growing

3 skills

Where I am deliberately investing next.

LLM agents & agentic workflowsAI developer toolingModel Context Protocol (MCP)

Also across: Git & CI/CD · REST API design · Requirement & solution analysis · Laravel Blade · HTML/CSS.

Engineering philosophy

Engineering leverage

The best engineering investment is often not a customer-facing feature. Reusable libraries, automation, internal platforms and better developer workflows multiply the effectiveness of an entire organization.

Pragmatic architecture

Architecture should solve the actual problem and leave room for future evolution — never add distributed complexity simply because a system can support it.

Operational ownership

A system is not finished when it is deployed. Monitoring, debugging, failure recovery, cost management, security and maintenance are part of the job.

Developer experience

Engineers should not repeatedly solve the same integration problem. If a problem appears often enough, it is a candidate for a library, a platform, automation or better tooling.

Education

Bangladesh University of Engineering and Technology (BUET)

B.Sc. in Computer Science & Engineering

Let's connect

Open to senior/staff/lead engineering, platform architecture and technical-lead roles — and always happy to talk founding-engineer or early-stage CTO journeys.

Email meView résumé