Reestablishing Domain Consistency
Employer not named by the sourceRemote
Frontier is not the employer and does not collect applications.
About this role
Software Architecture, NoSQL Couch & Mongo, Amazon Web Services, Node.js, PostgreSQL, Elasticsearch, Database Design, API Development · CANONICAL DATA MODEL
Hello,
What caught my attention in your project is that the real problem is not simply completing missing features.
You already have a product. The challenge is that several parts of that product are beginning to behave as independent systems when they should be operating from the same source of truth.
SipVault, the Document Hub, and Form Configuration should not merely exchange data. They should share a coherent domain model.
That is where I would begin.
Before changing production behavior, I would inspect the current React / TypeScript / Node.js / PostgreSQL implementation, map the existing entities and relationships, identify duplicated or conflicting models, and define the canonical structure that the rest of the application should depend on.
From there, the work becomes controlled:
— stabilize tenant boundaries and persistence — align APIs with the canonical model — migrate existing relationships safely — reconnect documents, forms, and configuration workflows — eliminate duplicated logic rather than adding another abstraction layer — protect critical flows with regression tests — leave the architecture understandable for whoever works on the syste