razorpay Technical Program Manager Interview: Questions, Experience & Prep (2026)

Razorpay is one of India's leading fintech companies, powering payments for millions of merchants across India. A Technical Program Manager (TPM) at Razorpay sits at the intersection of engineering, product, and business, coordinating complex cross-functional programs, managing dependencies across teams, and making sure large initiatives ship on time.

As of July 2026, Razorpay has 42 open roles listed on knok's job radar, and the TPM position is among the most competitive. Candidates report the process typically involves multiple rounds covering program management depth, technical understanding, and behavioral scenarios tied to Razorpay's scale.

Expect questions about Razorpay's core products (payment gateway, payment links, Razorpay X, POS) and how you would drive technical programs in a high-growth fintech environment. The company values ownership, technical credibility, and the ability to operate across organizational boundaries without formal authority.

These are company-specific questions that candidates report coming up in Razorpay TPM interviews:

1. Walk us through a complex program you managed end-to-end. How did you handle dependencies and blockers?
2. How would you drive alignment between an engineering team and a product team when they disagree on priorities?
3. Razorpay processes payments for millions of merchants. How would you manage a high-severity incident affecting the payment gateway?
4. Describe a time you had to push back on scope or timeline. How did you communicate this to senior stakeholders?
5. How do you track and communicate program risks before they become blockers?
6. Tell us about a time you improved an engineering team's delivery process. What did you change and why?
7. How would you onboard yourself to a new program that is already behind schedule?
8. Razorpay operates in a regulated environment. How have you handled compliance or regulatory constraints in a technical program?
9. Describe a time you had to influence a team that did not report to you.
10. How do you decide what to escalate versus what to resolve yourself?
11. Tell us about a time a technical decision you influenced turned out to be wrong. What happened next?
12. How do you ensure cross-team technical dependencies do not slip?

Q: Walk us through a complex program you managed end-to-end.

*Situation:* Our company was migrating a core payment processing service to a new infrastructure provider. Several engineering teams, a security team, and an external vendor were all involved.

*Task:* My responsibility was to ensure the migration completed before a firm regulatory deadline without disrupting live merchant transactions.

*Action:* I mapped all dependencies into a shared tracker visible to every team, ran standups focused only on active blockers rather than status theatre, built a risk register with clear owners and mitigation steps, and created a war room protocol for any issue touching live traffic.

*Result:* The migration completed before the deadline with zero merchant-facing downtime. The risk register format was later adopted by two other program teams as a standard template.

---

Q: Describe a time you had to push back on scope or timeline.

*Situation:* A senior stakeholder requested adding a new reporting feature to a compliance program that was already in final testing.

*Task:* I needed to protect the ship date while keeping the stakeholder confident in the overall program.

*Action:* I documented the impact of the addition: extra engineering effort, regression risk, and a likely deadline miss. I presented two options, shipping on time without the feature or delaying the entire program, and recommended the first option with a committed date for the reporting feature in the next cycle.

*Result:* The stakeholder agreed to the phased approach. The compliance program shipped on schedule, and the reporting feature launched as promised in the following cycle.

---

Q: Describe a time you had to influence a team that did not report to you.

*Situation:* A platform team's API changes were blocking several downstream teams, but the platform team had deprioritized the fix in favour of their own roadmap items.

*Task:* I had to get the fix prioritized without any direct authority over the platform team.

*Action:* I framed the downstream impact in terms of delayed merchant-facing features and brought this to a shared leadership forum. I also proposed a short-term workaround that downstream teams could use while the platform team completed the proper fix, keeping the ask narrow and low-risk so the platform manager could easily say yes.

*Result:* The workaround unblocked the downstream teams within a few days. The platform team scheduled the proper fix in their next planning cycle, and the working relationship stayed strong throughout.

A few structured frameworks that tend to work well for Razorpay TPM interviews:

STAR (Situation, Task, Action, Result): Use this for every behavioral question. Keep the Situation brief, spend most of your time on Action, and always close with a concrete Result.

Impact vs. Effort: For prioritization questions, show that you weigh the business impact of a task against the cost to deliver it, not just the urgency or loudness of the request.

Pre-mortem: For risk questions, describe how you imagine the program has already failed and work backwards to find what caused it. This signals proactive thinking rather than reactive firefighting.

What, So What, Now What: For incident or retrospective questions, structure your answer as what happened, why it matters to the business, and what you changed as a result.

Stakeholder map: For influence or alignment questions, show that you first identify all stakeholders, understand their incentives, and tailor your communication to each rather than sending one generic message to everyone.

Razorpay TPM interviewers typically look for a specific combination of traits.

Ownership: Do you treat program outcomes as your personal responsibility, or do you position yourself as a coordinator who just tracks others? The strongest candidates say 'I ensured' and 'I escalated' rather than 'the team eventually solved it'.

Technical credibility: Can you hold a real conversation with engineers about architecture trade-offs, API design, and technical debt? You are not expected to write code, but you must be able to ask sharp questions and understand the answers you get.

Stakeholder management: Can you align, influence, and sometimes push back without burning relationships? Razorpay moves fast and has strong opinions across teams, and interviewers want to see that you navigate this well.

Data orientation: Do you make decisions based on metrics and evidence, or on gut feel? Interviewers notice whether you instinctively reach for numbers to support your decisions.

Fintech awareness: Do you understand payment rails, API uptime expectations, PCI-DSS basics, and what a regulatory deadline means for engineering timelines? Candidates who treat Razorpay as just another tech company tend to underperform here.

A structured approach that candidates typically find effective for Razorpay TPM prep:

1. Study the product. Spend time using Razorpay's payment gateway, payment links, and Razorpay X. Understand the merchant onboarding flow and how a payment moves from a customer's click to a merchant's bank account.

1. Read the engineering blog. Razorpay publishes technical articles about their infrastructure, scaling challenges, and past programs. These give you genuine talking points that show you did more than skim the careers page.

1. Build your STAR library. Prepare five or six strong stories covering: a complex cross-functional program, a high-severity incident, a scope or timeline pushback, influencing without authority, a process improvement, and a time something went wrong.

1. Practice program metrics. Know how you measure program health beyond 'on time and on budget.' Be ready to explain what a good weekly status update looks like and how you handle a program that has turned red.

1. Review fintech basics. Be comfortable with settlement cycles, reconciliation, chargebacks, PCI-DSS compliance requirements, and why regulatory deadlines are often non-negotiable for engineering teams.

1. Prepare sharp questions for the interviewer. Ask about a recent program challenge at Razorpay, how the TPM team is structured, or what success looks like in the first few months. This signals genuine preparation and curiosity.

Talking only about process, not outcomes. Saying 'I set up a tracker and ran standups' tells the interviewer nothing about your impact. Always end with what changed because of your work, not just what you did.

Avoiding technical depth. Vague answers like 'I coordinated with the tech team' will not land at Razorpay. Be ready to describe what the technical challenge actually was and why it was hard to solve.

Overloading on buzzwords. Phrases like 'drove alignment' or 'leveraged synergies' are meaningless without a concrete story underneath. If your answer has no specific details, it will not be memorable.

Not knowing Razorpay's products. Candidates who have not used or researched the product are easy to spot. A basic understanding of how the Razorpay payment gateway works helps you anchor answers in the company's real context.

Weak or missing results. Every STAR answer must close with a result you can describe clearly. If you cannot name the outcome, the interviewer has no way to evaluate your actual impact.