CTO, CIO and technology leadership jobs

What a free account opens, and what Foresight adds

Reading is free here, and that is not a trial — every one of these 399 briefs opens in full without paying. What a membership buys is the ability to act on them at volume, to reach the ones outside India, and to be found by them while you are working.

Counted against the 399 open technology leadership mandates on this page — 108 in India, 291 elsewhere. Prices are annual and all-inclusive, with GST already inside the figure shown; quarterly terms exist at a smaller allowance. Nothing on this page is behind any of them.

Why these seats are open

Every mandate here is filed with the reason it exists. It is the most useful column in the corpus and the one no job board carries.

A majority of these mandates are planned, but the urgent minority has an unusual shape: unplanned departures are almost exactly as common as planned replacements, which is not true in any other function on this platform. Technology leaders leave mid-flight more often than finance chiefs or general managers do, and the corpus records it.

That matters because of what an unplanned technology departure does to a company. The programme stops. The vendor reopens the commercials. And the board discovers how much of the plan lived in one person's head rather than in a document. Those seats are filled in weeks rather than months, from a much shorter list, with an overwhelming preference for somebody who has landed the same transition before — which is why a specific, named prior transition on your record is worth more here than breadth.

The planned majority behave in the opposite way and reward the opposite behaviour. A board that has decided to replace a core platform briefs the leadership for it long before the programme is announced internally, because announcing a platform replacement before you have the person to run it is how a technology organisation starts losing its architects. Those mandates never appear anywhere public at any point in their life. You cannot check a page for a seat that was never posted, which is the argument for an agent rather than a browser.

Closing soonest

173 of these mandates carry a published deadline, and 0 of those fall inside the next fortnight. A seat with no date is not less real — a board that has not set one should not have one invented for it.

• Thu, 15 Oct18 daysPrincipal Tax Classification Architect — Withholding and Contract ControlsHyderabad, India · Cross-Border Technology Services · consulting
• Thu, 15 Oct18 daysPrincipal Cash Conversion Architect — Education Services Billing and Collection EvidenceDelhi NCR, India · Education Services Cash-Conversion Controls · consulting
• Mon, 26 Oct29 daysInterim Chief Technology Officer — Telecom 5G RecoveryDelhi NCR, India · Telecommunications · interim
• Mon, 26 Oct29 daysAccount-Based Fare Platform Recovery Leader — Public TransportSantiago, Chile · Metropolitan Public Transport · interim
• Mon, 26 Oct29 daysDistributed-Energy Market Platform Recovery Leader — Urban GridHouston, United States · Urban Electricity Distribution · interim
• Mon, 26 Oct29 daysChief Technology Officer — Commercial Launch OrganisationDublin, Ireland · Pharmaceuticals · permanent
• Mon, 26 Oct29 daysChief Information Officer — Home-Care DivisionAmsterdam, Netherlands · Consumer Goods · permanent
• Mon, 26 Oct29 daysDrinking-Water Quality Platform Recovery Authority — Urban UtilityCape Town, South Africa · Municipal Drinking Water · interim

Counted at the last refresh of this page, which runs hourly. The mandate itself is the authority on whether it is still open.

Where these mandates come from

• Jobs Directly Posted by Firms297
• Direct Mandates of Gladwin International43
• Jobs Posted by NRCs / Boards31
• Jobs Posted by Fellow Members27

Every mandate on this page arrived here deliberately. The largest group was posted directly by the hiring firm; the next largest are Gladwin's own retained and exclusive mandates. A smaller number come from nomination and remuneration committees filling board technology and assurance seats, and a smaller number again from members of the platform hiring into their own organisations.

What that list does not contain is anything scraped. At technology-leadership level an aggregated corpus is worse than useless, because the seats that get aggregated are the ones with a public job description — and a mandate with a public job description is by definition not the confidential programme a board is quietly staffing. Every brief here has a named person behind it who can tell you who the sponsor is, which is the one question that actually matters.

Your name stays yours

