Designing a provenance-aware employer data model
How NZ Accredited Employer Inspector keeps official accreditation data, community page mappings, derived name matches, and operational state separate.
Notes from production systems, SaaS trade-offs, backend-heavy product work, and decisions that carry real operating cost.
How NZ Accredited Employer Inspector keeps official accreditation data, community page mappings, derived name matches, and operational state separate.
How I approached a seemingly simple browser extension as a data-trust problem, with explicit source boundaries, user-triggered verification, and explainable results.
In a production SaaS developed and maintained by one person, every layer of complexity eventually returns to that person. Complexity worth owning solves a real problem. The rest borrows time from both the product and its developer.