THIS IS NOT
A RESUME.
IT'S A JOURNEY.
SCROLL TO ENTER
THE STORY OF HOW
I BECAME A
SOFTWARE ENGINEER.
One Agustiranda.NET Developer & Software Engineer
CHAPTER 01
2021

THE BEGINNING

InternPT Infineon Technologies Batam
This was where everything started.

I discovered something that would become a big part of my career.

.NETC# · ASP.NET MVC · The first stack that made sense.
WHAT I LEARNED
  • 01How applications are structured
  • 02How teams work
  • 03How requirements become software
  • 04How .NET is used in a real application

I learned how to write code.

FIRST BUILD

The first thing I shipped that other people used.

IFBT People Dashboard

2021Intern DeveloperPT Infineon Technologies BatamHR Dashboard
IFBT People Dashboard — HR Dashboard
IFBT People Dashboard — HR Dashboard
THE PROBLEM
Employee data lived in spreadsheets. Every report was manual, slow and out of date the moment it was sent.
THE APPROACH
Model the data first, then build screens around the questions the HR team actually asked every week.
THE BUILD
ASP.NET MVC application with server-rendered views, a relational schema and role-based access for the people team.
THE DECISIONS
  • 01Server-rendered MVC over SPA — the team needed reliability, not interactivity.
  • 02Normalized schema so reports stayed correct as data grew.
  • 03Reused layout components so new report pages took hours, not days.
THE RESULT
The first thing I built that other people used every day. Weekly reporting went from hours to a page refresh.
STACK
  • ASP.NET MVC
  • C#
  • .NET
  • SQL Server
CHAPTER 02
2022

GOING DEEPER

Intern + Part-time DeveloperPT Simpli Inovatif Mandiri (Simplidots)

I wanted to understand .NET beyond building applications.

INTERN
PART-TIME
LEARNBUILDUNDERSTAND
.NET
01
C#
02
API
03
SQL
04
REST
INTEGRATION

Different systems. One language between them.

Mapping Library

2022DeveloperPT Simpli Inovatif Mandiri (Simplidots)Integration Library
Mapping Library — Integration Library
Mapping Library — Integration Library
THE PROBLEM
Different applications. Different variables. Different structures. One problem — how do they understand each other?
THE APPROACH
Define one canonical shape, then describe every application as a mapping into and out of that shape.
THE BUILD
A reusable .NET library with declarative field mappings, type coercion and validation before anything is written.
THE DECISIONS
  • 01Declarative mapping definitions instead of hand-written conversion code per app.
  • 02Fail loudly on unmapped required fields rather than writing partial data.
  • 03Version the mappings so an app change never silently breaks another integration.
THE RESULT
Adding a new accounting application became a configuration task instead of a new integration project.
STACK
  • .NET
  • C#
  • REST API
  • SQL
PARALLEL PATH
2022

STUDY

EDUCATION

While interning and working part-time, I was also finishing my degree.

The same year I was learning how software breaks, I was completing the formal path that started it all.

DEGREE
INSTITUTION
Politeknik Negeri Batam (Polibatam)
PROGRAM
D4 Teknik Multimedia dan Jaringan
GRADUATION
2022
GRADUATION PAPER
Usability Analysis with Heuristic Evaluation Method on the IFBT People Dashboard Web
Read Paper ↗
CHAPTER 03
2022

THE UNEXPECTED

Associate DeveloperPT eBisnis Mandiri Technology (Total eBiz Solutions)

I thought I would spend most of my time building.

But my role took another turn.

  • UNIT TEST
  • MANUAL QA
  • TEST CASES
  • KATALON
TEST CASE
TC-014 · Login with expired session
INPUT
user: demo@corp.id · token: expired
SYSTEM
auth-service → session validator
EXPECTED
Redirect to /login with notice
ACTUAL
500 Internal Server Error
RESULT
FAILED → reported → fixed → retested

I learned how software breaks.

CHAPTER 04
2023

A NEW CHAPTER

Software EngineerImpetus Fintech Pte Ltd

In December 2023, I joined Impetus Fintech — the technology arm of Synergy Financial Advisers — as a Software Engineer.

BUILD+TEST+UNDERSTAND=ENGINEER

Legacy Module Migration

2024Software EngineerImpetus Fintech Pte LtdSystem Modernization
Legacy Module Migration — System Modernization
Legacy Module Migration — System Modernization
THE PROBLEM
Critical business modules were running on .NET Framework 4.8 — hard to maintain, hard to scale, and increasingly risky to change.
THE APPROACH
Move module by module to .NET 8 with an API-first design, keeping the legacy system running while each piece was rebuilt and verified.
THE BUILD
Rebuilt MVC modules as .NET 8 Web APIs with clean separation of concerns, preserving existing business behavior throughout the migration.
THE DECISIONS
  • 01Incremental migration over big-bang rewrite — the business could not afford downtime.
  • 02API-first design so the new modules could serve multiple frontends and future integrations.
  • 03Behavior parity verified module by module before any cutover.