This used to be the last thing on the page. For a sitting finance chief it is the first question, so it has been moved to where it is actually asked.

Registering is free and anonymous to the hiring side. You are not in a database a company can browse, and nothing about you reaches a board until you approve a specific named seat. What goes then is a portfolio written for that board and that mandate — not a CV placed into circulation, which is how a confidential search stops being confidential.

A chief executive who is discovered to be looking has a career problem. A chief financial officer who is discovered to be looking has a governance problem, because the market reads it as a signal about the numbers. That asymmetry is the reason this platform is built the way it is, and the reason the seats worth having are never advertised.

How the Terminal places a technology leader

Read the mandate titles before you read anything else on this page.

The technology mandates on this platform are named after programmes rather than after functions. A core banking cutover. A generative-AI enterprise launch. A streaming reliability recovery. A low-carbon platform. That is not a naming convention; it is what the seats are. Boards here are not buying somebody to steward an IT function indefinitely — they are buying somebody to move a specific thing from one state to another, on a clock, with the business running throughout.

The reporting cut says the same thing from the other direction, and it is the most decisive figure in this corpus. Almost all of these seats report to a group chief executive or a designated executive-committee sponsor. Almost none report to a board technology committee. Technology here is an executive delivery problem, not a governance one — which is the reverse of how the finance corpus on this platform is shaped, and it changes what a candidate should present.

The Terminal runs four routes into that market and they are genuinely different products. A permanent seat is a function to be built and held. An interim seat is a programme in trouble, or a departure mid-flight. An advisory seat buys your judgement on an architecture or a vendor decision without your calendar. A consulting seat — the largest single group here — is a named engagement inside a firm or a portfolio, where you are the person brought in because this has been done before.

What every route shares is the order of operations. Nothing about you moves until you say it moves. Whisper reads the corpus against your record and proposes a named seat; you approve or decline it; a portfolio is written for that specific board and that specific programme; a curator reads it before it leaves; and Gladwin presents you under your Executive Passport. A chief technology officer in post whose search becomes visible has a retention problem inside their own engineering organisation within a fortnight, and that is the risk this sequence exists to remove.

What the technology corpus actually contains

A market of transitions, with a tight experience band and almost no room below it.

The experience distribution is narrow and it sits high: the overwhelming majority of these mandates want twenty-two to twenty-eight years, with a large adjacent group at eighteen to twenty-two and very little either side. There is almost nothing below twelve, and — unusually — not much above twenty-eight either. Technology leadership on this platform is a mid-to-late-career market with a ceiling, which is a genuinely different shape from general management, where the late-career end is the larger half.

The reason is visible in the mandates themselves. A cutover, a platform rebuild or an AI launch is a two-to-four year commitment with a hard technical core, and boards are buying somebody who is still close enough to the work to be able to tell when they are being told something untrue by their own architects. That capability decays, and the corpus prices it.

The hiring cut is more planned than urgent, but the urgent half is unusually evenly split between replacements and genuinely unplanned events. An unplanned technology departure mid-programme is among the most expensive things that can happen to a company — the programme stops, the vendor renegotiates, and the board discovers how much of the plan lived in one person's head. Those seats are filled fast, from a short list, with an overwhelming preference for somebody who has landed the same transition before.

A note on what is NOT here. This corpus is thin on pure engineering-leadership seats in product companies — the VP Engineering ladder — because those are filled through networks and specialist search rather than through board-adjacent mandates. What is here is technology leadership in enterprises where technology is the instrument of a business change, which is a different job with a different assessment.

The executive sponsor, and why that line is the whole brief

Most of these mandates report to a chief executive or to a designated executive-committee sponsor rather than to a board committee. That phrase — "designated executive-committee sponsor" — appears on more of these briefs than any other reporting line on the platform, and candidates routinely read past it.

It means the programme has a named owner above you who is not the chief executive, and that person's interest is not identical to the chief executive's. A cutover sponsored by a chief operating officer is a continuity project. The same cutover sponsored by a chief financial officer is a cost project. The same cutover sponsored by a chief risk officer is a remediation project ordered by somebody outside the company. The technology is identical; the definition of success is not, and the reason technology leaders are removed mid-programme is almost never technical.

