Liquidity Stress Architecture Director

The mandate

This nine-month project will design and prove a quantitative liquidity stress architecture that connects positions, behavioural assumptions, contingent outflows, monetisation capacity and management action constraints. The engagement ends with tested artifacts and owner capability. It excludes liquidity strategy, funding execution, risk-appetite decisions and production operation after handover.

Named deliverables are a source-and-population map, scenario taxonomy, behavioural assumption register, counterbalancing-capacity method, intraday and contingent-flow treatment, management-action feasibility protocol, aggregation logic, result bridge, control matrix, test suite and operator guide. The architecture must distinguish deterministic contractual flow, modelled behaviour, judgmental overlay and constrained action.

Six milestone dates govern delivery: scope accepted by 6 November 2026; data and population diagnostic by 18 December; scenario and assumption design by 12 February 2027; engine specification by 16 April; parallel stress and defect closure by 11 June; final internal reproduction by 30 July. The Chief Risk Officer accepts each package after designated liquidity-risk and model-risk reviewers document challenge.

The acceptance test requires internal staff to run selected scenarios using approved inputs, identify seeded behavioural, encumbrance and double-counting defects, reconcile movement between runs and explain which management actions remain feasible under timing and operational constraints. Unresolved critical defects prevent acceptance.

Management must provide approved positions, contractual and behavioural data, current scenario definitions, action evidence, model documentation and decisions within agreed windows. Consulting owns architecture, testing and transfer; management owns assumptions, limits, actions and reported results. Funding execution, legal opinions, platform build, independent validation and recurring runs are excluded.

What you will own

• Map liquidity sources and uses with lineage from contractual record through modelling, aggregation and reported result.
• Define scenario families and severities that combine idiosyncratic, market, timing and currency dimensions coherently.
• Specify behavioural assumptions with evidence, segmentation, monitoring threshold, owner and refresh trigger.
• Prevent double counting across inflows, collateral, monetisation capacity and proposed management actions.
• Model action feasibility against operational lead time, market capacity, legal constraint and competing scenario demand.
• Build result bridges that explain changes by position, assumption, scenario, action and implementation.
• Execute parallel tests with seeded defects and verify critical remediation before handover.
• Transfer the method to internal owners while routing strategy, appetite and systems requests through change control.

Candidate qualifications

• Demonstrate quantitative design leadership for enterprise liquidity stress across contractual and behavioural flows.
• Describe a double-counting or timing error you exposed and its effect on apparent survival capacity.
• Show how you translated a proposed management action into constrained quantitative availability.
• Evidence assumption calibration and monitoring where recent behaviour was not treated as an unconditional forecast.
• Provide a parallel-run acceptance test that internal operators completed independently.
• Explain how you kept stress architecture separate from funding strategy and risk appetite.
• Show fixed-fee control when platform implementation or recurring production was requested.

Working terms and boundaries

• The total project fee covers nine months, five days weekly and six dated milestone packages.
• Acceptance rests with the Chief Risk Officer after internal reproduction and closure of critical defects.
• Management owns assumptions, strategy, limits, actions and production results; consulting owns named artifacts.
• Late data or decisions enter written dependency governance before dates or fees change.
• Funding execution, legal opinion, platform implementation, independent validation and ongoing operation are excluded.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 12 October 2026. Mandate reference QNT-CON-2026-SYD-08.