Senior QA EngineerJakarta, Indonesia
Fourteen years making complex, high-traffic systems provably reliable — across banking, retail, fintech and government platforms serving millions of citizens.
The record
Facts rather than self-scored figures. Every line is something an employer, a certificate or the software itself can confirm — and where the check can be made on this site, the last column links straight to it.
| Fact | What it means | Where to check |
|---|---|---|
| 15 years | Testing without a break since 2011 — manual, automation, API and performance, across every year of it. | Dated timeline |
| 7 companies | 6 industries: core banking, retail, IT consulting, fintech, edtech and government platforms. | Industry spans |
| Exelion | An enterprise test management platform architected and built end to end to replace TestRail. Not a tool he was trained on — a tool he wrote. | Working demo |
| 13 + 2 | The quality department he ran as its manager: 13 testers and 2 technical writers. | PT Geekseat Indonesia |
| Rapor Pendidikan | Indonesia's national school reporting platform. He owned its quality end to end and put its regression suite into the delivery pipeline. | GovTech Edu |
| Zero data lost | A bank's core platform replaced with every customer record intact, verified at the database across SIT and UAT. | PT Collega Inti Pratama |
| 15 certificates | Earned alongside full-time work, each listed with its issuer, date and credential ID. | The certificates |
Taken from the employment record and the certificates themselves. Nothing here is estimated, and no figure is self-scored.
Read the engagements in fullHow the work runs
Quality is designed in from the start rather than inspected at the end. Each stage feeds the next, and every stage produces evidence.
01
Map risk before writing a single case. Highest-risk paths get the deepest coverage.
02
Build test cases that read clearly, cover the edges, and survive refactors.
03
Run manual, automated and API suites — Selenium, Appium and Postman — across environments.
04
Turn results into decisions: what shipped, what is blocked, and what the risk actually is.
05
Release with confidence, then watch production to confirm the call was right.
Availability
If a team needs someone who can make release risk visible and act on it, that is the conversation to have.