The single most useful question to ask about one of these briefs is therefore who the sponsor is and what they are measured on. It is more informative than the stack, the team size or the budget, and it is answerable in one sentence by anybody genuinely close to the mandate. A brief where nobody can answer it is a brief where the programme has no owner, which is a different and much worse problem than a hard technical scope.

The small group of seats that DO report to a board technology committee are a different proposition again, and worth targeting deliberately if you are building towards a non-executive record. They are assurance seats in substance — the board wants an independent reading of whether what it is being told is true — and they are assessed on judgement and independence far more than on delivery.

How the same title differs by market

The stack survives translation. The authority does not.

In India, the largest concentration of these mandates by a wide margin, a great many sit inside global capability centres — and the structural question is whether the seat owns the technology or delivers it. A GCC technology leader with a global reporting line and a genuine product mandate is a different job from a GCC leader running delivery for a roadmap set elsewhere, and the two are frequently described in almost identical language. Candidates who do not establish which one they are reading arrive into a seat with far less authority than they expected.

In the Gulf, technology mandates are disproportionately greenfield and disproportionately sovereign-adjacent: a new platform, a new entity, a national programme. The technical work is frequently easier than in a legacy environment and the stakeholder work is much harder, because the timelines are political as well as commercial and the sponsor may not be inside the company at all.

In Western Europe and the United States, the defining feature is regulatory weight rather than scale. A technology leader in a regulated European business spends a materially larger share of their time on data residency, auditability and supervisory reporting than an equivalent leader in Asia, and a candidate whose record is all velocity and no evidence of operating under supervision reads as a risk rather than as an accelerator.

In Singapore and the APAC hubs, the pattern is span: a regional technology leader typically carries a dozen markets with different regulators, different vendors and wildly different levels of maturity, and the difficulty is in the aggregation rather than in any one market. Leaders who have run one large estate well are often underprepared for the multiplication.

Where these mandates are

• India108
• United States32
• Singapore20
• United Kingdom19
• United Arab Emirates17
• Netherlands13
• Switzerland13
• Germany13
• Japan11
• Australia10
• Denmark10
• France10

Counted from open mandates on 27 September 2026. 108 sit in India and 291 elsewhere; markets beyond the top 12 carry the remainder.

Who you would report to

The most revealing line on a brief, and the one candidates most often skip. 297 distinct reporting lines appear across these mandates.

• Group Chief Executive or designated executive committee sponsor69
• Group Chief Executive or designated executive-committee sponsor30
• Chief Executive Officer and the Board Technology Committee4

Lines named on fewer than four mandates are not shown — the tail is long by design, because a real board writes the structure it has rather than choosing from a menu.

The dominant reporting line on these mandates is a group chief executive or a designated executive-committee sponsor, and the contrast with the rest of the platform is stark: only a handful report to a board technology committee. Technology here is an executive delivery problem, not a governance one, and a candidate who prepares board-assurance evidence for an executive-delivery seat is answering a question nobody asked.

The phrase "designated executive-committee sponsor" carries more information than any other line on these briefs. It means the programme has an owner above you who is not the chief executive — and whose definition of success is their own. The same cutover sponsored by a chief operating officer, a chief financial officer or a chief risk officer is three different projects with three different failure modes, and technology leaders are removed mid-programme for misreading which one they are in far more often than for any technical reason.

The small number of seats reporting into a board technology committee are worth identifying and targeting separately. They are assurance roles in substance, assessed on independence and on the ability to explain technology risk to people without the vocabulary — and they are the natural first step towards a non-executive record for a technology leader, which is otherwise one of the harder board transitions to make.

How much experience these boards ask for

• 22–28 years190
• 18–22 years174
• 28+ years15

A further 20 mandates state the requirement in their own words rather than as a band — “proven controller responsibility”, “VP-level acquisition finance” — and are not bucketed here.

