Backend engineer — Jakarta Backend Engineer

Systems that hold under load.

Backend engineer building data-heavy services: POS and ERP integration, financial reconciliation, and forecasting that operations can plan against.

Selected work

Case study 02 Schema design, full stack

jowarung POS

A retail business ran purchasing, stock and cash across spreadsheets, so cost of goods and the real stock position were both estimates.

Role
Schema design, full stack
Stack
Next.js · Prisma · PostgreSQL · Tailwind CSS · Cloudflare R2

A Next.js and Prisma application on Postgres covering purchase orders, an inventory ledger with stock opname, sales transactions, cash movements, and price plus cost history, with an audit log on every write.

Case study 04 Full stack

PhotoBox

Event photo booth sessions ended with guests waiting for someone to copy files off a laptop.

Role
Full stack
Stack
Next.js · Supabase · Tailwind CSS · Resend · QR codes

Next.js on Supabase for database and storage. Sessions hold their photos, a QR code per session and an email download link hand them to guests, and the download page needs no account.

Case study 05 Full stack, multi-tenant

Invitation Platform

Invitations sent as a static image cannot collect RSVPs or keep a guest list in one place.

Role
Full stack, multi-tenant
Stack
Next.js · Prisma · NextAuth · Radix UI · zod

Next.js with Prisma and NextAuth: themes per invitation, a guest list with RSVP, comments and an event schedule, with forms validated end to end by zod and React Hook Form.

Capabilities

  • Backend Systems

    Node.js services with a clean controller and service split, REST and webhook integrations, and background workers that survive a restart.

    • Node.js
    • Express
    • Workers
    • REST APIs
  • Data & Databases

    SQL-first modelling and query work across MySQL, Postgres and ClickHouse, from schema design through aggregation at volume.

    • MySQL
    • MariaDB
    • PostgreSQL
    • Prisma
    • ClickHouse
  • Financial & Reconciliation

    Money flows that have to balance: purchase and sales ledgers, cost history, and exports that tie back to the source system.

    • Reconciliation
    • Ledgers
    • ERP Integration
    • Reporting
  • Pipelines & Export

    ELT into the warehouse, dbt marts, and the formatted outputs operations asks for: XLSX, CSV and PDF pipelines.

    • dbt
    • ClickHouse
    • XLSX
    • CSV
    • PDF
  • Infrastructure & Delivery

    Containers, object storage and CDN delivery, with the unglamorous parts handled: migrations, backups and repeatable deploy paths.

    • Docker
    • Cloudflare R2
    • Vercel
    • NAS and WebDAV
  • Product & Interfaces

    Type-safe interfaces over the same data: Next.js applications, BI dashboards, and the admin screens an ops team actually uses.

    • TypeScript
    • Next.js
    • Tailwind CSS
    • BI Dashboards

Working stack

Stack

  • Node.js
  • TypeScript
  • MySQL
  • PostgreSQL
  • ClickHouse
  • Docker
  • Cloudflare
  • Next.js
  • Python
  • Redis

Approach

  • Reliability

    Systems that hold under pressure, not just in a demo.

  • Clarity

    Code the next engineer can read, extend and trust.

  • Consistency

    Steady progress over bursts of unfocused effort.

  • Curiosity

    Actively exploring new tools and better approaches.

Contact

Open to backend and data engineering roles, and to contract work on systems that have to be right: ledgers, reconciliation, integrations.