Razorpay product manager tools tech stack and workflows used 2026

Keyword: Razorpay tools pm

What tools does a Razorpay product manager actually use in 2026?

A Razorpay PM’s daily stack is JIRA for sprint tracking, Confluence for documentation, Amplitude for product analytics, Looker for executive dashboards, Figma for UI design, Notion for knowledge sharing, and an internal “Razorpay Insights” service for transaction‑level data.

In a Q2 2026 debrief for a senior PM role on the Razorpay Checkout team, the hiring manager, Priya Sharma, asked the candidate to enumerate the tools he relied on for A/B testing.

The candidate listed JIRA, Google Sheets, and “some heat‑map tool.” The interview panel, including a senior TPM from the Payments Platform (team size ≈ 120), voted 4‑1 that the candidate lacked depth in the Razorpay stack. The panel cited a recent internal case where a PM used Amplitude’s “Funnel Explorer” to identify a 2.3 % drop‑off after the merchant onboarding step, then built a Looker view to surface “failed‑auth” events to the compliance team.

Not “knowing every product,” but “knowing the Razorpay‑specific tooling” determines whether a candidate can ship features in a two‑week sprint.

Insight 1 – Tool‑Signal Bias: Razorpay evaluates tool fluency more heavily than generic PM knowledge because the platform’s data pipelines are proprietary.

How does the Razorpay PM workflow integrate data and design?

Razorpay PMs run a “Data‑First Design Loop” that starts with raw transaction logs, moves to Amplitude segmentation, then to Figma prototypes validated against Looker dashboards.

During a June 2026 launch sprint for the “Instant Refund” feature, the PM, Arjun Mehta, opened the daily stand‑up with a Looker chart showing a 1.8 % increase in refund‑related support tickets. He then displayed a Figma prototype that added a “One‑Click Refund” button on the merchant dashboard.

The engineering lead, Maya Rao, asked for the metric that would prove the prototype’s impact. Arjun referenced an Amplitude cohort that projected a 0.7 % reduction in support tickets per 1,000 refunds. The team accepted the hypothesis and locked the scope for the next sprint.

Not “designing in a vacuum,” but “designing on top of live metrics” is the Razorpay standard.

Insight 2 – Metric‑Anchored Prototyping: The first counter‑intuitive truth is that a PM who can tie a Figma frame to a real‑time Amplitude segment gains trust faster than one who can produce polished mockups alone.

Which internal frameworks shape decision‑making for Razorpay PMs?

Razorpay uses the “R‑Score” framework (Revenue × Risk ÷ Complexity) and the “Three‑Lens Review” (Customer, Compliance, Engineering) to vet ideas.

In a Q3 2026 HC for a PM on the Razorpay Capital product, the hiring manager, Suman Patel, presented the candidate with a case: “You have a feature that could increase merchant onboarding revenue by $2.1 M annually but requires new KYC integrations.” The candidate replied, “I’d run a quick A/B test.” The panel demanded a formal R‑Score.

The candidate faltered, producing a superficial risk estimate. The HC vote was 3‑2 against the candidate because he did not apply the Three‑Lens Review, which had saved the team from a previous compliance breach in 2025.

Not “a gut feeling,” but “a disciplined framework” decides the fate of product proposals at Razorpay.

Insight 3 – Framework Over Intuition: The second counter‑intuitive truth is that Razorpay PMs who skip the R‑Score are treated as “visionary” but not “executable.”

What does a Razorpay PM’s day look like during a launch sprint?

A typical day begins with a 15‑minute “Metrics Pulse” in Looker, continues with a 30‑minute design sync in Figma, and ends with a 45‑minute sprint retro that references Amplitude’s “Feature Impact” report.

In the October 2026 sprint for “Dynamic Pricing,” the PM, Leena Kumar, opened the day by sharing a Looker dashboard that showed a 4.5 % revenue uplift from a pilot in the “Enterprise” segment. She then walked the team through a Figma prototype that introduced price‑tier sliders. After the sprint, the retro highlighted that the Amplitude “Conversion Funnel” had a 0.9 % drop after the price‑slider interaction. The team agreed to iterate on the UI spacing, a decision driven directly by the data.

