Technical Program Manager - 1

About the role

You will run the technical programmes for a payment instrument: a set of partner capabilities, a mandate, or a merchant-facing area such as refunds, webhooks or recurring payments. You make sure to work across engineering, Banking Alliances, segment PMs and TAM lands on time, on cost and in a way merchants can actually use. You work every day with the EM(s) and staff engineers, who own the technical design and partner tech work.

What you will do

• OKRs: Help set the payment instrument's programme OKRs and own one or two key results for your area, for example merchant integration time or a mandate deadline. Track them weekly and report progress.

• Requirements and plans: Turn asks from segment PMs, merchants and Compliance into clear requirements: use cases, merchant-facing behaviour, edge cases and acceptance criteria. Build the plan with the EM and keep it current.

• Partners and integrations: Work with Banking Alliances on which partner capabilities your area needs and what they cost. Make each integration succeed for merchants: the right pilot merchants, docs ready, TAM and Sales briefed, adoption tracked after go-live.

• APIs and SDKs: Know our merchant-facing APIs and SDKs well enough to answer most integration questions yourself. Review API specs for merchant integration experience. Own developer docs, integration guides and merchant-facing error messages for your area.

• Mandates: Run the programme for RBI, NPCI and network circulars in your area: work out the impact with Compliance, hand clear requirements to the EM, and track it to the deadline.

• Cross-team work: Track dependencies on other teams, shared platform teams, Risk and Finance systems, and clear blockers early.

• Merchant and business sense: Understand the problem behind each request and the cost and merchant impact of each choice. Use data to show what matters most.

What we are looking for

• 1–2 years in technical programme management, solutions engineering, integration or software engineering, ideally in payments or fintech.

• Comfortable reading API docs, making API calls (Postman or curl), reading JSON and following a sequence diagram.

• Basic SQL to pull and analyse transaction and adoption data.

• Clear writing: requirements, plans, docs and updates people can act on.

• Follow-through: you close loops across teams without reminders.

• Educational Qualifications: Graduation or post-graduation from a tier-1 engineering college.

Nice to have

• Hands-on engineering experience, such as building a backend service or a merchant integration in the past.

• Familiarity with payment concepts: auth and capture, settlement, reconciliation, idempotency, webhooks, 3DS, tokenisation.

• Experience writing developer documentation.

What success looks like

• By 3 months: You know your team’s flows and own the requirements, plan and docs for your area.

• By 6 months: You have landed multiple initiatives on time, and merchants are adopting what shipped. Your key results are tracked weekly.

• By 12 months: Segment PMs, TAMs and engineers come to you first for your area, and you have measurably improved merchant integration time or adoption.