TL;DR
A Head of Platform or VP Engineering in a fintech owns the engineering organisation and the systems it runs: the teams, the delivery, the reliability, the platform the product teams build on, and the operational discipline the regulator eventually inspects. It is the seat between a CTO, who owns technology strategy and is usually outward-facing, and a principal architect, who owns design decisions without owning teams.
The fintech-specific difference is that reliability and auditability are not engineering preferences but obligations. In an unregulated product company, an outage is a bad day. In a payments or lending business it is a reportable event with a customer compensation dimension, and the organisation has to be built so that the answer to "what happened and why" exists before anyone asks.
Key points
- The three senior engineering seats, CTO, Head of Platform and principal architect, are distinct. Companies that collapse them into one hire usually get the strategy and lose the delivery.
- Reliability engineering in fintech is a compliance capability, not only an operational one.
- The strongest signal is having scaled an engineering organisation through a regulatory inspection, not having scaled one quickly.
- Candidates from large unregulated technology companies can be excellent and need a planned adjustment to the constraint environment.
Three seats, not one
| CTO | Head of Platform or VP Engineering | Principal architect | |
|---|---|---|---|
| Owns | Technology strategy, the board conversation, build-versus-buy, the external face | The organisation, delivery, reliability, the platform | Design decisions and their multi-year consequences |
| Measured by | Whether the technology strategy supports the business | Whether the organisation ships reliably and the systems stay up | Whether the architecture held |
| Time horizon | Two to four years | Quarterly, with an annual capability view | Two to five years |
| Reports | CEO | CTO, or CEO where there is no CTO | CTO or Head of Platform |
Small companies legitimately combine them, and a founding CTO frequently does all three. The problem arises at the point of scale, usually between fifty and a hundred and fifty engineers, when the strategy work, the organisational work and the deep design work genuinely conflict for the same person's attention. The most common outcome is that the organisational work wins by urgency and the architecture decays, which is why the Head of Platform hire so often arrives at the same time as a rebuild. Hiring it a year earlier is cheaper.
What the role owns
The engineering organisation. Structure, hiring, levelling, performance, and the senior individual contributor track, which in fintech matters more than in most sectors because the scarce people are individual contributors.
Delivery. Planning, dependency management across teams, and the honest conversation with the business about what is possible. In a regulated fintech this includes an unusually large volume of mandated work that arrives with external deadlines, which has to be absorbed without the roadmap collapsing each time.
Reliability and incident management. Service levels, on-call, incident response, postmortems and the discipline of closing actions. In a payments or lending business the incident process is also an evidence process: what was detected, when, who was told, what the customer impact was, and what was reported. The CISO owns the security half of this and the two processes have to interlock.
The platform. Infrastructure, deployment, observability, data platform and the internal tooling product teams depend on. In an Indian fintech the platform also enforces constraints: data residency by region-locked accounts and policy-as-code, retention by schema, audit trail by default. Those requirements are set out in regulated engineering.
Engineering governance. Change management, access control, segregation of duties, release approval and the evidence that each worked. This is where an inspection actually lands, and where engineering organisations built on trust rather than on process struggle.
Vendor and build-versus-buy execution. The CTO may set the strategy; this role lives with the consequences and manages the vendor relationships under the RBI's outsourcing expectations.
Cost. Cloud and vendor spend, increasingly a board-level conversation.
Which backgrounds transfer
| Background | Transfers | Watch for |
|---|---|---|
| VP Engineering or Head of Platform at a scaled fintech | Strongly. The closest match | Small pool, well compensated, approached rather than applying |
| Engineering leadership at a bank's technology arm | Well | Strong governance instincts; assess pace, autonomy and comfort with smaller teams |
| Engineering leadership at a large unregulated technology company | Partially, often strongly with support | Technically excellent and genuinely fast. The constraint environment is a real adjustment |
| Engineering leadership at a broking or capital markets platform | Well | Reliability and settlement discipline transfer directly |
| Principal or staff engineer stepping into leadership | Situationally | Deep credibility with engineers; organisational skill must be assessed, not assumed |
| Delivery or programme management leadership | Weakly | FinTech engineering leadership requires technical judgement that programme management does not develop |
On the third row, the honest version: engineers from large unregulated technology companies frequently make excellent fintech platform leaders, and the failures follow a predictable pattern. They arrive, find the constraints arbitrary, route around them, and create a governance problem that surfaces at the next audit. The candidates who succeed are the ones who get curious about why the constraint exists. That curiosity is assessable at interview and worth testing deliberately rather than hoping for.
How to assess
Ask about an incident and its aftermath. Not just the technical fix: who was informed, what was reported externally, what the customer impact was, how the actions were closed and verified. In fintech the aftermath is the job.
Ask how they absorbed mandated work. "A regulator sets a deadline that consumes 30% of your capacity for two quarters. What happens to the roadmap and how do you handle the business conversation?" This is the single most fintech-specific question for this seat and it separates people who have lived it.
Probe the individual contributor track. "How do you keep a principal engineer who does not want to manage?" Platform leaders who have built a real senior individual contributor ladder give a structural answer. Those who have not will talk about compensation alone.
Test the governance instinct. "Walk me through how a change reaches production, and how you would evidence that to an auditor." Strong candidates describe it without defensiveness and know where the weak points are.
Check the reliability numbers. Availability, mean time to detection, change failure rate, how often they met their service levels. Candidates who have owned reliability have the numbers; those who have owned delivery alone do not.
Assess the boundary with architecture. Ask how they work with a principal architect, or what they would do without one. Candidates who want to make every design decision themselves do not scale, and candidates who delegate all of them do not provide technical leadership.
The search reality
Define the seat relative to the others before going to market. If there is a CTO, what does this role own that the CTO does not? If there is no principal architect, who makes the design calls? Candidates ask these questions in the first conversation and a company without clear answers signals that the role is undefined, which the strong ones read as risk.
The pool is larger than for the specialist seats but the fintech-experienced subset is not. Engineering leaders are plentiful in India; engineering leaders who have run a platform under supervision are not. Decide early whether regulated experience is a requirement or a preference, because that decision determines the shape of the search.
Expect a technical process and resource it. Senior engineering leaders judge a company by the quality of the technical conversations in the process. Panels dominated by non-technical interviewers lose the best candidates, who read it as a signal about what the organisation values.
Compensation benchmarks against technology, not against financial services. The alternatives these candidates hold are at product companies and global capability centres, and offers built on an internal financial services banding lose consistently.
Sequence with the architect hire. Where both seats are needed, hiring the Head of Platform first and involving them in the architect search produces a better partnership than hiring both in parallel through separate processes. Our approach to sequencing a build is in how we search.
Common questions
What is the difference between a CTO and a Head of Platform in a fintech?
The CTO owns technology strategy, the board and external conversation, and major build-versus-buy decisions. The Head of Platform or VP Engineering owns the organisation and its output: teams, hiring, delivery, reliability, the internal platform and engineering governance. Early-stage companies combine them in one person; the split usually becomes necessary somewhere between fifty and a hundred and fifty engineers, when strategic, organisational and deep design work start to conflict for the same attention.
Do we need a Head of Platform and a principal architect?
At scale, usually yes, because they solve different problems. The Head of Platform owns teams and delivery on a quarterly horizon; the principal architect owns design decisions whose consequences play out over years and has no direct reports. Companies that appoint only the first tend to find architecture decided implicitly by whichever team ships first, and companies that appoint only the second find excellent designs that the organisation cannot execute.
What should we test in a fintech engineering leadership interview?
Incident handling including the external reporting and closure, not just the technical fix; how they have absorbed regulator-mandated work without the roadmap collapsing; whether they have built a genuine senior individual contributor track; their reliability numbers; and how a change reaches production with the evidence an auditor would want. The mandated-work question is the most fintech-specific and the most revealing.
Can we hire an engineering leader from a big technology company into fintech?
Frequently yes, and often to real benefit, provided the adjustment is planned. The failure pattern is consistent: a strong leader finds the regulatory constraints arbitrary, routes around them, and creates a governance exposure that surfaces at the next audit. The candidates who succeed are the ones who become curious about why a constraint exists rather than treating it as friction, and that disposition can be tested directly during the process.
When should a fintech hire a Head of Platform?
Usually earlier than planned, and specifically before the architecture starts to decay rather than after. The common sequence is that a founding CTO carries strategy, organisation and design simultaneously until the organisational load crowds out the design work, at which point the platform hire arrives alongside a rebuild. Hiring roughly a year before that point costs the same salary and avoids the rebuild.