omniXM
Associate Product Manager
- Eligibility
- Not stated
- Batch
- 2022–2025
- Experience
- 1–3 years
- Salary
- ₹10–20 LPA
How well do you fit this role?
Your resume against this posting — what you have, what’s missing, and a short plan to close the gap.
PDF or text, up to 4 MB. It stays in this browser — nothing is saved to your account.
About this role
About the role: - Work with Engineering, QA, and teams across the organisation to keep product development moving forward. - Own the tracking of project phases, key milestones, task dependencies, expected outputs, and version launches. - Handle the full lifecycle of technical issues, including tickets logged by engineers, problems in live systems, faults reported by customers, and new requests. - Watch over ticket severity levels, how fast issues get resolved, and whether the team meets its SLA targets. - Write core product specifications: Business Requirement Documents, Product Requirement Documents, Functional Requirement Documents, individual user stories, and acceptance criteria that define what done looks like. - Shepherd the team through sprint planning, retrospectives, release sign-off, user acceptance testing, and post-launch checks. - Build and maintain tracking spreadsheets, performance dashboards, and regular status snapshots for leadership. - Spot where processes break down and push the team to work smarter. What we're looking for: - 1–3 years working in Product Management, Product Operations, Project Coordination, or comparable capacity. - Solid grasp of Agile and Scrum frameworks, and how software moves from concept to production. - Hands-on experience with Jira, Azure DevOps, or equivalent project management platforms. - Working knowledge of SaaS architecture, how APIs and integrations work, and emerging ideas in AI and LLM technology. - Ability to explain complex ideas clearly to any audience, spot patterns in data, write with precision, and untangle knotty problems. About you: - You thrive on coordination and detail work that keeps a team aligned. - You're comfortable with technical concepts even if you're not writing code yourself. - You see broken processes as puzzles to solve, not obstacles to accept.