Interim Director, Market Surveillance Technology — Exchange Controls

The mandate

Independent assurance could not reproduce several surveillance alerts from raw order events because clock normalisation, enrichment versions and scenario releases were not retained consistently. The technology director left after the committee rejected the initial remediation, creating a gap between compliance requirements and engineering execution.

The interim is needed within three weeks for an eight-month fixed term. A permanent director will be recruited after the replay environment passes acceptance in month four, with the final month reserved for transfer and no conversion option.

Handover is complete when selected alerts can be reproduced from immutable events, all critical feeds meet timestamp and completeness controls, scenario releases carry traceable approval, and independent assurance accepts a representative replay sample. The successor must execute one release and one regulatory data request using the new process.

The interim may stop surveillance releases, quarantine defective feeds, choose remediation architecture and direct ₹9 crore within the sanctioned portfolio. Retention-policy changes, replacement of the core surveillance engine, permanent hiring and outages affecting live market operation require CTO and committee approval.

Trading-engine performance, broker supervision and compliance judgement on alert disposition are outside scope. The director owns technological truth and reproducibility, not decisions about whether observed behaviour constitutes misconduct.

Why this seat is open

The rejected assurance response showed that project completion had been mistaken for reproducible evidence. Existing leads own individual feeds or engines but not the complete alert chain. A temporary director can impose an end-to-end standard before the exchange appoints long-term technology leadership.

What you will own

• Define the canonical event model for orders, trades, reference data, identities, timestamps and scenario versions.
• Decide which feeds or scenarios must be quarantined when completeness, synchronisation or lineage controls fail.
• Build a replay acceptance pack that reproduces selected alerts from immutable source events and retained code versions.
• Approve surveillance releases through compliance sign-off, test evidence, rollback readiness and versioned parameter records.
• Reconcile production alert counts to source volumes and investigate unexplained drops, duplication or latency.
• Present independent assurance with end-to-end samples and close every severe reproducibility exception.
• Transfer the data contracts, release catalogue, architecture decisions, control failures and next regulatory requests to the successor.

Candidate qualifications

• Led surveillance, exchange, trading or regulated market-data technology at functional director level.
• Built reproducible event pipelines involving timestamp normalisation, reference enrichment and versioned detection logic.
• Managed production releases where audit lineage and regulatory retrieval mattered as much as system availability.
• Bridged compliance scenario ownership and engineering delivery without assuming first-line trading judgement.
• Directed multi-disciplinary teams across data engineering, platform, quality and production operations.
• Understands Indian market infrastructure, electronic-order data and regulator evidence expectations.

Non-negotiables

• Can work from Mumbai within three weeks and travel to the Bengaluru engineering centre.
• No current relationship with the surveillance engine or market-data vendors.
• Will preserve Compliance's sole authority over alert disposition.
• Must have led live regulated-market technology, not a laboratory analytics programme.

1. 49 words maximum. Confirm your start date and any exchange, broker or surveillance-vendor conflict.
2. 49 words maximum. Describe an alert or trade event you made reproducible from raw data and versioned logic.
3. 49 words maximum. Which timestamp defect would force you to quarantine a surveillance feed?