The band here is narrow and it has a ceiling. The overwhelming majority of these mandates sit between eighteen and twenty-eight years, with very little below and — unusually for this platform — not much above either. Technology leadership is a mid-to-late career market rather than a late-career one, which is the opposite shape to general management.

The reason is legible in the work. These seats are transitions with a hard technical core, and a board is buying somebody still close enough to the detail to know when their own architects are telling them something untrue. That closeness decays with distance from the work, and the corpus prices it. The practical implication for a leader past that band is to move towards the assurance and board-committee seats deliberately, rather than competing for delivery seats against candidates the market reads as nearer the code.

Four ways into this market, and they are different products

By work mode: 238 hybrid · 134 onsite · 27 remote. At this level the work is a board relationship and an external stakeholder rather than a set of deliverables, which is why genuinely remote seats are the smallest group.

The specialist hubs inside this market

The corpus is filed by specialisation as well as by title. A hub is the same market entered through the work rather than through the job title.

A hub page counts every specialisation inside it separately, which no other page on the platform does — it is the only way to see controllership measured against capital markets rather than both filed under “finance”.

What these seats pay

Technology leadership is the function where the gap between what a seat pays and what an equivalent-seniority seat pays elsewhere is widest, and the reason is that a large share of these mandates are programme-shaped. A two-year cutover with a hard deadline commands a premium over a steady-state function of the same size, and an interim programme seat commands a larger one again.

That premium is real and it is also a trap. A programme rate that looks excellent against a permanent salary is being paid for a role that ends, and the candidates who do best in this market price the whole arc — the engagement, the gap after it, and what the engagement makes them able to charge next — rather than the monthly figure. A leader who takes three well-paid recoveries in five years and has no steady-state record left is a harder candidate to place into a permanent chair than they expect.

The Terminal takes pay from the mandates themselves — the ranges boards actually briefed, not a survey. Where the sample is too thin to support a median, this page prints no median at all. What decides a technology move is rarely the headline anyway; it is the equity or programme incentive, whether it vests on delivery or on time, and what "delivery" is defined as in a contract somebody else drafted.

Becoming the apex professional in this field

The ladder into technology leadership is less standard than in finance, because the entry point differs so much by company type — an enterprise CIO, a product-company CTO and a services technology partner have almost nothing in common until the last rung. What is consistent is the sequence of things that stop people, and it is remarkably consistent: technical leaders are trusted with systems long before they are trusted with money, and trusted with money long before they are trusted with the business case.

The rungs below are drawn from what these mandates actually demand. The useful question at each step is not "is my architecture good enough" but "have I ever been the one who said what it would cost and by when, in front of people who would remember".

1. 01

   Engineering / Infrastructure Lead

   A system, a platform or a estate. Uptime, throughput, and the technical quality of what is built.

   What stops people here — Technical leaders at this level are assessed on whether the thing works, and an excellent record here proves nothing about judgement under cost or time pressure — because those constraints arrived pre-set from above.

   The bridge — Own a number the business is held to, not a number engineering is held to. A unit cost, a cost-to-serve, a capacity forecast tied to revenue. The first time you defend one of those in front of a finance function is the beginning of the record that matters later.

2. 02

   Head of Technology / Divisional CIO

   Technology for a business line — the roadmap, the vendors, the budget, and the arguments about all three.

   What stops people here — The divisional seat can be run entirely inside technology. A leader who has never sat on the other side of a vendor negotiation, never carried a regulator conversation, and never cancelled something they had championed has no evidence of independent judgement.

   The bridge — Take the vendor exit, the failed programme, or the regulatory finding. The corpus asks for evidence of a transition landed under supervision far more often than it asks for evidence of a system built, and the unglamorous work is where that evidence comes from.

