Where I’ve worked

A record of the places, people, problems, and work that have shaped how I build software today.

2021 — Present

Along the way

Places that became part of the journey

Not everything here was perfect or made it to production. Some things worked, some changed direction, and some simply taught me a better way to approach the next problem.

Susi AirBackend DeveloperOctober 2025 — Present
  • TypeScript
  • Node.js
  • NestJS
  • MySQL
  • PostgreSQL
  • Docker
  • Nuxt
  • Nitro
  • Drizzle ORM
  • MinIO
  • OpenAPI

IndustryAviation

LocationPangandaran, West Java

I work in a small engineering team, so requirements often come directly from the people using the systems — staff, pilots, OCC, the Chief Pilot, data analysts, and management.

Most of these systems are already running day to day, which means changes usually have to happen gradually. Over time, I have become more careful about improving the structure without forgetting that someone still depends on it working tomorrow morning.

What I worked on

  • Work on REST APIs, business rules, validation, data normalization, email automation, and scheduled processes across several internal systems.
  • Gradually separate controller, application, and persistence responsibilities using clearer service and repository boundaries.
  • Started using ORM-based migrations so database changes could be tracked alongside the code instead of living only in the database.
  • Built an automated database backup scheduler that now runs in the production environment.
  • Added an index after tracing a slow data-retrieval path, cutting roughly 0.5 seconds from its response time.
  • Put together an engineering handbook, Git conventions, API documentation, ADRs, MkDocs documentation, and onboarding notes so fewer things had to live only in someone's head.

A few things I did

Laku6Full-Stack DeveloperJuly 2024 — October 2024
  • Next.js
  • Python
  • Symfony 2
  • MySQL
  • PostgreSQL

IndustryElectronics Recommerce

LocationJakarta

I joined an established product with a much broader mix of technologies than I had worked with before. Most of my time went into frontend work, where my JavaScript and TypeScript background matched what the team needed at the time.

It was a short chapter, but it gave me a closer look at what it means to work inside a larger codebase — following existing conventions, understanding unfamiliar parts, and making changes without treating the system as if it started with me.

What I worked on

  • Implemented a couple of production pages in Next.js from UX designs while following the existing component, styling, and application conventions.
  • Worked through existing Symfony 2 flows to debug issues and make small backend changes.
  • Built Python scheduled jobs for reporting, database access, and processing application datasets.

A few things I did

Rhapsodie.coProject ManagerFebruary 2024 — July 2024
  • Figma
  • GitHub
  • Trello
  • Miro
  • Google Docs
  • cPanel

IndustryMusic Education Platform

LocationBSD City, Tangerang

I worked somewhere between the business owner and the development team, helping turn ideas for a platform connecting music teachers and students into something the team could actually plan and build.

The project did not begin from a blank page. There was already a Laravel application, but very little documentation or source-code handover, so part of the work was first figuring out what already existed before deciding where to go next.

What I worked on

  • Recovered the existing source code from the hosting environment and went through it to get an initial picture of the system.
  • Turned conversations with the owner into software requirements, user-role and feature flows, MVP scope, success criteria, and a Definition of Done.
  • Mapped out the trade-offs between continuing with the legacy application and rebuilding it, including the time, cost, and technical debt that came with either direction.
  • Put together an initial product structure in Figma and helped look for a third-party development partner to continue the implementation.
  • Followed the work through GitHub activity, local builds, implementation reviews, and technical discussions as the project moved forward.

A few things I did

Kelola Teknologi DigitalFull-Stack DeveloperJanuary 2023 — June 2023
  • TypeScript
  • Node.js
  • Express.js
  • React
  • Next.js
  • MySQL
  • Docker
  • GitLab

IndustrySoftware Development / IT Services

LocationBSD City, Tangerang

I moved between projects as the team's needs changed, which meant getting used to different domains, codebases, and problems fairly quickly. The two I remember most clearly are Qonnectic and Prima Health Tracking System.

This was also where I started paying more attention to how a codebase is organized — not because architecture needed to be complicated, but because I wanted it to be easier to follow when someone had to debug, change, or continue the work later.

What I worked on

  • Modeled hierarchical file and folder relationships in MySQL for a document-management feature.
  • Helped turn client-owned spreadsheet calculations into application flows for livestock operations.
  • Moved a growing prototype backend out of Next.js into a dedicated Express.js service as the project became more complete.
  • Proposed an N-layered architecture with feature-based vertical slicing, put together a reusable boilerplate, and walked the team through how it could be used.

A few things I did

Bangunindo Teknusa JayaBackend DeveloperAugust 2022 — January 2023
  • Python
  • Flask
  • PostgreSQL
  • Docker
  • Git
  • Prisma

IndustryTechnology & Infrastructure Solutions

LocationJakarta

Most of my time was spent around the backend of T3 BAKTI KOMINFO, where infrastructure monitoring data eventually had to turn into something people could act on. My work mostly touched APIs, integrations, automation, data processing, and production fixes.

This was one of the places where I started noticing that backend work is often less about one system working alone, and more about helping several systems talk to each other reliably.

What I worked on

  • Built an escalation flow for prolonged packet-loss events, connecting monitoring events to Slack notifications and support tickets for the relevant ISP or vendor.
  • Worked on Flask APIs, backend integrations, and data-processing requirements that came from the data analytics team.
  • Helped maintain and troubleshoot backend functionality that was already running in production.
  • On a separate early-stage project, noticed a possible SQL injection risk in raw queries, raised it with the technical lead, and helped put temporary query-safety measures in place.

A few things I did

PT Inovasi Solusi InternasionalBackend DeveloperMarch 2021 — August 2022
  • JavaScript
  • TypeScript
  • Node.js
  • Express.js
  • MySQL
  • Knex
  • Docker
  • OpenAPI
  • Joi
  • Jest

IndustrySoftware Development

LocationJakarta

This was the first place where programming stopped being something I was learning on my own and became part of a system that other people actually depended on.

Most of my time went into an online registration and KYC platform for Solid Gold Berjangka, where I helped move existing Laravel functionality into TypeScript and Express.js without losing the business behavior that was already there.

What I worked on

  • Worked on registration, login, logout, password recovery, user profiles, account management, and role-based authorization.
  • Translated existing KYC and risk-validation rules into backend logic and connected the application to an external screening system.
  • Added server-side validation, rate limiting, sanitization, authorization checks, escaping, and Jest unit tests as I became more aware of how much an API should distrust incoming input.
  • Documented endpoints, payloads, responses, authentication, and errors with Swagger/OpenAPI so the frontend did not have to guess how the backend behaved.
  • Organized backend code by feature so related logic stayed closer together instead of being scattered across unrelated folders.

A few things I did

Looking back

Software engineering is larger than source code.

I started by trying to make things work. Over time, I began caring more about whether the code could be understood, changed, and carried forward by someone else.

Somewhere along the way, software became less about code alone and more about everything around it — business rules, data, infrastructure, documentation, communication, people, and the constraints holding them together. I still enjoy making things work. I just no longer think that is where the work ends.