Open-Finance API Reliability Leader

The mandate

The platform reliability director exited after recurring consent-validation and payment-initiation failures were treated as unrelated service events, producing contradictory partner notices and incomplete root-cause closure. Engineering managers maintain availability, but no executive currently joins customer harm, ecosystem obligations and technical reliability into one decision chain.

The interim is expected in São Paulo within sixteen days for an eight-month fixed assignment. Recruitment for a permanent platform executive begins in month four, with a four-week overlap planned after selection; the interim will not participate in final candidate scoring.

Exit conditions are two consecutive reporting cycles inside approved availability and latency objectives, complete lineage for consent and initiation failures, closure of all severity-one corrective actions, a passed multi-participant recovery exercise, and one incident review chaired by the successor. An improved aggregate uptime percentage by itself is insufficient.

The leader may declare platform incidents, freeze releases, change reliability priorities, retire unsafe interfaces and reallocate the current operations budget. Any customer-compensation policy, product withdrawal, capital request above BRL 12 million or permanent appointment needs executive approval; regulatory representations remain signed by the designated compliance officer.

Core-ledger replacement, credit underwriting, consumer-app redesign and commercial pricing are out of scope. Work is bounded to Open Finance APIs, consent and certificate dependencies, partner operations, service evidence and the command routines needed to keep these components reliable.

Why this seat is open

Several failures revealed that technical ownership stopped at service boundaries while customers experienced one continuous journey. The prior leader's departure made the fragmented accountabilities visible at the same moment ecosystem scrutiny intensified. The executive team chose temporary authority to repair the operating system before appointing its long-term owner.

What you will own

• Reconstruct the failure history across consent, certificates, directories, rate limits, payment initiation and downstream bank dependencies.
• Set journey-level service objectives and error budgets that expose customer failure hidden by healthy component averages.
• Decide release freezes and restoration priorities through a single incident command model with named business, risk and technology delegates.
• Replace narrative root-cause closure with evidence for recurrence tests, corrective-control ownership, expiry dates and sampled effectiveness.
• Establish partner communication protocols that reconcile shared incident facts before ecosystem status or customer guidance is issued.
• Run a multi-participant resilience exercise covering certificate failure, degraded consent lookup and ambiguous payment state.
• Transfer the reliability scorecard, risk decisions, incident library, partner commitments and next-quarter engineering priorities to the permanent appointee.

Candidate qualifications

• Led reliability or platform operations for a regulated bank, payment network, open-banking platform or high-volume financial API estate.
• Commanded customer-impacting API incidents involving external participants and can evidence decisions across technical and regulatory timelines.
• Implemented service objectives and error budgets at end-to-end journey level rather than using infrastructure uptime as a proxy.
• Governed consent, strong-authentication, certificate or directory dependencies within a financial data-sharing ecosystem.
• Repaired root-cause and corrective-action disciplines so control effectiveness could be sampled after tickets were closed.
• Managed senior engineers, partner operations and incident leaders across a platform serving material transaction or data-sharing volumes.

Non-negotiables

• Can start within sixteen days, work in São Paulo three days weekly and travel to Brasília when scheduled.
• Will join the severity-one on-call chain and accept documented authority boundaries over regulatory communications.
• Has personally governed external-participant API reliability, not only internal application support or delivery management.
• Must disclose any active role with a Brazilian bank, fintech, API aggregator or relevant technology supplier.

1. 49 words maximum. Give your earliest start date and confirm whether you can take executive incident accountability from São Paulo within sixteen days.
2. 49 words maximum. Which end-to-end API reliability measure exposed a failure that component uptime concealed in your last platform role?
3. 49 words maximum. Describe one cross-participant incident decision you made before complete causality was known and what happened next.