What are we looking for?

• 8+ years of experience in software engineering, with a strong portfolio of shipped products
• Proficiency in multiple programming languages (e.g. C#, TypeScript, PowerShell) and development frameworks
• Extensive experience with system design, architecture, and large-scale distributed systems
• Strong understanding of database technologies, both relational and NoSQL
• Experience with cloud platforms (ideally AWS), containerisation and orchestration technologies (e.g., Docker, Kubernetes), Serverless technologies and event-driven cloud-native architectures
• Experience working with various tools to design, orchestrate, test, build, release & monitor your work
• Experience with Agile development methodologies and processes, e.g. Scrum, Kanban
• Highly developed technical leadership, decision making and influencing skills
• Embraces customer-first thinking and strives to balance technical priorities with pace of delivery
• Excellent problem-solving skills and the ability to think critically and strategically
• 
  

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.
•