3. 03

   Programme / Transformation Technology Lead

   A named transition with a deadline — a cutover, a migration, a platform replacement — and the business continuity around it.

   What stops people here — Programme leaders accumulate excellent delivery records and frequently no steady-state record at all. Boards hiring a permanent chief technology officer read a run of programmes as somebody who leaves before the consequences arrive.

   The bridge — Stay past the go-live. The eighteen months after a cutover — when the defects surface, the run costs land and the promised savings either appear or do not — are worth more in a chief-technology assessment than the cutover itself, and most candidates have left before them.

4. 04

   Group CTO / CIO

   The technology estate and the executive relationship. Architecture, spend, the build-versus-buy decisions, and the credibility of what the board is told.

   What stops people here — At this level the constraint is access rather than evidence. These seats are filled from a pool the chief executive or their advisers already know, and the most common reason a strong candidate is not considered is that nobody in the room thought of them.

   The bridge — This is what the platform is for. The chief executive filling this seat is choosing from people they have already met; named, confidential mandates put you in front of them first, and your record travels under a passport rather than as a CV your own architects could find.

5. 05

   Board Technology Committee / Independent Director

   Assurance rather than delivery. Telling a board whether what it is being told about technology risk is true.

   What stops people here — Independence is the qualification, and a long executive career in one sector disqualifies you from that sector. Most first-time candidates apply precisely where they are conflicted, and cyber or data experience alone is read as a specialist credential rather than a governance one.

   The bridge — Build the governance record deliberately — committee exposure from inside your executive seat, a first directorship in an adjacent industry, and a demonstrated ability to explain technology risk to people who do not have your vocabulary. The Terminal files these separately because boards assess them separately.

The technology CV a non-technical board can actually read

It will be read by a chief executive, a chief financial officer and possibly a chair. None of them will read the stack.

The commonest failure in a senior technology CV is that it is written for another technologist. It lists platforms, cloud providers, methodologies and team sizes, and it assumes the reader can convert those into business consequence. The people deciding these mandates cannot and will not. A line that names four technologies tells them nothing; a line that says a migration moved a business off a platform that was blocking a product launch, on time, with the launch happening, tells them everything.

The second failure is scale without stakes. A technology leader is read against what would have happened if it had gone wrong — the transactions, the customers, the regulatory exposure, the revenue that depended on the thing staying up. A CV that gives team size and budget but never establishes what was at risk forces the reader to assume the lower bound, and readers reliably do.

The third is the absent cost line. Almost every one of these mandates is, underneath, a question about money — whether the estate costs what it should, whether the programme will land inside its number, whether the run cost after go-live was the one that was promised. A senior technology CV containing no cost outcome anywhere reads as somebody who has spent budget rather than managed it, and that is a disqualifying reading at group level.

For a board technology seat the document changes in kind. It leads with governance and judgement: committee exposure, the sectors in which you are genuinely independent, the specific assurance question you are equipped to ask, and evidence of having explained technology risk to people without your vocabulary. An executive technology CV submitted for a board seat reads as a candidate who has not understood the difference between running the estate and assuring it.

Every mandate here asks three questions before you may apply

A specimen, not a live brief — the real questions describe the client's own programme and are not published. Every technology mandate on the Terminal carries three of them, authored for that seat.

1. 01This group is replacing a platform that three prior attempts failed to move off. Describe a comparable transition you have personally landed, and what you did differently from whoever tried before you.200 words
2. 02The seat reports to a designated executive-committee sponsor rather than to the chief executive. Describe an occasion when your sponsor's definition of success diverged from the company's, and how you handled it.150 words
3. 03Name a programme you led where the run cost after go-live was materially different from what was promised, and what you did about it.150 words

This is the filter, and it is the reason the platform is not a job board. A partner reads a considered answer to a real situation rather than a stack of documents, which means a strong candidate with an imperfect CV is read properly — and it means a speculative application costs you something, which is why the corpus stays worth reading.

CTO, CIO, chief digital officer and programme director

Four titles applied almost at random in adverts, and four different assessments behind them.

The technology titles are the least standardised on this platform. The same scope is called a chief technology officer in one company and a chief information officer in another, and "chief digital officer" can mean anything from a product organisation to a marketing technology budget. Reading the title alone is the least reliable way to understand one of these mandates.

