Back to homepage

The full track record

Seven years in HR technology, spanning two complete generations of the stack

Full-stack engineer at ASTRNT from May 2019 to August 2026. Principal contributor to the flagship recruiter platform and the candidate assessment application, and the engineer who led the ground-up rebuild on a modern stack, then wrote the product specifications that drove it. Now open to senior full-stack and product-engineering roles.

This page is built from primary sources rather than recollection: the commit history across my Git identities, the Jira tickets cited in those commits, and the documentation I authored. Every number below is verifiable.

  • May 2019 – Aug 2026
  • Web Developer → Senior Full-Stack Engineer
  • Indonesia

The numbers

A sustained, auditable record

7+ yrs
Years in HR technology

one domain, May 2019 – Aug 2026

11,697
Commits authored

across 35 repositories, deduplicated

1,661
Jira tickets held

93% completed · 335 reported by me

88/88
Months active

no dormant month in seven years

2,114
Hours logged

via Jira #time smart commits

70
Docs authored

Confluence pages + 48 co-edited

49
Product specs written

19 PRDs · 30 design use cases

2.0
Platform generations

Laravel/React → Next.js/TypeScript

The career arc

Three acts, one trajectory

From feature contributor, to multi-product full-stack engineer, to the person trusted with re-architecting the company's flagship product.

2019 – 2021

Act I · Depth

Joined as a Web Developer and was committing to production within weeks, on both sides of the product at once: the Laravel recruiter platform and the React candidate assessment app.

  • Became the principal contributor to the candidate assessment experience: interview session & timer engine, resumable video upload, camera/mic device testing, online proctoring and anti-cheat controls.
  • Shipped five question engines (MCQ, RSQ, FTQ, document upload, media answer), the retake flow, and internationalisation across EN / ID / PT-BR with locale-aware pluralisation.
  • The highest-intensity months of the whole tenure land in the first year: deep ownership of two core products from month one.

2021 – 2024

Act II · Breadth

From a single platform to a product family, plus a sideways move into data engineering that the company had never had in-house.

  • Executed a Laravel 5.4 → 5.8 and PHP 7.1 → 7.4 migration on the live revenue-generating monolith across parallel legacy/target branches, without freezing feature delivery.
  • Helped turn one shared Laravel 8 + Nuxt 2 codebase into three white-labelled products: Kognisi, Popskul, and the CDC per-university career portals.
  • Built the job-market data-acquisition capability from scratch: a scraping suite against LinkedIn, JobStreet, Prosple, GradConnection, Kalibrr, Disnaker and Talentic, feeding a common ingestion API.
  • Shipped a Python/Flask service (VirusTotal scanning, Drive/YouTube transfer, Azure Speech pronunciation scoring) and client-facing landing pages for named enterprises including BCA, Deloitte, Gojek and Google.

2025 – 2026

Act III · Modernisation

Consolidation on the core, then a generational rebuild, executed by the same engineer who had maintained the legacy system for seven years.

  • Diagnosed and fixed a production performance crisis at 2,500 concurrent candidates: N+1 elimination, a database lock and index audit, and queue offloading.
  • Led the ASTRNT 2.0 dashboard rebuild on Next.js 16 · React 19 · TypeScript 5 · Tailwind, with a dual-database live-migration architecture and explicit feature-parity tracking against V1.
  • Authored the product specification layer for the rebuild: 19 PRDs, 30 design use cases, and the company-wide PRD template, work specified then implemented by the same person.
  • Integrated AI scoring and matching (Anthropic, OpenAI, Gemini SDKs) and enforced engineering standards: mandatory Claude Code skill gates and a no-mock E2E policy.

Platform & infrastructure

The cloud chapter: carrying the platform from AWS to Azure

Alongside the product work, I helped move ASTRNT's stack off AWS onto Azure across the public site, the candidate app and the recruiter backend: Azure DevOps hosting, per-environment builds and PM2 process management stood up for each web app, and storage, video and logging re-homed where Azure had no direct AWS equivalent.

  • Repo hosting and integration moved to Azure DevOps (dev.azure.com); the web apps shipped through a beta-az integration line that ran in parallel with the AWS environment.
  • PM2 process management on the servers: public-live on :8080 and web-qna on :8081, each with an ecosystem.config.js and a pm2-reload deploy step.
  • Per-environment builds per app: twin build-aws / build-azure scripts that switch every API and media host at build time from one codebase.
  • Object storage and the video ingest/out pipeline moved onto Azure Blob Storage.
  • The activity-log store was re-homed from AWS DynamoDB onto MongoDB, which the platform already ran, because Azure has no managed DynamoDB equivalent.

Domain expertise

What seven years in one vertical teaches

HR technology knowledge that transfers less visibly than a framework, yet matters more.

Asynchronous video interviewing

Recording, upload, playback and review pipelines that hold up on unknown devices and unreliable connections.

Online proctoring & anti-cheat

Camera proctoring, screen recording, copy/paste blocking, multi-tab detection and mobile lockout.

Assessment & AI scoring

Psychometric (VRA) assessments and AI-assisted scoring of video answers and English fluency.

CV parsing & candidate matching

Document ingestion and structured CV extraction: the pipeline that feeds the matching engine.

ATS workflow

Talent pools, hiring teams, reviewer assignment, comments and voting, change-request status.

White-labelling & i18n

Per-company branding and multi-tenant product families, localised across EN / ID / PT-BR.

Legacy modernisation

Running a migration track in parallel with live production for three years, then a ground-up rebuild.

Job-market data

Reverse-engineered scrapers and an ingestion API that opened a new capability area in-house.

How I work

Engineering practice, measured

Requirements traceability

Every commit links code to a requirement: 916 distinct Jira ticket keys cited in commit messages across 13 projects.

Sustained ownership

1,661 tickets held over seven years; 93% completed. The rest were handed on with progress intact, not abandoned.

Spec-first, then ship

19 PRDs, 30 design use cases and the company-wide PRD template, work defined then implemented by the same person.

Deliberate risk-taking

New technology is proven in low-risk projects first: TypeScript in a scraper in 2024 carried the flagship rebuild in 2026.

Never dormant

88 of 88 calendar months active. A flat contribution line: the difference between bursts and someone a team can plan around.

Honest documentation

Specs that record their own failures and design reversals, including a security gap flagged before it could reach production.

Next

Interested in working together?

I'm open to senior full-stack and product-engineering roles in HR-tech, B2B SaaS, or any domain where writing the spec and shipping the code go hand in hand.