Director of Product Engineering — Interim, Logistics Technology GCC

The mandate

A divested logistics platform remains dependent on the seller's identity, data and deployment services after the transition deadline. The engineering director resigned amid repeated outages, leaving the India team without authority to trade separation work against customer commitments.

The interim must begin within three weeks for twelve months, ending when the temporary separation office closes. An internal product vice president will inherit the independent platform after a six-week shadow period.

Handover means all critical seller dependencies removed, platform availability above 99.9 per cent for a quarter, recovery objectives proven in a full exercise, and the successor holding a complete service and architecture ownership map.

The director may prioritise engineering, freeze risky feature releases and approve separation tooling below ₹75 lakh. Changes above ₹3 crore, extensions to transition-service agreements and customer contract concessions require executive approval; commercial product pricing is excluded.

Warehouse physical automation, global sales integration and new-market localisation sit beyond the mandate. The engineering team must first create a stable sovereign platform from the divested estate.

Why this seat is open

Transition-service expiry arrived before technical independence, turning architectural debt into contractual risk. Leadership departure removed the decision-maker who could protect separation capacity. A finite director will drive the platform through independence and then return ownership to the product organisation.

What you will own

• Inventory every seller dependency across identity, code, data, infrastructure, observability, support and deployment.
• Decide the removal sequence using transition expiry, outage exposure and achievable rollback.
• Establish protected engineering capacity and release gates for separation-critical work.
• Rehearse data, identity and infrastructure cutovers with customer-impact and recovery evidence.
• Build end-to-end service ownership linking code repositories, runbooks, telemetry, on-call and third parties.
• Prove recovery time and data-loss objectives through a full independent-platform resilience exercise.
• Transfer architecture decisions and service accountability to the internal successor during six weeks of live operation.

Candidate qualifications

• Eighteen-plus years in product engineering, including leadership of SaaS or logistics platforms with high availability.
• Completed a corporate carve-out, transition-service exit or comparable platform-separation programme.
• Deep experience in identity, data segregation, cloud infrastructure, CI/CD, observability and service resilience.
• Evidence of protecting technical-debt capacity against feature pressure during a binding separation deadline.
• Ability to translate architecture dependency into financial, contractual and customer-operating exposure.
• History of returning a programme-built engineering organisation to stable line ownership.

Non-negotiables

• Available in Pune within three weeks and able to support critical global cutovers.
• No current role with the seller, transition-service vendors or direct logistics-platform competitors.
• Prepared to freeze features when separation or resilience evidence is inadequate.
• Commits to the fixed twelve-month independence window.

1. 49 words maximum. When can you start, and which global cutover hours can you support from Pune?
2. 49 words maximum. What transition-service dependency did you remove closest to contractual expiry?
3. 49 words maximum. Which recovery objective have you proven in a full platform exercise?