The table below is drawn from how the mandates here are actually written — what the brief says the seat owns, who it reports to, and what the assessment turns on when a chief executive is choosing between two candidates who both look qualified on paper.

What a membership actually gets you

Open mandates in this market

20 of 399. Title, market and engagement are open to everyone; the brief itself opens with a free account.

• Engineering Planning Programme Director — Backlog-to-Forecast ArchitecturePune, India · Engineering Programme Planning Architecture · consulting
• Remuneration Committee Adviser — Pay Analytics InterpretationMumbai, India · Financial Services Reward Oversight · advisory
• Healthcare Performance Engineering Manager — Workflow Response ReadinessHyderabad, India · Healthcare Workflow Technology Services · permanent
• Senior Director Transfer Pricing — Software Value Creation and Agreement GovernanceBengaluru, India · Enterprise Software Development · permanent
• Principal Tax Data Assurance Specialist — Withholding Ledger and GST ReconciliationBengaluru, India · Technology Finance Operations · consulting
• Senior Director Tax Assurance — Digital Infrastructure Provisions and Controversy EvidenceHyderabad, India · Digital Infrastructure Services · permanent
• Senior Vice President GRC Platform Delivery — Banking Risk Workflow CoherenceMumbai, India · Banking Risk Technology · permanent
• Performance Engineering Service Manager — Test Evidence Continuity, InterimHyderabad, India · Retail and Healthcare Engineering Test Services · interim
• Senior Director Regional Indirect Tax — Technology Services Invoice and Supply PolicyHyderabad, India · Technology Managed Services · permanent
• Principal Director Fee-Service Profitability Analytics — Unit-Cost IntegrityMumbai, India · Financial Fee Services · consulting
• Principal Banking Process Re-Engineering Director — Service Exception RoutingPune, India · Banking Service Operations · consulting
• Principal Tax Classification Architect — Withholding and Contract ControlsHyderabad, India · Cross-Border Technology Services · consulting
• National Tax Head — Software Export Entities and Incentive Evidence ControlsBengaluru, India · Software Export Operations · permanent
• Principal Cash Conversion Architect — Education Services Billing and Collection EvidenceDelhi NCR, India · Education Services Cash-Conversion Controls · consulting
• Vice President, Engineering Group Reporting and Cross-border ControlsMumbai, India · Engineering Group Financial Reporting · permanent
• Principal Retail Performance Architect — Peak Transaction ResilienceHyderabad, India · Digital Retail Transaction Platforms · permanent
• Principal Integration Performance Architect — Dependency Capacity and Tail LatencyBengaluru, India · Retail and Healthcare Integration Platforms · permanent
• Technology Capital Allocation Board AdviserBengaluru, India · Digital Technology Holdings · advisory
• Communications-Platform M&A and Financing Strategy AdviserMumbai, India · Cloud Communications and CPaaS · advisory
• Manufacturing Infrastructure Security and Recovery-Evidence ConsultantBengaluru, India · Manufacturing · consulting

Questions and answers

How many CTO and CIO jobs are open right now?

399 technology-leadership mandates are open on the India Board Terminal today, across 52 markets, out of 3,088 open mandates in total. The figure is counted from the live corpus rather than written into the page, so it changes as boards brief and as seats close.

Why are so many of these named after programmes rather than functions?

Because that is what they are. A core banking cutover, an AI enterprise launch, a reliability recovery. Boards on this platform are overwhelmingly buying somebody to move a specific thing from one state to another on a clock, with the business running throughout — not somebody to steward an IT function indefinitely.

Who do these seats report to?

Almost all of them to a group chief executive or a designated executive-committee sponsor, and only a handful to a board technology committee. That is the reverse of the finance corpus here, and it means technology is being treated as an executive delivery problem rather than a governance one.

What does "designated executive-committee sponsor" actually mean?

