How to Choose an Executive Search Firm for Infrastructure & Real Estate Leadership Hiring

A specialist firm organises its partners around sectors and runs the majority of its mandates within a narrow set of practices; a generalist firm distributes mandates across partners by availability. In infrastructure specifically, the verification is structural. Ask how many CXO placements the firm has completed in infrastructure and real estate in the last twenty-four months, what percentage of annual mandate volume that represents, what sub-sectors those placements covered (EPC, developer, InvIT portfolio, REIT, fund-owned operator), and which sector bodies or industry-association roles the practice partner holds. A specialist answers in specifics within two minutes. A generalist pivots to brand strength or global reach.

The strongest proxies are structural rather than reputational. Ask the firm to share anonymised summaries of its last three infrastructure CXO placements — the mandate context, the capital structure of the hiring company, the shortlist size, the time to close, and the current status of the placed candidate at twelve and twenty-four months. Ask for a written process document describing the weekly operating cadence. Ask to speak with the partner who would actually run your mandate, not the relationship lead. A firm that can produce all three within forty-eight hours has the operational discipline that predicts quality; one that cannot is selling brand equity rather than search capability.

Four question sets separate capable firms from confident ones. First, sector and mandate specifics: name three infrastructure placements in the last two years across different capital structures and describe why each succeeded or failed. Second, process: what is your written weekly cadence and how do I see progress without asking? Third, assessment: how do you evaluate cultural fit beyond the résumé for a family-to-institutional or EPC-to-InvIT transition? Fourth, commercials and post-placement: how are fees staged, what is the guarantee window, and what is the structured integration process past day thirty, given the state-level stakeholder density of the role? A firm that answers all four with specifics has a point of view; one that deflects to brand or global network does not.

Heavily. Infrastructure is the sector in which generalist coverage most visibly underperforms, because the leader pool fragments across operating models that do not substitute for each other — an EPC COO is not an InvIT COO, a listed developer CFO is not a fund-portfolio CFO. Global brand firms can win infrastructure mandates on relationship capital and geographic reach, but the mandate itself typically gets run by an associate whose sector depth is formed after the brief. A specialist partner with a smaller brand and a continuous sector map will usually outperform a generalist partner with a larger brand and a standing start. Category is a proxy. Partner is the unit of decision.

Three structural differences. First, the leader pool is fragmented across distinct operating models — EPC contracting, developer management, fund-owned concession operation, InvIT portfolio leadership, REIT platforms — and the CVs do not interchange cleanly. A search calibrated for one model will under-source the others. Second, the geography is dispersed and site-heavy; cultural fit must include willingness to operate across 3–5 state jurisdictions and engage directly with state-level government. Third, timelines matter in a different register: project milestones, concession penalty clocks, and RERA or SEBI disclosure windows run independently of the hiring cycle, so a week lost in search translates to visible consequence later. These make domain depth — Rule 1 — the entire brief rather than a nice-to-have.

Four tests. First, has the firm placed a comparable Project Director or COO in a project of similar ticket size and complexity in the last twenty-four months — and can it name the outcome? Second, does the assessment probe dispute-handling with subcontractors, state-level permitting, and incident response — not just technical delivery credentials? Third, does the reference conversation include site lieutenants and client-side counterparts, not only former managers? Fourth, does the firm understand the difference between a contracting-culture Project Director and a developer-culture one, and has it mapped candidates across both — because the wrong source pool is a common failure mode. A firm that treats the role as "senior operations" has not done the work.

Listing-readiness is a distinct credential, not a generic capital-markets competence. A REIT or InvIT CEO, CFO, or head of asset management needs sponsor-independence temperament, investor-reporting cadence discipline, regulator relationship credibility, and fluency with the specific REIT or InvIT regulatory regime. Most EPC, developer, and fund-side CVs do not carry all four. A credible search firm for these mandates maps candidates across listed-entity governance experience, not only project-delivery experience, and probes the candidate's track record on distribution discipline, capital recycling, and sponsor-independent disclosure. Ask the firm how many listed-infrastructure-entity placements it has completed; if the answer is zero, the learning will happen on your mandate.

Cross-culture infrastructure moves fail most often on pace-of-decision mismatch and risk-appetite gap, not on technical capability. A leader from a listed EPC is used to committee-paced capital approvals, standardised bid-margin discipline, and process-led execution; a family-held or PE-backed developer typically runs faster, with lower decision latency and higher founder-influence on risk. A credible search firm names this dimension in the briefing, tests the candidate through structured scenarios — "describe the last major project decision that was escalated to the promoter and how you closed it" — and triangulates through references with peers who have made the same cultural move. Firms that reduce fit to chemistry at the interview table add no value to this specific risk.

A credible infrastructure CXO search runs ninety to one hundred and twenty days from mandate kick-off to signed offer, with another thirty to sixty days to full onboarding across site and government-stakeholder introductions. Variation is driven by three factors. First, sub-sector — an EPC CEO role with a deep existing pool reaches shortlist in six weeks; a REIT CEO role with a thin listed-entity pool can need ten. Second, capital structure — listed-entity replacements run slower because approaches are sequenced to protect disclosure integrity. Third, brief clarity — mandates that redefine mid-process because the board is still resolving EPC-versus-developer strategy restart the clock. A firm promising a CXO close in under sixty days is working from a pre-built shortlist or cutting assessment depth.

