How should an executive evaluate logistics and supply-chain CEO jobs in India?

Ask where the promise breaks, how customer segments differ and which exceptions consume disproportionate capacity. Determine whether growth requires more density, a different proposition, stronger execution or a redesigned network. Treat that distinction as the first gate. Keep contrary evidence with its source. Do not let interview momentum settle it.

Write a customer-to-network equation covering service commitment, capacity pattern, operating choice and economic consequence. Use it to screen expansion plans and executive targets. Revenue growth or footprint alone cannot establish that the underlying customer promise is differentiated or economically durable.

A logistics company can celebrate rapid customer acquisition while each exception quietly changes the network it is operating. The contradiction is growth measured as revenue even when the customer promise, density and capacity pattern no longer support reliable economics. Select three materially different customer cohorts and trace promised service, lane or facility demand, exception frequency, recovery work and contribution after operational complexity. Commercial proposals, route plans, service-failure records and post-launch reviews provide the relevant evidence. The CEO consequence is a network that appears to scale in aggregate while frontline teams subsidise difficult accounts through overtime, empty movement and manual intervention. Define the chosen customer promise and the operating equation that makes it durable, then use both to screen new business. Stop if sponsors refuse customer-level economic review, describe every service exception as temporary, or expect the incoming leader to preserve all volume while simultaneously improving reliability, working capital and margin.

Ask how utilisation, empty movement, service failure, subcontracting and working capital enter decisions. Explore which costs appear only after commercial commitments and how customer-specific complexity is priced. Turn the gap into an authority question. Ask for one contested decision. Record who resolved it and how.

Trace one new-customer case from commercial assumption through network effect and post-launch review. Identify where the organisation can reprice, redesign or exit if the evidence differs. Candidate access cannot validate unit economics; authorised operational and financial evidence is required before any conclusion.

A blended enterprise margin can look healthy while specific routes, facilities or customers consume cash and capacity. The contradiction is a CEO held to network economics without the granular evidence needed to govern them. Reconstruct one new-customer case from pricing assumptions through route design, subcontracting, service recovery, working capital and the first post-launch review. Compare expected utilisation with actual empty movement, handling variation and exception cost. The executive consequence of obscured economics is that expansion decisions reward volume at the moment the operating system becomes less coherent, leaving the CEO to repair commitments already embedded in customer expectations. Require a recurring contribution view by customer, lane, site and service, with authority to reprice, redesign or exit when assumptions fail. Stop if finance and operations cannot reconcile the same case, if post-launch economics are never reviewed, or if diligence access ends at enterprise EBITDA while the role is expected to promise profitable density.

Map contract lock-ins, concentration, service dependencies and capital commitments. Ask who can alter the mix when demand shape changes and how transition risk is represented. Test the commitment under visible pressure. Record who accepts the cost. Name who can reverse the choice.

Build an asset-choice ledger with strategic control, flexibility, service consequence and lifecycle economics. Use it to separate a procurement exercise from a business-model decision. An asset-light or asset-heavy label does not determine quality; the relevant question is whether the model supports the chosen customer promise.

An asset-light narrative can conceal deep dependence on a few partners, while an asset-heavy narrative can conceal inflexible capital. The contradiction is treating the label as strategy rather than asking whether the asset mix serves the chosen customer promise. Review owned equipment, leases, subcontractor concentration, facility commitments and technology dependencies against demand volatility and service-critical routes. Contract terms, partner performance records and lifecycle cost comparisons should show who bears transition risk when the demand shape changes. The CEO consequence is strategic paralysis: the leader may be accountable for service and cash while unable to alter a partner, site or fleet choice inherited under a different model. Build an asset-choice ledger that records control, flexibility, economic consequence and alternate path for each critical element. Stop if major commitments cannot be examined, if related partners are protected from performance comparison, or if sponsors demand a model change while declaring every material contract and facility outside the incoming CEO's authority.

Ask how local exceptions are governed, which measures leaders share and how customer urgency affects safety, quality and cost decisions. Examine whether business-unit boundaries prevent network optimisation. Price the uncertainty before it compounds. Separate verified conditions from working assumptions. Give each gap an accountable source.

Follow one service failure from signal through recovery and systemic correction. Confirm who can impose a network-wide change and who protects local continuity during transition. Executive reporting does not establish that the CEO can alter frontline behaviour or partner execution without operational mechanisms.

Network accountability becomes hollow when the CEO can review frontline performance but cannot change site leadership, incentives or operating standards. The contradiction is enterprise responsibility delivered through local autonomy with no mechanism for resolving persistent exceptions. Follow a significant service failure from the first operational signal through customer recovery, root-cause action and network-wide learning. Shift records, site reviews, partner scorecards and incentive measures will reveal whether correction survives local pressure. The executive consequence is repeated firefighting and a growing gap between reported recovery and changed behaviour, with safety, quality and cost trade-offs made differently at every node. Require a clear route to impose common standards while protecting justified local continuity, including consequences for leaders and partners who do not act. Stop if business-unit boundaries prevent a network correction, if customer urgency routinely bypasses safety or control disciplines, or if site access is restricted while the CEO is asked to guarantee service reliability.

Warnings include every exception described as temporary, technology expected to repair an unclear operating model and expansion rewarded without post-launch economics. A broad CEO title may also conceal dependence on owner-led commercial decisions. Write the threshold before final-stage momentum. Reopen only on authorised evidence. Keep reassurance outside the proof record.

Set gates for customer promise, economics, asset freedom, operating authority and sponsor thesis. Decline if the organisation values a scale narrative more than the evidence needed to govern it. The decision evaluates mandate integrity and does not assess a logistics provider, customer, route or current service outcome.

A logistics CEO process should stop when the scale story becomes more detailed as the underlying customer economics become less accessible. Test customer promise, route and facility contribution, asset freedom, frontline authority and owner-led commercial exceptions as one connected system. Evidence must include a recent expansion case, a service-failure correction and the decision rights over pricing, capacity and partners. The executive consequence of unresolved gaps is accountability for an enterprise whose reported growth is separated from the operating choices that determine cash and reliability. Record each gap as a pre-appointment gate, with a source and responsible sponsor, rather than a first-hundred-days discovery. Stop if technology is presented as the cure for an undefined operating model, if expansion is rewarded without post-launch economics, or if the owner retains commercial commitments that the CEO cannot challenge. Declining such a role assesses mandate integrity and does not judge a provider, customer, route or current service level.