Financial Software Engineer

FRTB (Fundamental Review of the Trading Book)

• Global regulatory initiative with compressed US timelines
• Requires rapid iteration, testing, and validation of risk models and calculations

Strategic Risk on P&L

• Internal regulatory-driven transformation programme
• Focused on:
• VaR (Value at Risk) methodology redesign
• High complexity across enterprise risk and finance systems

Role Reality: What This Job Actually Is

• This is not a traditional BA role

Actual split

• 80% Developer / Technical / Data work
• 20% BA / coordination / requirements interpretation
• Candidates will:
• Work directly with risk data, pricing, and calculations
• Troubleshoot and reproduce risk and P&L outputs
• Write Python code regularly
• Participate in technical design and validation discussions

Core Responsibilities

Technical (Primary Focus)

• Use Python to:
• Reproduce risk and pricing calculations
• Breaks in P&L and risk outputs
• Data inconsistencies and calculation discrepancies
• Work with risk/pricing platforms via APIs:
• Support testing and validation of regulatory implementations

BA / Functional (Secondary Focus)

• Translate regulatory requirements into:
• Practical implementation approaches
• Technical and functional specifications
• Map:
• End-to-end risk workflows
• Data lineage and control frameworks
• Act as liaison between:
• Risk / Quant teams
• Engineering teams

Required Skills

Technical (Non-Negotiable)

• Strong Python (core requirement)
• Experience working with:
• Analytical/computational systems
• Ability to:
• Debug calculations
• Investigate production issues
• Work hands-on with datasets

Domain Knowledge

• Financial services background (essential)
• Exposure to:
• Credit risk / capital / liquidity
• Understanding of:
• VaR
• Regulatory frameworks (Basel / FRTB preferred)

Analytical & Behavioural

• Strong problem-solving / investigative mindset
• Ability to explain complex results and discrepancies
• Comfortable operating in complex, large-scale regulated environments
• Able to engage in technical design conversations, not just requirements gathering

Technology Environment

• Enterprise risk/pricing platforms (internally built or similar to industry frameworks)
• API-driven architecture for risk calculations
• Limited cloud usage – more traditional internal platforms

#J-18808-Ljbffr…