Automation · 2025
Employee CV Generator
Deterministic CV generation for a real HR team: pulls employee data from Drive and Sheets, fills a branded template, and exports PDF + DOCX — no code required by the user.
- AI or external APIs — deterministic
- 0
- formats per employee — PDF + DOCX
- 2
- source prioritization
- per-field
Architecture
Select a stage to explore it.
01 · Sources
Employee documents in Drive folders and project experience in a Google Form responses sheet — the data as HR actually keeps it.
Visuals

01 · Problem
HR at PT Magna Solusi Indonesia assembled employee CVs by hand from scattered sources — Drive documents, form responses, old CVs — a slow, error-prone process repeated for every request.
02 · Solution
A Google Apps Script system that generates every CV from a Sheets menu: data flows from repositories through per-field prioritization into a branded template, and out as PDF and DOCX per employee. Deliberately no AI and no external APIs — the output must be deterministic and auditable, because it's a legal-adjacent HR document.
03 · Engineering decisions
Apps Script is usually written as one long function; this is a layered architecture — controllers, services, repositories, a template engine, and utilities — with a per-module test suite, because the person maintaining it next won't be the person who wrote it. Per-field source prioritization (rather than per-document) means one missing form answer doesn't block a CV.
04 · Results
A tool in real use by a real HR team, operated entirely from a spreadsheet menu with idempotent setup, logging, and error handling. My first shipped software with users who weren't me.
05 · Lessons learned
Constraints are design inputs: 'no code access for the user' and 'must be auditable' shaped better architecture than freedom would have. Boring, deterministic technology was the correct choice — the craft is in the structure.