Job Application for Technical Delivery Manager

← Back to Careers

We are looking for

A Technical Delivery Manager who takes complete ownership of client projects and delivers them. This is a customer facing role. You will be the person the client calls, and the person accountable when a date is at risk. You will run 2 to 4 concurrent product development projects and lead a team of roughly 10 to 20 engineers across hardware, firmware, embedded and application layers, working through Tech Leads.

This is a delivery-first role, not a design role. You are not expected to review schematics or PCB layouts; the Tech Leads own design correctness. You are expected to be technically literate enough to follow the engineering discussion, challenge an estimate that does not add up, recognise a risk before it becomes a slip, unblock your team quickly, and explain any of it to a client in plain language.

The person we are looking for treats a committed date as a promise, chases closure rather than reporting status, and would rather flag a problem early than explain a missed milestone later.

Should have the following responsibilities and background

1. Delivery Ownership

• Own end to end delivery of assigned client projects: scope, schedule, effort, quality and the final handover.
• Break scope into phases, milestones and deliverables with clear acceptance criteria, and build realistic schedules with the Tech Leads.
• Track progress against plan daily, not weekly, and act on variance the same week it appears.
• Drive milestone closure: prototypes, design reviews, firmware releases, test cycles, certification inputs and customer sign-offs.
• Maintain a single, current source of truth for plan, status, risks and open actions on every project.
• Run project closure properly: deliverables handed over, documentation complete, lessons captured.

2. Client Ownership and Communication

• Act as the primary point of contact for the client on all delivery matters: requirements, reviews, milestone demos, change requests and escalations.
• Run regular client review calls with a prepared agenda and circulate minutes with owners and dates.
• Translate client requirements into clear internal briefs, and translate engineering reality into language a client can act on.
• Communicate risk, delay and trade-offs proactively. No surprises at a milestone.
• Handle escalations with root cause, impact and corrective action, and follow through until the client confirms closure.
• Build long-term client confidence through consistent delivery and transparent, professional communication.
• Work across timezones with clients in Europe and the US, including occasional early or late calls.
• Identify scope creep early, raise change requests with management, and protect both the schedule and the commercial position.

3. Daily Team Review and Unblocking

• Run the daily rhythm: stand-ups and review calls with clear outcomes, owners and dates.
• Know at all times what every engineer is working on, what is blocked, and what is at risk.
• Get in and help when the team is stuck: pull in the right expert, break the problem down, take the decision, or escalate quickly. Do not let an engineer sit blocked for days.
• Chase dependencies actively: vendors, component availability, test labs, client inputs and internal teams.
• Ensure decisions taken in a call are written down, assigned and tracked to closure.

4. Team Management and Resource Allocation

• Allocate engineers across projects and tasks based on skill, load and priority, and rebalance as priorities change.
• Maintain a forward view of capacity: who becomes free when, where the next crunch is, and where a hire or a reallocation is needed.
• Work with Tech Leads on task assignment, review load and technical growth of the team.
• Onboard new engineers into projects quickly and productively.
• Give regular, direct feedback; support appraisals; recognise good work and address under-performance early.
• Reduce single-point dependency by insisting on documentation, cross-training and shared ownership.

5. Risk, Quality and Reporting

• Maintain a live risk register per project with owner, mitigation and review date.
• Escalate internally early and with a recommendation, not merely a problem.
• Ensure agreed engineering processes are followed: design reviews, code reviews, test coverage, version control and release discipline.
• Own the weekly status report to the client and to management: progress, plan versus actual, risks, decisions needed.
• Track effort against estimate and feed the learning back into future estimation.
• Contribute to improving delivery process, templates and review checklists across the company.

Skills and Experience Required

• Delivery Ownership: Proven track record of owning multi-month client projects end to end and hitting committed dates, or of recovering projects that had slipped.
• Technical Literacy: Able to read a system architecture, understand hardware, firmware, embedded and application layers, follow a technical debate, and judge whether an estimate or a proposed fix is credible. Design authority stays with the Tech Leads.
• Client Communication: Excellent spoken and written English. Confident running reviews, demos and difficult conversations directly with European and US clients, technical and non-technical.
• Team Leadership: Experience leading 10 to 20 engineers through Tech Leads: daily reviews, task allocation, performance conversations, mentoring and conflict resolution.
• Resource & Capacity Planning: Planning engineer allocation across parallel projects, spotting over-commitment early, and negotiating trade-offs with management rather than absorbing them silently.
• Estimation & Planning: Breaking a scope into phases, milestones and deliverables; building schedules that survive contact with reality; tracking effort against plan.
• Risk & Escalation: Identifying slippage, dependency and quality risks early; raising them with root cause, impact and a recommended action, not just a problem statement.
• Process & Reporting: Running structured reviews with documented findings and closure tracking. Weekly status reporting that a client can read and trust.
• Tools: Jira, Azure DevOps, MS Project or similar; Git-based workflows; Confluence or equivalent documentation practice; Excel or Power BI for effort and status tracking.
• Commercial Awareness: Understanding of scope, change requests, effort versus billing, and how a delivery decision affects project margin.

Technical Background Expected

You do not need to be a practising designer. You do need to have come from a technical background and be able to hold a technical conversation credibly with both your team and the client.

• Engineering degree in Electronics, Electronics and Telecommunication, Computer Science, Electrical or a related field.
• Working understanding of the electronics product development lifecycle: requirements, architecture, schematic and PCB design, prototype build, bring-up, firmware development, integration, testing and certification.
• Familiarity with the vocabulary and typical risks of embedded development: microcontrollers, RTOS, embedded Linux, communication protocols such as SPI, I2C, UART, USB, Ethernet, Wi-Fi and BLE, and cloud or IoT connectivity.
• Awareness of what certification cycles such as CE, FCC, UL and BIS involve in terms of time and cost.
• Enough hands-on history, ideally as a former engineer or tech lead, to tell a real technical constraint from an excuse.

Preferred Skills (Added Advantage)

• Experience in a product design services, outsourced product development or contract engineering environment.
• Experience delivering to European or US clients, particularly startups.
• Exposure to IoT or IoMT (Internet of Medical Things) projects, and to regulated development such as ISO 13485.
• PMP, Prince2 or Agile or Scrum certification. A proven delivery record matters more than a certificate.
• Working knowledge of German or another European language.
• Experience setting up or improving delivery processes and reporting from scratch.

Qualifications

• B.E. / B.Tech / M.E. / M.Tech in Electronics, Electronics and Telecommunication, Computer Science, Electrical Engineering or a related field. MBA is optional and not a substitute for delivery experience.
• 8 to 12 years of total experience, with at least 3 years owning delivery of technical projects and managing teams.
• Demonstrable record of projects delivered, with dates, team size and client outcomes you can talk through in detail.
• Excellent verbal and written communication in English. This is non-negotiable for a customer facing role.
• Based in Pune or willing to relocate. This is an in-office role with occasional client travel.

What Success Looks Like

• Clients contact you first and trust what you tell them about status and dates.
• No milestone slips without the client and management having known well in advance, with a plan already in motion.
• Engineers are rarely blocked for more than a day.
• Management can ask about any project at any time and get an accurate answer immediately.
• Delivery does not depend on any single individual, including you.

Will have the following remuneration and work location

• CTC Range: As per industry standard for relevant experience.
• Pune, Wakad Office.