HireHire › Showpad jobs › GTM Project Manager

GTM Project Manager

Apply for this role or explore on the map →

Job & Department Summary

Showpad’s Revenue Operations team owns the systems, data, and operating processes that allow the go-to-market organization to sell, service, and grow revenue. The team spans five disciplines — GTM Systems, Deal Desk, Business Intelligence, Sales Operations, and GTM Strategy — across North America, EMEA, and India.

The GTM Project Manager exists to make that team deliver predictably. Today, Revenue Operations runs a large and highly interdependent portfolio, and the senior specialists who should be solving commercial and technical problems are instead managing their own project logistics: chasing stakeholders, scheduling follow-ups, keeping tickets current, and reporting status. This role takes that work off them and does it better.

The role is based in Pune and reports to the Director, GTM Strategy. It supports the entire Revenue Operations team rather than any single function, and it is deliberately positioned as a delivery role, not an administrative one. The person in this seat is expected to hold senior stakeholders to commitments, surface risk before a date slips rather than after, and own a subset of projects end to end.

How the role splits

Approximately 25% of the role is ownership of the Revenue Operations backlog in Jira: data accuracy, delivery governance, reporting, cadence, and direct management of selected projects. The remaining 75% is embedded delivery support across Deal Desk, Business Intelligence, GTM Systems, Sales Operations, and GTM Strategy — driving the cross-functional projects those functions depend on, and unblocking the dependencies between them.

Why this role matters

Revenue Operations sits upstream of the company’s ability to quote, book, forecast, renew, and report. When a Revenue Operations project slips, a sales team loses visibility, a renewal notification does not send, or an executive forecast is built on incomplete data. This role is the difference between a capable team and a team that reliably lands what it commits to.

 

Key Responsibilities

Jira Backlog Ownership and Delivery Governance (approximately 25%)

  • Own the Revenue Operations project backlog in Jira as the single accountable person for its accuracy, structure, and currency.
  • Maintain completeness of required fields on every ticket — assignee, effort, impact, ELT sponsor, functional sponsor, priority, target date, and confidence level — and run a regular triage cadence to close gaps rather than accumulate them.
  • Run the team stand-ups, including agenda, follow-ups, and documented actions.
  • Track delivery dates and confidence levels across the portfolio, and escalate items trending toward a slip early enough that the date can be defended or renegotiated deliberately.
  • Produce the recurring delivery reporting used by Revenue Operations leadership and executive stakeholders, including weekly progress summaries and the monthly roadmap view organized by executive sponsor.
  • Directly manage a defined subset of projects end to end — scoping, planning, coordination, delivery, and closeout.
  • Maintain the distinction between business-as-usual requests and project work so that ad hoc demand does not silently consume roadmap capacity.

Program Delivery Support Across Revenue Operations (approximately 75%)