payments backend, food reviewer, offlaner, idempotency nerd, engineering lead, senior backend engineer

Rega Halma Ruzty

Senior Backend Engineer · former Engineering Lead

product-minded. backend-deep. ships fast without breaking money.

I build backend systems that move money and can't afford to be wrong. 9+ years across fintech, banking, healthcare and enterprise: Node.js, TypeScript, PostgreSQL, distributed systems, and the boring parts that keep them correct, like idempotency, retries and reconciliation.

// impact

Numbers, not adjectives

9+

years building production systems

12mo

empty repo to production, business banking platform

100+

enterprise SMEs onboarded

10

engineers, team scaled and mentored

<100ms

a query that used to time out, after a CTE rewrite

~4x

weekly ticket output, from my own delivery process

// about

I didn't start in software

I studied animal husbandry, then spent three years running a breeding farm: 6 houses, 60,000 grandparent-stock layers producing day-old chicks, with a team of 12 workers and an assistant supervisor. Targets were daily and misses were expensive.

That's still how I build software. Find where the process leaks, measure it, fix it, and make sure the fix survives a bad day. Money-moving backends just raise the stakes.

play the full version of Chick Pen (opens in a new tab)

// experience

Where I've worked

  1. 2025 - now · Singapore, remote

    Senior Backend Engineer @ Littlelives

    • Multi-tenant workflows on NestJS, TypeORM and PostgreSQL, with safe rollouts
    • Bank GIRO collection and refund integrations with idempotency and reconciliation
  2. 2021 - 2025 · Singapore, remote

    Engineering Lead @ Grof

    • Led a business banking platform from an empty repo to production in 12 months
    • Grew the team to 10 engineers; replaced manual deploys with GitHub Actions
  3. 2021 · Jakarta, remote

    Full-Stack Developer @ Bithealth

    • Healthcare web apps for clinical staff, API contracts to hospital platforms
  4. 2019 - 2021 · Jakarta, remote

    Full-Stack Developer, Squad Lead @ Multipolar Technology

    • White-label mobile banking platform for 2 banks: ISO 8583, video KYC, Kafka
  5. 2017 - 2018 · Bandung

    Full-Stack Developer @ Tabel Data Indonesia

    • Ported DB2 query logic to Java for a multithreaded bank clearing batch
  6. 2014 - 2017 · Operations Supervisor @ Charoen Pokphand. the short version →

// selected work

Case studies

fintech · lead · 2021-2025

A business banking platform from an empty repo

problem
An idea, no code: business accounts, free international transfers and virtual corporate cards for SMEs.
approach
Shaped the technical requirements, set up AWS and CI/CD myself, modular monolith on Nium for transfers and cards, KYC for people and KYB business-profile checks via Cynopsis Artemis.
result
Production in 12 months, 100+ SMEs onboarded, team grown to 10.
Next.jsNodeMongoDBAWSNium

delivery · process · 2026

Shipping full-stack tickets 4x faster

problem
One API ticket used to take me 2-3 days, mostly testing it myself before I trusted it.
approach
A tested, recorded delivery process I built, with my sign-off at each step and evidence behind every change.
result
About 4x my old weekly output: 200+ tickets in 4 months. Each one now spans API, web and often mobile, with every case on recording.
Claude CodePlaywrightPostgreSQL

banking · architect

White-label mobile banking

problem
Two banks, one platform, core banking and video KYC.
approach
Independent modules, ISO 8583 core integration, Kafka events, Jitsi video calls.
result
Shipped for 2 enterprise banks.
FeathersJSKotlinKafka

payments · backend · now

Backends that never double-charge

problem
Bank GIRO collections and refunds, plus migrations on data that can't be wrong.
approach
Idempotency keys, queued retries, reconciliation; parallel-run validation before every cutover.
result
100% data integrity across production migrations, each one validated by a parallel run before cutover. Zero-downtime releases.
NestJSPostgreSQLRedisNSQ

internal tools · now

Ops answers "what happened?" without an engineer

problem
Every stuck record or odd status meant pinging an engineer or PM.
approach
17 Retool tools across the app's modules that show live status, triage the issue and retry failed processes.
result
Operations and Customer Success reach a conclusion on their own.
RetoolPostgreSQLREST

// how it works

The patterns behind the work

01/04 · payments

A retry that never double-charges

$ Press play to watch the naive version break, then switch to the fix.

illustrations of common patterns, not simulations · ← → to switch

// projects

Side projects

~/regahr/hierarchical-locations-api

Hierarchical Locations API

REST API for infinitely nested location trees, with automatic parent detection and recursive reads.

NestJSPrismaPostgreSQL

~/denrose.store

Denrose

Storefront for handmade clay earrings, with a CMS for the catalogue and a 3D clay earring.

Next.js 14SanityThree.js

~/regahr/doc-gen

Doc Gen

Turborepo monorepo for DOCX to PDF conversion, S3 storage and e-signing via Docuseal.

NestJSNext.jsS3Turborepo

~/regahr/appointment-api

Appointment API

Scheduling API with slot constraints, documented system and database design.

NestJSTypeScriptSQLite

// stack

What I work with

backend
Node.jsNestJSExpressTypeORMREST
data
PostgreSQLMongoDBRedisquery tuningmigrations
distributed
NSQKafkaidempotencydistributed locksreconciliation
cloud & ops
AWS ECS/EC2/S3DockerGitHub ActionsGrafana
frontend
ReactNext.jsTypeScript
tooling
Claude CodeCodexworkflow orchestration
certified
MongoDB C100DBAMongoDB C100DEV

// co-zzle

Puzzle of the day

loading.js

 

Hiring for senior backend or payments?

Email me