Technical Program Manager
Program Manager:
About the role
We need a hands-on Program Manager who can build and run plans across multiple engineering groups and projects — not a coordinator who only collects status. Will work in Kochi with US-based leadership, persist through ambiguity, and make progress visible when teams do not share a single backlog or manager.
Will use Jira as the system of record and AI to help build, maintain, and report on project and program plans. Comfortable in both Agile delivery and standard project management, and you can present status clearly to executives.
This is a program-level seat: several workstreams, dependencies, and stakeholders. You get into the work — plans, risks, Jira hygiene, follow-through — rather than managing the process from a distance.
Responsibilities :
Area - You will
Program plans - Build and maintain program and project plans: scope, milestones, dependencies, owners, and dates. Keep them current as engineering work moves.
Jira and reporting - Use Jira as the live plan. Structure epics, versions, and dashboards so status is pulled from the work, not rebuilt in slides. Use AI to draft, update, and report on plans while keeping them verified.
Cross-group delivery - Work across multiple engineering groups and projects. Translate between teams that operate differently. Chase dependencies and decisions until they land.
Cadence and status - Run a reliable status rhythm. Produce executive-ready updates: progress, risks, asks, and what changed. Present, do not only email a deck.
Risks and follow-through - Surface risks early, drive mitigation, and do not drop issues across teams. Tenacious close-the-loop ownership.
Ways of working - Apply Agile where teams sprint, and standard project management where programs need milestones, gates, and integrated plans. Do not force one method on every workstream.
Required qualifications
Area - Expectation
Project and program management - 2+ years' experience managing projects and operating at program level: multiple workstreams, dependencies, and stakeholders — not only a single team sprint board.
Hands-on Jira - At least 2 years hands-on with Jira. Building and reporting on plans (epics, roadmaps or equivalent, filters, dashboards). You configure and maintain the plan; you do not wait for someone else to update tickets.
AI for planning - Some experience using AI in project management; (build, maintain, and report on project plans, with human review).
Agile and traditional PM - Experienced with Agile delivery and standard project management (schedules, milestones, RAID/risk logs, integrated plans).
Executive communication - Comfortable with executive presentations and status: concise, current, and clear on asks.
Cross-team influence - Soft skills and working access to operate across groups that are not one org chart. Builds trust, gets information, and keeps work moving without formal authority over every team.
Working style - Hands-on and tenacious. Based in Kochi; collaborates with US-based leadership and local engineering teams.
Nice to have
Not required. Useful signal for candidates.
Area - Examples
Engineering background - Technical background in software engineering (or equivalent) — enough to understand delivery, estimates, and dependencies on a Java/SaaS estate.
Jira depth - Advanced Roadmaps, Structure, Automation, or similar. Confluence for program docs and decision logs.
Credentials - PMP, PMI-ACP, CSM, or equivalent — credentials do not replace hands-on plan ownership.
Healthcare - Healthcare IT, ambulatory, or similarly regulated product delivery.
Hours - Comfortable overlapping US morning for executive status.
Location: Kochi, India (US-hours overlap required)
Reports to: Head of Engineering