Principal Accountabilities

• Architecture and technical direction. Own the design of the engine and the services around it: boundaries, orchestration, what gets versioned. In twelve months, it is live on real volume, and the team can extend it without you.
• Modular data acquisition. Credit bureaus, banking and open banking feeds, accounting platforms, identity and fraud providers plug in behind stable interfaces. Adding or replacing one never touches decision logic.
• Credit policy as a versioned asset. Design how rules, policies and models are expressed, versioned, tested and released, so Credit and Risk move at their own pace and policy ships independently of the platform.
• Correctness, auditability and replay. Any decision can be reconstructed with the inputs used and the policy version applied. Proposed changes are shadow run and backtested against history before they go live.
• Observability built in. Instrumentation is part of building a component, not a later phase. From telemetry alone: which sources were called, which policy version applied, what was decided, and what it cost in third-party data. You own the latency and availability objectives.
• Standards and technical leadership. Define how we build, test, deploy and run services in this domain, then hold the line through review and working examples. Mentoring is valued, though we hire for technical depth first.
• 
  

Principal Accountabilities

• Architecture and technical direction. Own the design of the engine and the services around it: boundaries, orchestration, what gets versioned. In twelve months, it is live on real volume, and the team can extend it without you.
• Modular data acquisition. Credit bureaus, banking and open banking feeds, accounting platforms, identity and fraud providers plug in behind stable interfaces. Adding or replacing one never touches decision logic.
• Credit policy as a versioned asset. Design how rules, policies and models are expressed, versioned, tested and released, so Credit and Risk move at their own pace and policy ships independently of the platform.
• Correctness, auditability and replay. Any decision can be reconstructed with the inputs used and the policy version applied. Proposed changes are shadow run and backtested against history before they go live.
• Observability built in. Instrumentation is part of building a component, not a later phase. From telemetry alone: which sources were called, which policy version applied, what was decided, and what it cost in third-party data. You own the latency and availability objectives.
• Standards and technical leadership. Define how we build, test, deploy and run services in this domain, then hold the line through review and working examples. Mentoring is valued, though we hire for technical depth first.
•