That the programme has an owner above you who is not the chief executive, and whose definition of success is their own. The same cutover sponsored by a COO is a continuity project, by a CFO a cost project, by a CRO a remediation ordered from outside. Technology leaders are removed mid-programme for misreading which one they are in far more often than for anything technical.

Will my engineering organisation find out I am looking?

Not through this platform. Your name is not in a database a hiring side can browse, and nothing about you reaches a board until you approve a specific named seat. A technology chief whose search becomes visible has a retention problem inside their own engineering organisation within a fortnight — which is the risk this sequence exists to remove.

How much do these seats pay?

The pay section on this page shows the median of the ranges these boards actually briefed, with the sample size beside it, and shows none where the sample is too thin. Programme seats carry a real premium over steady-state functions of the same size, and interim programme seats a larger one again — but that premium is paid for a role that ends.

How many years of experience do these boards ask for?

The band is narrow and it has a ceiling: the overwhelming majority sit between eighteen and twenty-eight years, with very little below and, unusually, not much above either. Boards are buying somebody still close enough to the work to know when their own architects are telling them something untrue.

Is a run of interim programme roles bad for my career?

It is excellent for the next programme and progressively harder for a permanent chair. Boards hiring a group chief technology officer read a sequence of programmes as somebody who leaves before the consequences arrive. The fix is not fewer programmes — it is staying past one go-live and carrying the run cost that follows it.

What is the difference between a CTO and a CIO on these mandates?

Less than the titles suggest and more than candidates assume. A CIO here typically owns the estate the business runs on and is assessed on reliability and cost; a CTO owns what the company builds and is assessed on architectural judgement at scale. Many briefs use the wrong one, which is why the scope paragraph matters more than the title.

I work in a GCC. Do these mandates apply to me?

A very large share of the India mandates here sit inside global capability centres, and the question worth establishing before you apply is whether the seat owns the technology or delivers it. A GCC leader with a genuine product mandate and a global line is a different job from one running delivery for a roadmap set elsewhere, and the two are often described in almost identical language.

Do I need cloud or AI credentials?

The mandates ask for evidence of transitions landed, not for certifications. Where AI appears it is usually as a named programme — an enterprise launch, a governance build — and what is being tested is whether you have put something into production under supervision, not whether you can describe the technology.

How do I get onto a board technology committee?

Treat independence as the qualification. A long executive career in one sector disqualifies you from that sector, and cyber or data depth alone reads as a specialist credential rather than a governance one. The route that works is committee exposure from inside your executive seat, a first directorship in an adjacent industry, and demonstrated ability to explain technology risk to people without your vocabulary.

Are remote technology leadership roles real?

A small number genuinely are and the work-mode cut on this page counts them honestly, but the large majority are hybrid and a substantial minority fully onsite. A transition with a hard deadline is run in a room, and the mandates reflect that more than the wider technology market does.

What happens after I apply?

Every mandate here carries three questions written for that specific programme, and they must be answered before an application is accepted. They are usually about a comparable transition you have personally landed and what you did differently from whoever tried before you — which is the filter, and the reason a partner reads a considered answer rather than a stack of CVs.

How is this different from a technology recruiter?

A recruiter works a requisition and holds a handful at a time. This is a corpus of 399 open technology-leadership seats across 52 markets, read against your record by an agent, with your name withheld until you release it for a named seat — and with 129 of them currently urgent, which in this market means a programme that has lost its leader mid-flight.

The same corpus, entered elsewhere

• functionCFO and finance leadership jobs
• functionCOO and operations leadership jobs
• functionCEO, managing director and country head jobs
• sectorTechnology leadership jobs — CTO, CIO and engineering chiefs
• sectorBanking and financial services leadership jobs
• sectorInfrastructure, energy and utilities leadership jobs
• sectorManufacturing and industrial leadership jobs
• sectorLogistics, supply chain and mobility leadership jobs
• sectorConsumer, retail and FMCG leadership jobs
• sectorHealthcare, pharma and life sciences leadership jobs
• sectorMedia, entertainment and telecom leadership jobs