Lead backend and platform engineer · fintech
I build the systems that turn messy financial data into regulated, pixel-perfect documents.
Lead developer of a white-label platform producing investment factsheets for 18 UK wealth managers. One engine, 91 PDF templates, hundreds of documents in a monthly run. The factsheet on this page is my own CV in that format: invented client brands, real numbers.
- 18
- firms served
- 91
- pdf templates
- 93/246
- commits, oxylabs sdk
- 5
- apps in production, solo
Muhammad Hamdan
Lead backend and platform engineerObjective
I lead development on a white-label platform that turns fund data into regulated PDF factsheets for 18 UK wealth managers. The rendering engine, the job queue behind it and the Excel import that feeds it are mine.
Career, 2022 to now
Risk profile
3 of 7. Ships fast, but reads the spec first.
Key information
| Role | Lead developer |
|---|---|
| Employer | Mabel Insights |
| In industry since | Jun 2022 |
| Based | Remote (UTC+5) |
| Clients | 18 firms |
| PDF templates | 91 |
Top holdings
By share of working time.
| TypeScript / NestJS | 34% |
|---|---|
| Python | 22% |
| PostgreSQL / Redis | 18% |
| React / Next.js | 14% |
| Go | 12% |
static render · meridian-wealththe brands are invented. the numbers are mine.
Selected work
The Factsheet Engine
White-label PDF platform behind 18 UK wealth managers: a firm uploads its fund data and gets back finished, regulated factsheets in its own brand. Under the hood: BullMQ fan-out and fan-in, a diff-based Excel importer, server-side D3 charts.
~50k LOC · 91 templatescase studyFitFlix
Class-booking marketplace in Vilnius. Built and run solo: five Next.js apps, NestJS and Prisma, Revolut payments, cross-app SSO. Live, with real studios on it.
production · fitflix.ltcase studyGambit
Spec-first autonomous trading system. Ten named invariants, three circuit breakers, crash-window order reconciliation. Paper-mode only, and the promotion gate is written into the spec.
733 tests · paper-modecase study
Inside the Factsheet Engine case study: the pipeline, running. Fan-out under a concurrency cap, one job failing and retrying with backoff, fan-in to a streaming ZIP. Press run.
Proof
Things you can check without taking my word for any of it.
- oxylabs-sdk-pythontheir org, top contributor
- fitflix.ltlive in Vilnius
- github.com/Rorrschachthe source
- in/muhammadhamdan1linkedin, the CV version
Other work
Oxylabs Python SDK
Top contributor on a real company's official SDK: 93 of 246 commits, in a codebase I did not own. They sit under hamdan-mslm, the account I worked from at Mslm, and the contributor graph is public.
open sourceTennistonic
Python automation for a live tennis site, including a YouTube to WordPress highlights pipeline with fuzzy entity matching. Shipped as an .exe so a non-technical client could run it themselves.
client workGoVan Movers
Next.js site for a moving company. Four-step quote wizard validated with Zod, plus Google Places and Trustpilot integrations.
client workReloGrab
Productized web and marketing service for moving companies. Mine, from scratch.
founded
About
Muhammad Hamdan is a lead backend and platform engineer. Muhammad Hamdan leads the white-label platform that generates regulated investment factsheets for 18 UK wealth management firms at Mabel Insights. His stack is TypeScript, Node.js, NestJS, PostgreSQL, Redis, BullMQ and AWS. He built and runs FitFlix, a class-booking marketplace in Vilnius, on his own. He is the top contributor to the official Oxylabs Python SDK.
I am a backend and platform engineer, fully remote. My day overlaps UK hours, which is how I ended up leading a platform for British wealth managers instead of working nights. I finished a CS degree at COMSATS in 2024, most of it while already working full time.
The part I care about is the unglamorous part. Retries that are safe to run twice. Caches that know when they have gone stale. Error messages that name the tab, the row and the column instead of saying something went wrong. A factsheet with a wrong number in it is a compliance problem, not a bug report, so most of my design decisions start from what happens when a thing fails rather than what happens when it works.
Off hours are chess and the gym. One explains the project names, the other explains why I built a fitness marketplace.