SYSTEM / 03
Central Land Repository
Enterprise land administration workflows for a federal government platform.
ROLEFullstack Engineer
PERIOD2025—Present
ARCHITECTURERole-driven / Secure workflows
01 / CONTEXT
A system shaped by real-world constraints.
The product coordinates a multi-stage Certificate of Occupancy process across operational roles, payments, approvals and final issuance.
02 / ROLE & OWNERSHIP
Where I contributed.
- Full-stack engineering across secure access, workflow interfaces, shared services and operational data tooling.
03 / CONSTRAINTS
What made the work difficult.
- Different roles needed controlled access to specific workflow stages and operational records.
- Large result sets needed reliable server-side filtering and pagination without fragmenting frontend behavior.
04 / ENGINEERING DECISIONS
What mattered technically.
Explicit workflow stages
Modelled the Certificate of Occupancy process as a multi-stage workflow from application through approval and issuance.
Reusable operational grids
Built shared data-grid behavior around server-side filtering and pagination.
Centralised application boundaries
Used shared services and centralised error handling to keep frontend behavior consistent as the workflow surface expanded.
05 / RELIABILITY & SECURITY
Correctness beyond the happy path.
- Access uses OTP and JWT controls together with request signing and encrypted payload exchange.
06 / TECHNOLOGY
Technology should support the system, not become the story.
React · TypeScript · Redux Toolkit · TanStack Query · Zod · AWS