THE RESULT
Core modules now run on a modern, maintainable .NET 8 stack — easier to extend, test and deploy.
STACK
  • .NET 8
  • C#
  • ASP.NET Core
  • REST API
  • SQL Server

Performance Reporting & Reliability

2025Software EngineerImpetus Fintech Pte LtdPerformance & Ownership
Performance Reporting & Reliability — Performance & Ownership
Performance Reporting & Reliability — Performance & Ownership
THE PROBLEM
The performance reporting module was slow under load, and production errors surfaced through Sentry logs without a clear owner.
THE APPROACH
Migrate the module, tune the heavy queries and data paths, then take full ownership — every Sentry error, fix and future update for the module goes through me.
THE BUILD
Migrated reporting module with load-performance tuning, plus a debugging workflow driven by Sentry logs to find and fix production issues at the root.
THE DECISIONS
  • 01Profile first, tune second — optimizations driven by measured bottlenecks, not guesses.
  • 02Sentry-driven debugging: every production error traced from log to root cause to fix.
  • 03Full module ownership: errors, fixes and future updates are my responsibility.
THE RESULT
Reporting loads measurably faster, production errors are resolved systematically, and the module has a clear, accountable owner.
STACK
  • .NET
  • C#
  • SQL Server
  • Sentry
  • Performance Tuning

Singpass FAPI 2.0 Migration

2026Software EngineerImpetus Fintech Pte LtdSecurity & Compliance
Singpass FAPI 2.0 Migration — Security & Compliance
Singpass FAPI 2.0 Migration — Security & Compliance
THE PROBLEM
The existing Singpass Login and Myinfo integration had to meet the stricter FAPI 2.0 security profile required for financial-grade identity flows.
THE APPROACH
Own the migration end to end: understand the FAPI 2.0 requirements, rework the authentication flows, and validate every integration path against the new standard.
THE BUILD
Reimplemented the Singpass Login and Myinfo flows on FAPI 2.0, covering token handling, signing, and the updated integration contracts.
THE DECISIONS
  • 01Full ownership of the migration — from spec reading to production verification.
  • 02Security-first implementation: every change validated against the FAPI 2.0 profile, not just made to work.
  • 03Regression-tested every dependent flow so users never noticed the cutover.
THE RESULT
The platform's identity flows now meet the financial-grade FAPI 2.0 standard without breaking active sessions or dependent client integrations.
STACK
  • .NET
  • C#
  • Singpass
  • Myinfo
  • FAPI 2.0
  • OAuth
CHAPTER 05
2026

THE NEXT CHAPTER

AI tools are shifting how software is built and operated.
I chose to explore where they actually create practical leverage.

THE IDEA DIDN'T START WITH AI.

It started with a problem.

Q1

What should we cook today?

Q2

What ingredients do we already have?

Q3

How can we prepare meals efficiently for the family?

Q4

How can we adapt meal preparation for children starting MPASI?

TOO MANY QUESTIONS
FOR ONE MEAL.
satuWajan.id

AI-assisted meal preparation for families — and for the MPASI stage.

  • CHICKEN
  • CARROT
  • POTATO
  • RICE
FAMILYPROBLEMAIMEAL PLANPREPARATION
AI THINKING...
TODAY'S MEAL
  • Chicken & carrot porridgeMPASI 8m+ · 20 min
  • Potato chicken stewFamily portion · 35 min
  • Steamed rice + brothShared base · 15 min

One pan. A family meal and a baby's first meal, decided in seconds.

Explore more open source & side projects in The Vault →
CASE STUDY

satuwajan.id

2026CreatorPersonal projectAI Product
satuwajan.id — AI Product
satuwajan.id — AI Product
THE PROBLEM
Planning family meals is a daily decision loop: what to cook, what is already in the kitchen, and how to adapt it for a baby starting solids.
THE APPROACH
Start from the household's real constraints — ingredients on hand, time, and the child's feeding stage — and let AI do the planning, not the cooking.
THE BUILD
A pantry-first input model feeding a planning layer that returns a shared family meal plus an MPASI variation from the same pan.
THE DECISIONS
  • 01AI as a planning tool, not a chat gimmick.
  • 02One pan, two outputs — family portion and baby portion from the same base.
  • 03Extensible architecture so a real model API can be plugged in later.
THE RESULT
A working concept that turns four uncertain questions into one decided meal.
STACK
  • React
  • TypeScript
  • AI
2021

I learned how to write code.

2022

I learned how software breaks.

2023

I learned how to build software.

2026

Now I'm learning how to take end-to-end ownership of products.

THE STORY
IS STILL BEING WRITTEN.
CURRENTLY
Building.
Learning.
Exploring.
THE NEXT CHAPTER
IS STILL LOADING…
MAYBE THE NEXT CHAPTER
STARTS HERE.

Focused on building reliable .NET backends, production-grade REST APIs, and full-stack web applications. Open for full-time and high-impact engineering roles.

Every chapter changed how I build.

© 2026 One Agustiranda.NET Developer & Software Engineer