Backend engineer.
I build for the messy parts.

Systems that deal with retries, partial failures, human judgment, and AI uncertainty without hiding the hard edges.

Selected work Professional experience Email me

Backend systems Security & user management Developer tooling Applied AI

Selected work

A few systems worth opening up.

Projects where architecture, product behavior, and operational constraints are part of the same problem.

01 / Household finance

Richmod

A self-hosted household finance system that turns emails, Telegram messages, and documents into an auditable ledger. The model interprets evidence; deterministic application code owns financial state.

View Richmod on GitHub

State PostgreSQL is the source of truth

AI boundary LLM output is untrusted input

Uncertainty Human review instead of guessing

Stack Go · Next.js · PostgreSQL

Agenticform

Agent orchestration

A Java control plane for multiple Codex agents across local and remote execution nodes, with durable tasks, approvals, policy gates, isolated workspaces, and recovery semantics.

Java · Go · React

Viral Clipper

Applied AI experiment

A video pipeline that transcribes long-form footage, scores candidate moments, renders vertical clips, and feeds real performance data back into its ranking model.

Java · Python · Next.js

Professional systems,
without the private internals.

At DANA, my backend work spans Security and User Management: identity and verification, authentication and account lifecycle, risk controls, and recurring payments.

Public capability map only. Architecture, vendors, production metrics, thresholds, and proprietary decision logic stay private.

Open public résumé LinkedIn

DANA Indonesia 2022 — now

Backend engineering

Security +
User Management

Production systems across security and user-facing account domains, with explicit failure behavior, controlled rollout, operational recovery, and compatibility with existing services.

Java · Spring · OceanBase · Kafka Public scope / NDA-safe

Identity & verification

Biometric and liveness verification, OTP, KBA, passkeys, and verification integrations.

Authentication & lifecycle

Risk & abuse controls

Device and abuse signals, distributed controls, staged rollout, and operational tooling.

Recurring payments

Recurring execution, interval-aware behavior, timeout handling, and bounded retries.

2018 — 2019 Majapahitech

Android · wearable telemetry

2019 — 2022 Beehive Drones

Backend · IoT · drone operations

2022 — now DANA Indonesia

Security · user management · payments

Software should make its boundaries obvious.

Correctness before cleverness.

Use probabilistic systems for interpretation, not as an excuse to make critical state transitions unpredictable.

Failure behavior is product behavior.

Retries, idempotency, recovery, and explicit ownership belong in the design, not in a cleanup sprint.

Operate what you build.

Deployment, observability, and security boundaries should be visible while the architecture is still easy to change.

Working set

The technologies that show up repeatedly in the systems I build.

Backend

Java · Spring · Go · PostgreSQL · Kafka

Product

TypeScript · React · Next.js

Operations

Docker · Linux · Cloudflare · GitHub Actions

Building something with sharp edges?

raufimusaddiq@gmail.com

Backend engineer.I build for the messy parts.