Abdurrahman Ramadhan
I design and build scalable web applications, mobile experiences, backend systems and AI-powered products — from the interface down to the infrastructure underneath it.
Selected Projects
Business teams drowned in unstructured documents and needed answers grounded in their own files, not a generic model.
The OCR + retrieval pipeline, the Langchain/OpenAI runtime, and the Google Cloud deployment with CI/CD.
Visit ↗Every game portal kept its own logins. Users juggled accounts and the team maintained auth in a dozen places.
A single SSO directory with JWT/opaque tokens, MFA (TOTP/WebAuthn) and passwordless auth, plus HA/DR, rate limiting and DDoS protection.
Visit ↗A venue wanted guests to run the room from their phones — songs, gifting and F&B — without downloads or friction.
The whole thing, solo: mobile UI/UX, the NestJS backend, an in-app gem economy processing 2k+ transactions a day, and CI/CD to 99.9% uptime across two venues.
Visit ↗The exchange needed live insight into TVL, pool liquidity and system health, plus an anti-abuse rewards layer.
A Go risk service monitoring TVL and liquidity, the rewards backend with rate limits and anti-abuse, and the wallet-connect rewards frontend.
Visit ↗Retail investors needed a compliant, reliable way to buy and track mutual funds on mobile.
Backend systems and scalable APIs on Google Cloud, database integrations across MySQL/MSSQL, and robust error handling supporting 50k+ users and 10k+ transactions a day.
Visit ↗A static résumé can't answer follow-ups. I wanted visitors to interrogate my experience directly.
The whole site and the assistant below — it runs against a local model, so nothing a visitor types leaves the machine, and answers are grounded in case-study notes I wrote myself.
Seven years, one line
Started on PHP and Laravel fintech, moved through Node, React and React Native, then into Go services, Web3 and AI runtimes. Since 2023 I run delivery as a technical project manager while still writing the hard parts.
Stack Depth
Bars are years in production, not self-assessed confidence.
Work Process
The same five steps whether the deliverable is a mobile app, an ERP module or an agent runtime.
Understanding goals, audience, constraints and what the system has to survive.
Choosing the boundaries: services, data ownership, and what stays boring on purpose.
Vertical slices shipped behind flags, reviewed against real data rather than fixtures.
Load, failure modes, observability and a rollback path before anyone calls it done.
Documentation, runbooks and a delivery cadence that keeps it moving without me.
Don't browse it. Ask it.
The assistant reads the same notes this page is built from. Ask about an architecture decision, a stack, or why I made a call — it answers with the project attached.
Let's work together ✳
I'm open to challenging engineering problems, ambitious products and remote roles. Usually replies within a day.