CHIEF Architect

Description Platform Architecture Governance Own and enforce the five-layer architectural blueprint across all systems, data, and integration layers. The canonical data model is non‑negotiable infrastructure. Establish and maintain schema governance — no uncontrolled field creation, no custom code bypassing platform tools. Every field has a defined source tier, business definition, and provenance record. Complete and govern the DynamoDB-to-Postgres migration, including schema design, data validation, and deprecation sequencing for legacy DynamoDB tables. Own the Silver data dictionary architecture: field definitions, source lineage from stated data through manufactured data to authoritative Silver designation, tier classification (Tier 1 direct institutional pull, Tier 2 third‑party, Tier 3 document submission), and target/consumer documentation. Establish and chair the Architecture Review Council. All significant design decisions are reviewed, documented, and held to pattern standards before implementation. Define and enforce the Anti‑Rube Goldberg principle: one governed way to solve each class of problem. Reuse over novelty. No proliferation of bespoke solutions. Rules Engine and BPM Deployment Deploy and govern the componentized rules engine and BPM layer that is the operational core of the certified loan process across all three seller channels: Flow/Delegated, Non‑Delegated/Mini‑Corr, and Bulk/Institutional. This layer is what makes the 600‑to‑6 complexity abstraction possible at scale. Complete the Camunda (or equivalent) rules engine evaluation, make the selection decision, and lead deployment. The rules engine must be business‑authorable, engineer‑reviewed, and vendor‑extractable. Enforce the workflow/rules separation principle in all builds: workflow orchestrates, rules validate. Logic never embeds in workflow steps. Build the componentized rules library in collaboration with the credit risk and underwriting leadership, supporting channel‑specific configurations without duplicating core logic. Design the rules engine to support the eight certified loan process gate validations across delegated, non‑delegated, and bulk channels, with third‑party data integration at each gate where applicable. #J-18808-Ljbffr