Career & Overview

Software Engineer in Jakarta: What I Actually Do, and Why I Work Across the Stack

A software engineer based in Jakarta working across Laravel, Node.js, React, and AWS — here's what that actually looks like day to day, and how I decide what to build.

Sapto Aji

Software engineer, Jakarta

Published
Reading time

"Software engineer" is one of those titles that means very different things depending on who's saying it. For some people it's writing backend services all day. For others it's pixel-perfect frontend work. For me, it's been both — and increasingly, that's the point.

I'm a software engineer based in Jakarta, Indonesia. My foundation is in modern JavaScript environments and AWS architecture, and I've deliberately spent the last stretch of time expanding into Laravel, Python, and Java. This post is the starting point for a series of write-ups on what that work actually looks like — the projects, the trade-offs, and the reasoning behind them.

Why work across the stack instead of specializing

There's a real argument for specializing deeply in one layer of the stack, and plenty of excellent engineers do exactly that. My reasoning for going broader is different: the projects I want to build and ship aren't frontend problems or backend problems in isolation — they're product problems that happen to need both.

A real-time queue system for a clinic needs a backend engineer's judgment about broadcasting and data consistency, and it needs a frontend that makes a waiting number feel instantly trustworthy. A vendor payment tracker needs backend logic for milestone-based calculations, and a frontend that makes financial state legible at a glance. Treating these as one discipline instead of two has made me a better engineer at both.

That said, working across the stack doesn't mean being shallow everywhere. It means:

  • Backend engineering: API design, real-time systems (Pusher, WebSockets), relational data modeling, and cloud architecture on AWS
  • Frontend engineering: React-based interfaces, state that stays consistent under real-time updates, and UI that doesn't fight the backend's data shape
  • Full-stack judgment: knowing when a problem needs a decoupled API and separate frontend, and when a simpler, tightly integrated approach (like Laravel with Livewire) is the right call for the actual scale of the problem

What I'm actually building right now

Rather than talk in the abstract, here's the current, real work:

  • AntreKlinik — a real-time queue management system for small clinics and salons, built with Laravel, Livewire, and Pusher. The engineering challenge here is backend-heavy: real-time broadcasting, consistent queue-position recalculation, and choosing managed infrastructure over self-hosted where it actually makes sense for the product's stage.
  • VendorPay — a vendor payment and down-payment tracker for event organizers, built with Node.js, React, and PostgreSQL, supporting both fixed and percentage-based payment milestones. This one leans more into frontend and data-modeling challenges: representing partial payment states clearly and keeping the UI trustworthy when money is involved.

Both were chosen for the same reason: they solve real problems for real small businesses, not just resume-filler demos. A project with genuine income potential forces different engineering decisions than a toy app does — you have to think about reliability, cost, and what happens when something goes wrong in production, not just whether the demo works.

How I think about picking what to build

A pattern that shows up across both projects, and that I'd call one of the more important "soft" engineering skills: matching architectural complexity to the actual stage of the product. It's tempting, especially early in a career, to reach for the most technically impressive solution available. In practice, the harder and more valuable skill is judging what a problem actually needs — a managed service instead of a self-hosted one, a monolith instead of a microservice, a simple form instead of a configurable rules engine — and having the discipline to build that instead.

I go into this in more depth in the backend case study on AntreKlinik's real-time architecture, which is the natural next read if you want the technical detail behind the decisions above.

What's next

This post is the starting point for a longer series. Coming up:

  • A backend engineer's deep dive into real-time architecture and infrastructure trade-offs (AntreKlinik)
  • A frontend engineer's look at building trustworthy UI for financial and real-time data (VendorPay)
  • Notes on deliberately expanding into Laravel, Python, and Java as a JavaScript-and-AWS-first engineer

I'm a software engineer based in Jakarta, Indonesia, working across Laravel, Node.js, React, and AWS. If you're hiring or just want to talk shop about any of the projects above, feel free to reach out.