Public Safety Workforce Platform
Compliance-bound products need isolation without fragmenting the engineering model.
ResultDelivered an isolated cloud environment and made the product operate within a more restricted service boundary.
- Role
- Full-stack product and platform engineering
- Period
- 2026 · ongoing
- Context
- Public safety workforce operations
- Confidentiality
- Anonymized professional work
At a glance
Compliance-bound products need isolation without fragmenting the engineering model.
Delivered the isolated cloud environment, adapted shared application behavior to restricted services, and added scoped machine access, observability, and release-drift controls.
Delivered an isolated cloud environment and made the product operate within a more restricted service boundary.
The choice behind the implementation.
- Challenge
- A compliance-bound tenant required stronger infrastructure isolation without creating a separate product.
- Decision
- Preserve one product model while expressing environment-specific boundaries and service adaptations through infrastructure as code.
- Trade-off
- Configuration and operational paths become more explicit, but the platform avoids a manually maintained product fork.
The product boundary
The platform coordinates overtime and shift operations for public-sector teams. Users claim shifts, check in and out, and create records that support downstream payment workflows. The implementation spans a multi-tenant application and an isolated environment for a compliance-bound tenant.
What I delivered
- Delivered the isolated government cloud environment end to end and adapted the application where expected managed services were unavailable.
- Designed a machine-to-machine API with scoped access, token revocation, a custom serverless authorizer, and route-level rate limits.
- Established production observability with alarms and a severity-aware alert processor that routes actionable failures.
- Introduced patch-aware drift audits and a pre-deployment checklist after identifying fixes stranded between releases.
- Generated regulator-formatted PDF and Word documents in the browser.
Engineering shape
- React applicationsTwo user-facing surfaces sharing a common platform contract.
- GraphQL and serverless servicesTyped product operations distributed across roughly 35 functions.
- Infrastructure as codeTerraform-managed services with a separately isolated deployment boundary.
- Operational evidenceAlarms, severity classification, release checks, and drift audits.
The public boundary is deliberate.
Product and client identities, customer data, repositories, and confidential implementation details are intentionally omitted. The page describes only confirmed personal contribution and safe technical context.