A healthy infrastructure mandate draws from three channels in roughly stable proportions. Direct approaches from continuous sector mapping typically produce the majority of the shortlist — sixty to seventy percent — because the leaders who have actually run large projects or listed-entity platforms are passive and insulated. Peer referrals from partner-level industry relationships account for fifteen to twenty-five percent; these are the candidates who take the call because a trusted consortium counterpart or former client said to. Database or active-applicant candidates are the remainder — five to fifteen percent, done honestly. A firm whose infrastructure shortlist is dominated by database or aggregator sourcing is running recruitment, not search.

Good-faith conduct is visible in three places. First, mapping depth — the firm produces a written longlist of forty to sixty candidates considered for an infrastructure CXO mandate, not just the four to six presented; you see what was mapped, not only what was selected. Second, rejection reasoning — each longlist candidate carries a one-line reason recorded, so you can calibrate the firm's filtering against your own priorities (e.g., "not pursued: insufficient REIT governance exposure"). Third, disagreement — the firm pushes back when the market demands it, proposes adjacent profiles when the brief is misaligned with the pool, and flags when the compensation band is out of range for the capital structure. A firm that never disagrees is either running a thin map or a sales process.

Retained search fees for infrastructure CXO mandates are a percentage of the hired executive's first-year total compensation, typically paid in three stages: engagement at mandate kick-off, shortlist on presentation, and placement on acceptance. Contingency fees are success-only, paid on placement, and generally lower — reflecting that the firm invests less upfront in mapping the fragmented infrastructure leader pool. The structural difference is not just commercial. Retained buys exclusivity, partner-level engagement, continuous sector mapping, and structured assessment; contingency buys speed and lower nominal cost, at the cost of depth. For infrastructure CXO hiring — where the wrong cultural or sub-sector match is exceptionally expensive — contingency is rarely the right model. A firm offering hybrid or discounted retained terms without explaining what is being compressed is a flag.

A credible guarantee has three properties, and infrastructure-specific considerations sharpen each. First, a written tenure window — typically six to twelve months for CXO-level placements, during which a replacement search is conducted at reduced or no additional fee if the placed candidate exits. Second, scope definition — the guarantee should cover voluntary exits and mutual-separation outcomes, not only terminations for cause; infrastructure first-year exits often surface as negotiated departures rather than clean terminations, and a narrow scope voids most guarantees in practice. Third, a structural backstop — some portion of the fee held against successful twelve-month tenure, not released on placement alone. Ask how the guarantee has been invoked on infrastructure mandates in the last twenty-four months. A firm with real accountability will have examples.

Gladwin demonstrates Rule 1 in infrastructure through structural organisation and continuous sector work. The Infrastructure & Real Estate practice is led by a partner who runs it full-time, with placements spanning EPC contractors, institutional developers, InvIT-portfolio companies, fund-owned operators, and REIT platforms. The practice maintains active coverage across roads and highways, urban infrastructure, energy transmission and renewables, airports and ports, water and waste, and real estate in residential, commercial, and logistics formats. Across 16 years of Gladwin practice and 500+ C-suite placements firm-wide, 55+ have been in infrastructure. Domain depth is not a claim; it is the organisation chart and the placement history.

Gladwin's approach to passive infrastructure talent (Rule 2) is built into how the practice operates between mandates. The Infrastructure partner maintains a live map of approximately 150 CXOs across six sub-sectors, updated through NHAI and state-utility briefings, sector body participation, consortium-bidding conversations, InvIT and REIT transaction flow, and investor conferences. When a role briefs, the partner already knows which ten to thirty leaders are worth approaching, which have been quietly open to a move, and which require a particular introduction route through a trusted consortium counterpart. The majority of placements reach us through this continuous-mapping channel rather than through the database. The database supports; it does not source.

Gladwin runs a six-month post-placement integration cadence on every infrastructure mandate, calibrated to the stakeholder density of the sector and aligned to Rule 9. The cadence includes a week-two calibration with the placed candidate and the hiring manager, a month-one structured check-in covering early team read and site familiarisation, a month-three read covering government and consortium stakeholder interfaces, a month-six performance calibration with the board or investor representative, and an off-ramp definition if friction is identified early. The cadence is not a service upgrade; it is the default. First-year infrastructure CXO failures are expensive and mostly preventable with attention past day thirty.

The fastest path is the consultation form on this page — start here. Submissions are reviewed by the Infrastructure & Real Estate practice partner within one business day, not by an associate or automated qualification layer. The form captures enough context (sub-sector, role level, timeline, capital structure) to calibrate the initial thirty-minute call under mutual confidentiality. No information is retained or contacted beyond that call without explicit permission. No databases. No cold outreach. If the timing is exploratory rather than immediate, the consultation still applies — the early conversation helps calibrate expectations on compensation, candidate pool depth, and realistic timeline.

Four pieces of information calibrate the first conversation faster. First, the role and seniority level (CXO, VP, Director, Senior Manager). Second, the sub-sector and capital structure — EPC contractor, listed or unlisted developer, InvIT or REIT platform, fund-owned operator, government SPV — because the partner assignment and mapping approach shifts accordingly. Third, the timeline — immediate, within four or eight weeks, or exploratory — which shapes partner availability and mapping investment. Fourth, one or two sentences on mandate context: replacement, new seat, turnaround, or succession. None of this is required upfront; start here and the rest emerges in the first call.