Not “working in isolation,” but “closing the loop with data every day” is mandatory for Razorpay’s rapid iteration culture.

Insight 4 – Continuous Data Loop: The third counter‑intuitive truth is that a PM who spends the most time on UI polish without referencing live metrics will be out‑performed by a teammate who iterates on a single metric‑driven change.

How does the hiring committee evaluate a Razorpay PM candidate’s tool fluency?

Razorpay’s HC uses a “Tool‑Proficiency Matrix” that scores candidates on JIRA, Amplitude, Looker, and internal APIs on a 0‑5 scale; a total score below 12 fails the candidate.

During a July 2026 HC for a junior PM on the “Razorpay Subscriptions” team, the candidate earned a 3 in JIRA, 2 in Amplitude, 1 in Looker, and 0 in Razorpay Insights. The panel’s final vote was 5‑0 to reject. The hiring manager, Rohan Verma, noted that the candidate’s answer to “How would you surface churn risk for subscription merchants?” was “I’d write a SQL query.” The matrix penalized the lack of Looker experience.

Not “a generic product sense test,” but “a calibrated tool‑score” is the gatekeeper for Razorpay PM hires.

Insight 5 – Quantified Tool Evaluation: The fourth counter‑intuitive truth is that a candidate with strong product intuition but a low tool‑score is rejected more often than a candidate with modest intuition but high tool proficiency.

Preparation Checklist

Review the Razorpay Insights API documentation (the endpoint for “/v1/transactions” returns JSON with latency ≤ 120 ms).
Practice building a Looker dashboard that tracks “Refund Success Rate” for the last 30 days; the target KPI is 99.2 %.
Run a mock Amplitude cohort analysis on “Merchant Onboarding Completion” to identify a 1.5 % drop‑off point.
Draft a concise R‑Score for a hypothetical “Instant Payout” feature (Revenue ≈ $3.4 M, Risk ≈ 2, Complexity ≈ 4).
Work through a structured preparation system (the PM Interview Playbook covers Razorpay’s Three‑Lens Review with real debrief examples).
Re‑hearse a 2‑minute pitch that ties a Figma prototype to a specific Looker metric.
Prepare a salary expectation: $165,000 base, $20,000 sign‑on, 0.03 % equity, per the 2026 Razorpay compensation guide.

Mistakes to Avoid

BAD: Claiming “I’m comfortable with any PM tool” without naming Amplitude or Razorpay Insights. GOOD: Citing a recent Amplitude “Funnel Explorer” analysis that uncovered a 2.3 % checkout drop‑off and describing the resulting design change.

BAD: Responding to “How would you measure success?” with “KPIs are important.” GOOD: Naming the exact Looker chart (“Monthly Active Merchant – MAU”) and the target growth of 8 % YoY.

BAD: Saying “I’d rely on stakeholder meetings” for decision‑making. GOOD: Explaining the R‑Score calculation and how the Three‑Lens Review filtered a high‑risk feature in Q1 2025.

📖 Related: Razorpay PM intern interview questions and return offer 2026

FAQ

What level of tool proficiency is required for a Razorpay PM role?

Razorpay expects a minimum score of 12 out of 20 on its Tool‑Proficiency Matrix, with at least a 3 in Amplitude and a 3 in Looker. Low scores in any core tool lead to an automatic reject, regardless of product vision.

Do Razorpay PMs need to write code?

No. The judgment is that a PM should be able to read API docs and construct queries, not ship production code. Candidates who claim deep engineering experience are often judged as over‑qualified and may be redirected to TPM roles.

How does Razorpay assess a candidate’s ability to work with the “R‑Score” framework?

During the interview loop, candidates receive a case study and must produce an R‑Score on the whiteboard. The panel scores the calculation, the justification of each factor, and the communication clarity. A score below 7 out of 10 on this exercise typically results in a 0‑5 HC vote.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.

TL;DR

Review the Razorpay Insights API documentation (the endpoint for “/v1/transactions” returns JSON with latency ≤ 120 ms).