1. Agile Program Management :

- Drive and institutionalize Agile/Scrum processes across engineering teams.

- Work closely with Engineering, Product and QA teams to ensure effective sprint planning, execution and closure.

- Facilitate Sprint Planning, Daily Stand-ups, Backlog Grooming/Refinement, Sprint Reviews and Retrospectives.

- Track sprint commitments, velocity, capacity, spillovers and delivery predictability.

- Identify process gaps and continuously improve Agile maturity across teams.

- Ensure Agile ceremonies result in meaningful outcomes rather than becoming process formalities.

- Track dependencies across multiple teams and proactively identify execution risks.

2. Program Tracking & Execution :

- Own end-to-end tracking of technology programs from planning through release.

- Establish clear milestones, deliverables, owners, dependencies and timelines.

- Maintain program RAID logs covering Risks, Assumptions, Issues and Dependencies.

- Identify execution bottlenecks and drive teams toward timely resolution.

- Follow up rigorously on action items and commitments.

- Escalate risks and issues proactively with appropriate context and data.

- Work across Engineering, QA, Product, DevOps, Infrastructure, Security and other functions to ensure smooth execution.

3. Data-Driven Program Management :

- Build and maintain program dashboards and reports covering key engineering metrics.

- Analyze data from Jira, Excel and other engineering/project management tools.

- Track metrics such as sprint velocity, commitment vs. delivery, spillovers, cycle time, lead time, defect trends, defect leakage, release readiness, deployment frequency, release stability, open risks/issues, dependency ageing and resource/capacity utilization.

- Identify trends, anomalies and execution risks from the data.

- Go beyond reporting numbers and provide analytical insights and recommendations.

- Create concise and management-friendly reports for senior leadership.

- Establish a strong culture of fact-based decision making.

4. Reporting & Communication :

- Own weekly/monthly technology program reporting.

- Consolidate information from multiple engineering and functional teams into a single accurate view.

- Present program health, progress, risks, dependencies and key decisions required.

- Prepare executive-level dashboards and management reports.

- Ensure reporting is accurate, consistent, data-backed, concise and action-oriented.

- Communicate complex technical and execution issues clearly to both technical and non-technical stakeholders.

5. Release Management :

- Have a strong understanding of the end-to-end software release lifecycle.

- Work with Engineering, QA, DevOps and Product teams to establish release readiness.

- Track feature readiness, development completion, QA completion, regression status, critical/high-priority defects, performance testing, infrastructure readiness, deployment readiness, rollback plans and production validation.

- Ensure release dependencies and risks are identified well in advance.

- Drive release go/no-go discussions using objective data and clearly defined criteria.

- Track post-release issues and ensure appropriate closure and RCA.

6. Technical Understanding :

- Understand engineering discussions and challenge assumptions where required; the role does not require full-time hands-on development.

- Working knowledge of SDLC, Agile/Scrum, software architecture fundamentals, APIs/backend systems, databases, DevOps and CI/CD, cloud/infrastructure fundamentals, QA/testing methodologies, production release processes, and monitoring/logging/incident management.

- Be able to understand what engineering teams are doing, why something is delayed, what the technical dependency is, and what the actual risk to the program is.

Tools & Technical Skills :

- Jira : advanced understanding of workflows, dashboards, reports, JQL and Agile metrics.

- Microsoft Excel : strong proficiency including Pivot Tables, VLOOKUP/XLOOKUP, SUMIFS/COUNTIFS, conditional logic, data analysis, charts and dashboards.

- PowerPoint / presentation tools : strong proficiency for management reporting.

- Good to have : Confluence, Power BI/Tableau, Git/GitHub/GitLab, CI/CD tools, cloud platforms and monitoring/observability tools.

Desired Background :

- 5 - 7 years of overall experience in software/technology organizations.

- Prior experience in Software Development, QA/Testing, Technical Project Management, Program Management or Engineering Operations.

- Candidates who started their careers in Development or QA and transitioned into TPM/Program Management are particularly preferred.

- Demonstrated experience working with multiple engineering teams and cross-functional stakeholders.

- Experience managing technology programs from requirement/planning through production release.

Core Competencies :

- Agile & Process Excellence : deep practical understanding of Agile/Scrum and ability to identify and improve ineffective processes.

- Analytical Thinking : extremely comfortable with data; strong attention to detail; ability to identify patterns, trends and anomalies and convert raw data into meaningful insights.

- Communication : excellent verbal and written communication, strong stakeholder management and interpersonal skills, and ability to communicate with engineers, QA, Product, DevOps and senior leadership.

- Execution Orientation : highly organized, structured, proactive and strong on ownership, follow-through and cross-functional execution.

- Problem Solving : ability to understand root causes, distinguish genuine technical risks from routine execution noise, and drive resolution without necessarily having direct authority.

Educational Qualification :

- Preferred : B.E. / B.Tech in Computer Science, Information Technology or related discipline; MCA.

- Equivalent technical education and relevant experience may also be considered.

What Success Looks Like :

- Provide leadership with a single, accurate and data-backed view of technology execution.

- Ensure Agile processes are being followed effectively and continuously improved.

- Identify delivery risks and dependencies before they become critical issues.

- Improve sprint and release predictability.

- Bring discipline and transparency to the software release process.

- Reduce execution bottlenecks through structured follow-up and cross-functional coordination.

- Build high-quality dashboards and reports that enable better decision making.

- Understand technical discussions sufficiently to identify gaps, challenge assumptions and escalate meaningful issues.

- Establish a culture of ownership, accountability, transparency and data-driven execution.