Paytm Business Analyst

This guide features 10 challenging Business Analyst interview questions for Paytm (Senior BA to Lead BA levels), covering fintech metrics, payment transaction analysis, merchant growth strategies, and root cause analysis aligned with Paytm’s mission of driving financial inclusion.

1. Analyze Transaction Volume Drop — Root Cause Analysis & Strategic Response

Difficulty Level: Very High

Role: Senior Business Analyst

Source: LinkedIn Post by Baghel Neeraj (Paytm Data Analyst Interview Experience)

Topic: Root Cause Analysis & Operations Analytics

Interview Round: Case Study (60 minutes)

Business Function: Operations Analytics / Payments

Question:
“You notice that Paytm’s daily transaction volume has dropped by 20% this week compared to the previous week. Your manager expects a detailed analysis and recommendation within 24 hours. Walk through your analytical approach, what metrics you’d investigate, potential root causes, and how you’d recommend responding.”

Answer Framework

STAR Method Structure:
- Situation: Daily transaction volume dropped 20% week-over-week, signaling a potential P0 issue affecting revenue and trust.
- Task: Diagnose the root cause (Technical vs. Seasonal vs. Product) and recommend a recovery plan within 24 hours.
- Action: Conducted a multi-dimensional analysis (User, Geography, Payment Method). Identified that the drop was concentrated in Tier-2 cities (-30%) and Card/Wallet transactions (-25%/-35%), pointing to a mixed cause (Seasonal end + Payment Success Rate drop).
- Result: Recommended rapid retention campaigns for seasonal drop and technical failovers for payment failures, projecting a 12-15% volume recovery.

Key Competencies Evaluated:
- Structured Problem-Solving: Breaking down aggregate metrics into testable segments (User, Geo, Method).
- Fintech Acumen: Understanding Payment Success Rates (PSR), PG latency, and Merchant Churn.
- Action Orientation: Moving from “Analysis” to “Response Plan” (Short-term vs Medium-term).

Answer (Part 1 of 3): Multi-Dimensional Diagnosis

Problem Clarification: First, checking if this is a data pipeline issue (false alarm) or real drop. Validated it’s real.
Segmentation Analysis:
* By User: New users (-5%) vs Active users (-25%). The drop in core active users is concerning.
* By Geography: Tier-1 (-15%) vs Tier-2 (-30%). The skew towards Tier-2 suggests a targeted issue.
* By Payment Method: UPI (-12%) is stable. Wallet (-35%) and Cards (-25%) are the bleeding points.
* Findings: The drop isn’t system-wide; it’s specific to Tier-2 users relying on Wallets/Cards.

Answer (Part 2 of 3): Root Cause Identification

We evaluating hypotheses based on likelihood:
1. Seasonal/External (High Probability): A major sale or competitor promo ended recently. Matches the -20% magnitude.
2. Payment Failure (High Probability): Success Rate analysis shows Wallet reliability dropped from 94.5% to 91.2%. This explains ~5% of the drop.
3. Trust Issues (Medium): Tier-2 users are sensitive to trust. If a “Fraud Rumor” spread, Wallet usage drops.
Conclusion: It is a compound issue: 60% Seasonal (Post-festival dip) and 40% Technical (Wallet/Card gateway failures).

Answer (Part 3 of 3): Strategic Response & Recovery

Immediate (24hrs):
* Technical: Fix the Wallet gateway latency/timeouts. Implement auto-retry for failed Card transactions using secondary routes.
* Communication: Acknowledge the issue transparently if it was a technical outage.
Short-Term (1-2 Weeks):
* Retention Campaign: Launch a specific “Come Back” offer for the Tier-2 Active Users who stopped transacting (e.g., “Get ₹10 cashback on next Wallet txn”).
* Monitoring: Set up real-time alerts for “Wallet Success Rate < 92%” to catch this faster next time.

2. Unit Economics of a Cashback Campaign — Profitability Analysis

Difficulty Level: Very High

Role: Senior Business Analyst

Source: LinkedIn Post by Ankit Batham (Paytm Case Study)

Topic: Unit Economics & Profitability

Interview Round: Case Study (45 minutes)

Business Function: Growth & Retention Analytics

Question:
“Paytm is planning to offer ₹50 cashback for every 5 transactions completed within a week.

Target: 10M eligible users.

Assumptions: 40% take-up rate, 25% of users would have completed those 5 transactions anyway (Incrementality = 75%).

Economics: Average transaction value: ₹500. Commission per transaction: 1.2%.

Calculate the campaign’s profitability and provide a recommendation.”

Answer Framework

STAR Method Structure:
- Situation: Proposed growth campaign (₹50 cashback) targets 10M users to drive transaction frequency.
- Task: Calculate Net P&L (Profit & Loss) and decide if the campaign is financially viable.
- Action: Calculated Total Cost (Cashback + Ops) vs Incremental Revenue (Commission). Identified a significant loss (-₹41.1 Cr).
- Result: Recommended against a full rollout. Proposed a “Segmented Pilot” targeting only High-LTV users to improve ROI using a “Hybrid Level” approach.

Key Competencies Evaluated:
- Quantitative Rigor: Precision in calculating Incremental Cost vs Incremental Revenue.
- Incrementality: Understanding that paying for behaviour that would happen anyway is waste.
- Strategic Thinking: Balancing immediate P&L loss against long-term LTV and Network Effects.

Answer (Part 1 of 3): Financial Analysis (The P&L Calculation)

The Cost (Cashback):
* Participants: 10M * 40% = 4M Users.
* Qualifiers (Winners): 4M * 75% (success rate assumptions) = 3M Users.
* Total Cashback Cost: 3M * ₹50 = ₹150 Cr. (Note: We pay for all winners, even non-incremental ones).

The Revenue (Incremental Commission):
* Incremental Users: 3M Winners * 75% Incrementality = 2.25M Users.
* Incremental Txns: 2.25M * 5 txns = 11.25M txns.
* Revenue: 11.25M * ₹500 * 1.2% (Comm) = ₹67.5 Cr.

Net P&L: Revenue (₹67.5 Cr) - Cost (₹150 Cr) = -₹82.5 Cr Loss.
Correction from scenario prompt: Even with optimistic adjustments (indirect revenue + lower admin costs), the base math shows a -35% to -50% Net Margin. The campaign burns cash.

Answer (Part 2 of 3): Strategic Value & Indirect Benefits

While the campaign is P&L negative, we evaluate Indirect Value:
1. LTV Uplift: If these 2.25M users develop a habit, their 12-month value increases by ₹500 each (+₹112 Cr long term).
2. Float Income: Users load wallets to transact, giving Paytm interest-free working capital.
3. Defensibility: Prevents churn to PhonePe/Google Pay.
Verdict: The “Strategic Value” might justify the burn, but only if Retention is proven.

Answer (Part 3 of 3): Recommendation & Optimization

Draft Verdict: Do NOT launch to 10M users immediately. The burn is too high.
Proposed Strategy (The Fix):
1. Run a Pilot: Target 1M users first (Week 1). Measure actual Incrementality (Is it really 75%? If it’s 50%, we bleed more).
2. Segmented Offer:
* High-Value Users: Offer ₹50 (They generate higher commission).
* Low-Value Users: Offer ₹30 for 3 txns (Lower risk).
3. Strict Cap: Cap total budget at ₹10 Cr for the first month to contain risk.

3. Merchant Onboarding Prioritization — Data-Driven Segmentation

Difficulty Level: High

Role: Senior Business Analyst

Source: LinkedIn Post by Baghel Neeraj (Paytm Interview)

Topic: Merchant Growth & Prioritization

Interview Round: Case Study (45 minutes)

Business Function: Merchant Business Insights / Growth

Question:
“Paytm’s merchant onboarding team can handle 100K new merchants per month. You have 500K merchants waiting to be onboarded. How would you prioritize which merchants to onboard first? Design a scoring model with specific metrics and weights.”

Answer Framework

STAR Method Structure:
- Situation: Backlog of 500K merchants with limited capacity (100K/month). First-come-first-serve strategy leaves money on the table.
- Task: Build a prioritization logic (Scoring Model) to maximize 12-month GMV and Merchant Retention.
- Action: Designed a weighted scoring model (Revenue 30%, Stickiness 25%, Network 25%, Risk 20%) to segment merchants into 4 Tiers.
- Result: Prioritized onboarding Tier 1 & 2 merchants, increasing average GMV per merchant from ₹3L to ₹8L and generating +₹60 Cr monthly incremental revenue.

Key Competencies Evaluated:
- Segmentation Logic: Moving beyond simple “Big vs Small” to complex “Network Effects” and “Risk”.
- Weighting Methodology: Justifying why Revenue > Risk in a growth phase.
- Operational Execution: Translating a “Score” into a daily “Call List” for the sales team.

Answer (Part 1 of 3): The Scoring Model (Value Drivers)

We don’t treat all 500K merchants equally. We score them (0-100) based on 4 factors:
1. Revenue Potential (30%): Estimated Monthly GMV. Proxy: Shop type (Restaurant > Kiosk), Location (Market vs Residential).
2. Engagement/Stickiness (25%): How likely are they to stay? Proxy: Business age (>2 years), Digital maturity (Has GST, email).
3. Network Value (25%): Do they bring customers? Proxy: High footfall area, Social media presence, Rating (4.5+ stars).
4. Risk Profile (20%): Fraud/Churn risk. Proxy: Document completeness (Full KYC = Low Risk), Category (Electronics = High Risk due to chargebacks).

Answer (Part 2 of 3): Segmentation Strategy (The 4 Tiers)

Based on the Score, we bucket merchants:
* Tier 1 (Score 80-100): “Whales” (e.g., Popular Restaurants). Action: VIP Onboarding (Immediate). Allocation: 30K slots.
* Tier 2 (Score 60-79): “High Potential” (e.g., Busy Retail Shops). Action: Standard Onboarding. Allocation: 50K slots.
* Tier 3 (Score 40-59): “Fillers” (e.g., Small Vendors). Action: Waitlist / Self-Serve Onboarding only. Allocation: 20K slots.
* Tier 4 (Score 0-39): “Risky/Low Value”. Action: Do not onboard.

Answer (Part 3 of 3): Business Impact Calculation

Why this matters?
* Without Prioritization: Random 100K merchants -> Avg GMV ₹3L -> Total Monthly Volume ₹300 Cr.
* With Prioritization: Top 100K merchants -> Avg GMV ₹8L -> Total Monthly Volume ₹800 Cr.
* Impact: +₹500 Cr Volume and +2x Retention (Tier 1 merchants stick longer). This turns an operational constraint into a revenue optimization lever.

4. Behavioral — Data Conflict with Stakeholder & Decision-Making Under Ambiguity

Difficulty Level: Medium-High

Role: Senior Business Analyst

Source: LinkedIn Post by Baghel Neeraj (Paytm Interview)

Topic: Behavioral & Stakeholder Management

Interview Round: Behavioral (30 minutes)

Business Function: Cross-functional Analytics

Question:
“Tell us about a time when your data analysis contradicted what a senior stakeholder believed. How did you handle it? What was the outcome?”

Answer Framework

STAR Method Structure:
- Situation: Product Manager believed adding a “Save Card” feature would boost retention (assumption based on Competitor/Google Pay).
- Task: Validate this hypothesis. My data showed 60% of Paytm users actively avoided saving cards due to trust issues.
- Action: Instead of public confrontation, I booked a 1-on-1. I verified my data (Survey + Beta Logs). I proposed a Compromise: “Let’s A/B test it only on High-Value Users who trust us more.”
- Result: A/B test showed +12% lift for High-Value users but 0% for others. We rolled it out selectively, saving engineering effort and avoiding user friction.

Key Competencies Evaluated:
- Data Integrity: Standing by the data even when it’s unpopular.
- Emotional Intelligence: Choosing “Private Meeting” over “Public Debate”.
- Business Thinking: Finding the “Third Way” (Segmentation) instead of a binary Yes/No.

Answer (Part 1 of 3): The Conflict (Situation & Task)

“I was analyzing wallet engagement. The PM wanted to launch ‘One-Click Card Save’ to reduce friction, assuming it would work because Google Pay does it.
However, my deep-dive into user surveys showed a clear signal: Trust Deficit. 60% of our specific user base (Tier-2/3) explicitly said they prefer entering OTPs every time for security. The PM’s assumption was based on a different demographic (Tier-1). I had to communicate that ‘Our users are different’ without sounding like a blocker.”

Answer (Part 2 of 3): The Approach (Action)

“I didn’t say ‘You are wrong.’ I validated my data first (triangulated Survey vs Beta Logs). Then I scheduled a private discussion.
I presented the data as a Risk vs Reward trade-off: ‘If we force this, we might scare off the 60% tax-sensitive users. But the 8% power users might love it.’
I proposed a hypothesis-led experiment: Don’t launch to everyone. Let’s run a controlled A/B test only on users with >₹10k annual spend (High Trust Cohort).”

Answer (Part 3 of 3): The Resolution (Result)

“The PM agreed to the test.
The Data: High-Value users showed a 12% increase in transaction frequency. Low-Value users showed 0% change and higher app uninstall rates in the test group.
The Outcome: We launched the feature only for the High-Value segment. The PM became a data advocate because the ‘Segmented Rollout’ saved him from a failed mass-launch. It taught me that data isn’t just for blocking—it’s for refining.”

5. Churn Analysis — Predicting Soundbox Merchant Drop-offs

Difficulty Level: High

Role: Senior Business Analyst

Source: LinkedIn (Paytm Growth Team Interviews)

Topic: Predictive Analytics & Churn

Interview Round: Technical Case (60 minutes)

Business Function: IoT / Soundbox Operations

Question:
“Paytm Soundbox churn (merchants stopping usage) has increased by 15% in the last 2 months.

1. How do you define ‘Churn’ for a Soundbox merchant?

2. What features would you use to build a predictive model?

3. Propose an intervention strategy.”

Answer Framework

STAR Method Structure:
- Situation: Rising churn in the critical “Soundbox” subscription business (Hardware as a Service).
- Task: Define the “Churn Event” accurately and identify early warning signals to prevent device return.
- Action: Defined churn as “Zero scans for 7 days + Device offline”. Built a feature set including “Battery Status” (Technical) and “Transaction Volume Trend” (Commercial).
- Result: Identified that 40% of churn was “Technical” (Battery/Network) not “Intentional”. Launched “Proactive Service Visits” reducing churn by 18%.

Key Competencies Evaluated:
- Metric Definitions: Distinguishing “Dormant” (Temporarily closed shop) from “Churned” (Switched to PhonePe).
- Feature Engineering: Technical telemetry (Battery, Signal) + Transactional signals.
- Operational Strategy: Field ops vs Tele-calling interventions.

Answer (Part 1 of 3): Defining Churn (The “Zero-Scan” Trap)

We can’t just use “Subscription Expired”.
Definition: A merchant is “High Risk Churn” if:
1. Zero Transactions for 7 consecutive days.
2. Device Heartbeat is missing (Offline) for >48 hours.
3. Exception: Filter out “Known Holidays” (e.g., Market closed on Tuesday) to avoid false alarms.

Answer (Part 2 of 3): Predictive Features (The “Why”)

To predict who will churn next month, I analyse:
* Technical Log: Low Battery persistence (Device dying often?), Weak Signal Strength (2G vs 4G). Hypothesis: Frustrated users churn.
* Commercial Trend: declining Daily Average Transactions (DAT) over 4 weeks. (Competitor encroachment?).
* Voice Alerts: High volume of “Payment Failed” voice alerts (Frustration).
* Subscription: Days remaining < 10 days.

Answer (Part 3 of 3): Intervention Strategy

Segment based on Root Cause:
1. Technical Risk (Dead Battery/Bad Signal): Trigger an automated ticket for a Field Service Engineer to visit and swap the device (Free). Outcome: Retain customer by fixing hardware.
2. Commercial Risk (Low Volume): Trigger a Discount Offer (50% off rental) via Call Center.
3. Competitor Risk: Merchants doing transactions but not on Soundbox? Send a “Mystery Shopper” or Sales Rep to check if they installed a PhonePe box.

6. Fraud Detection Metrics — Balancing Security & User Friction

Difficulty Level: High

Role: Senior Business Analyst

Source: Risk Analytics Team

Topic: Fraud Detection & Risk Management

Interview Round: Case Study (60 minutes)

Business Function: Risk & Compliance

Question:
“Paytm’s ‘Wallet’ fraud rate (chargebacks) has increased by 0.5%. The Risk Team wants to tighten rules.

1. What metrics would you monitor to measure ‘Fraud’?

2. How do you balance ‘Blocking Fraud’ vs ‘Blocking Real Users’ (False Positives)?

3. Design a real-time logical rule to stop ‘Account Takeover’ (ATO) attacks.”

Answer Framework

STAR Method Structure:
- Situation: Rising fraudulent transactions (ATO and Phishing) leading to regulatory scrutiny and loss.
- Task: Implement stricter controls without stopping genuine users (who might just be traveling).
- Action: Analyzed “False Positive Rate” vs “Fraud Catch Rate”. Proposed a Step-Up Authentication model (2FA) instead of hard blocks for medium-risk events.
- Result: Reduced Fraud by 20% while keeping Transaction Success Rate (TSR) stable.

Key Competencies Evaluated:
- Risk Metrics: Confusion Matrix (Precision vs Recall).
- Trade-off Analysis: Cost of Fraud vs Cost of Lost Business (Good User Rejection).
- Rule Design: Velocity checks vs Device Fingerprinting.

Answer (Part 1 of 3): Fraud Metrics (Detecting the Bad)

We track:
1. Strict Fraud Rate: (Chargeback Count / Total Txn Count). Target: < 0.1%.
2. False Positive Rate (FPR): (Genuine Users Blocked / Total Blocked). This is the “Insult Rate”. We must minimize this.
3. Authentication Drop-off: (Users seeing OTP screen / Users entering OTP). If this spikes, our security is adding too much friction.

Answer (Part 2 of 3): Designing the Rule (The ATO Trap)

Scenario: Account Takeover (Hacker logs in).
Rule Logic:
* IF Device_ID is NEW

* AND Location is >500km from last login (Velocity check: Impossible Travel)

* AND Transaction_Type is “Wallet to Bank” (Cash out)

* THEN: Trigger “High Risk”.

Answer (Part 3 of 3): The Intelligent Response (2FA vs Block)

Instead of a “Hard Block” (Transaction Declined), we use Step-Up Auth:
* Low Risk: Allow.
* Medium Risk (New Device): Ask for OTP + Grid Card/PIN.
* High Risk (Impossible Travel): Block + Freeze Account.
Business Impact: This dynamic friction ensures grandmother sending money isn’t blocked, but a bot draining a wallet is.

7. Feature Launch KPI Framework — Paytm Postpaid (BNPL)

Difficulty Level: Medium

Role: Senior Business Analyst

Source: Paytm Postpaid Case Study

Topic: Product Analytics & Metrics

Interview Round: Product Case (45 minutes)

Business Function: Lending / Postpaid

Question:
“Paytm is launching ‘Postpaid’ (Buy Now Pay Later).

1. What is your North Star Metric?

2. What Guardrail Metrics would you track to ensure we don’t go bankrupt?

3. How do you measure if the product is ‘Successful’ after 3 months?”

Answer Framework

STAR Method Structure:
- Situation: Launching a credit product (BNPL) involves high risk. High adoption is easy (free money), but sustainable growth is hard.
- Task: Define a balanced Scorecard that incentivizes growth without wrecking asset quality.
- Action: Selected “Total Active Loan Volume” as North Star but paired it with stricter “Delinquency Rate (NPA)” guardrails.
- Result: Balanced framework ensured the product grew 20% MoM while keeping Bad Loans < 1.5%.

Key Competencies Evaluated:
- Product Sense: Differentiating “Vanity Metrics” (Signups) from “Value Metrics” (Disbursals).
- Risk Awareness: Understanding NPA (Non-Performing Assets) in lending.
- Cohort Analysis: Tracking repayment behavior over time.

Answer (Part 1 of 3): The Metrics (Success vs Risk)

North Star (Growth): Weekly Active Borrowers (Users taking >1 loan/week).
Why: Signups don’t matter. Usage matters.
Guardrail (Risk): NPA% (Non-Performing Assets) at 90 Days.
Why: If we lend ₹100 and get back ₹0, we fail. Target NPA < 2%.

Answer (Part 2 of 3): Secondary Health Metrics

1. Approval Rate: (Loans Given / Loans Applied). Low approval = Bad UX. High approval = High Risk. Optimize this ‘Goldilocks’ zone.

1. Repayment Rate: % of users paying before due date.

1. Cross-Sell: Do Postpaid users spend more on Paytm Mall? (The ecosystem benefit).

Answer (Part 3 of 3): Measuring “Success” (3-Month Review)

After 90 days, I look at Cohort Repayment Curves.
* Good Signal: Cohort 1 has 98% repayment. Cohort 2 has 98% repayment.
* Bad Signal: Cohort 1 had 98%, but Cohort 3 (expanded users) has 90%. This means we are acquiring “Bad Users”.
Verdict: If NPA > 3%, pause growth. Fix credit model. If NPA < 1%, expand aggressively.

8. Competitive Pricing Analysis — Defending Market Share vs PhonePe

Difficulty Level: High

Role: Senior Business Analyst

Source: Market Intelligence Case

Topic: Pricing Strategy & Competition

Interview Round: Strategy Case (60 minutes)

Business Function: Marketplace / Strategy

Question:
“PhonePe has launched a massive ‘₹100 Cashback’ campaign. Our daily market share dropped by 5%.

1. Should we match the offer (costing ₹50 Cr)?

2. If not, design a smarter, cheaper response strategy.

3. How do you identify which users are ‘Deal Hunters’ vs ‘Loyalists’?”

Answer Framework

STAR Method Structure:
- Situation: Competitor (PhonePe) is buying market share with deep discounts. Matching them dollar-for-dollar is unsustainable.
- Task: Defend market share with a limited budget (20% of PhonePe’s spend).
- Action: Segmented users by “Price Elasticity”. Decided to Ignore Deal Hunters and Target At-Risk Loyalists.
- Result: Retained 80% of volume using only 20% of the budget. Accepted the loss of low-value cherry-pickers.

Key Competencies Evaluated:
- Game Theory: Predicting competitor moves (War of Attrition).
- Price Elasticity: Quantifying how users react to price changes.
- Segmentation: “Win-back” signals.

Answer (Part 1 of 3): Elasticity Analysis (Who are we losing?)

We don’t need to save everyone.
* Segment A (Deal Hunters): Switch apps for ₹5. We let them go. Their LT (Lifetime Value) is negative.
* Segment B (Loyalists): Use Paytm for convenience. They haven’t churned yet but might if the gap (₹0 vs ₹100) is too big.
* Segment C (At-Risk): Usage dropped 50% this week. These are the battleground.

Answer (Part 2 of 3): The “Surgeon’s Scalpel” Strategy

Instead of a blanket “₹100 for All”:
1. Win-Back Offer: Target Segment C with “₹50 Cashback” (Half the competitor offer, but enough to tip them back).
2. Gamification: Target Segment A with “Scratch Cards” (Perceived value is high, actual cost is low, e.g., ₹2 avg).
3. Do Nothing: For Segment B, rely on UX/Habit.

Answer (Part 3 of 3): Execution & Measurement

We launch via Push Notifications only to targeted segments (Invisible to general public).
Metric: Win-back Rate.
If Segment C win-back is > 40%, the strategy holds.
The Trap: If we match ₹100 publicly, PhonePe might raise to ₹150, starting a “Race to the Bottom”. Asymmetric warfare is better.

9. Customer Segmentation — Optimizing Marketing Spend via RFM

Difficulty Level: Medium

Role: Business Analyst

Source: Growth Marketing Team

Topic: Customer Segmentation & Targeting

Interview Round: Analytics Case (45 minutes)

Business Function: Marketing Analytics

Question:
“Paytm sends a generic ‘Recharge Now’ push notification to all 100M users. The Click-Through Rate (CTR) is a low 0.5%.

1. How would you segment the user base to improve CTR?

2. Design specific campaigns for 3 key segments.

3. Estimate the impact on Marketing ROI.”

Answer Framework

STAR Method Structure:
- Situation: “One-size-fits-all” marketing was annoying users (Spam) and wasting budget (Low Conversion).
- Task: Create a Data-Driven Segmentation model to send “Right Message to Right User”.
- Action: Applied RFM Analysis (Recency, Frequency, Monetary) to cluster users into 3 personas. Stopped sending ads to “Lost” users.
- Result: CTR increased from 0.5% to 3.0% (6x). Analyzing “Who needs what” saved ₹2 Cr in SMS costs.

Key Competencies Evaluated:
- Analytical Techniques: RFM vs K-Means Clustering.
- Marketing empathy: Understanding user intent (Bill Payer vs Gamer).
- ROI Optimization: Cutting waste (Not messaging the dead).

Answer (Part 1 of 3): The RFM Model Approach

We score users on:
* Recency: Days since last txn (Last 7 days = 5 pts, >90 days = 1 pt).
* Frequency: Txns per month (<1 = 1 pt, >10 = 5 pts).
* Monetary: Average Ticket Size.
This gives a 3-digit score (e.g., 555 for Power User, 111 for Dormant).

Answer (Part 2 of 3): Defined Personas & Strategy

1. The “Utility Payer” (High R, Low F, High M): Pays Electricity/Rent once a month.
   • Campaign: “Rent Due in 2 days? Pay now.” (Timing is key).
   • Avoid: “Gaming cashback” (Irrelevant).

1. The “Daily Scanner” (High R, High F, Low M): Tea/Coffee scans.
   • Campaign: “Scan 5 times, win ₹10.” (Gamification works here).

1. The “Dormant” (Low R, Low F): Inactive 60 days.
   • Campaign: “We miss you. Here is ₹20 free.” (Aggressive win-back).

Answer (Part 3 of 3): ROI Impact

By suppressing messages to the “Lost/Dead” segment (Score 111) who make up 40% of the base:
* Cost Savings: 40M SMS * ₹0.10 = ₹40L saved per campaign.
* Conversion: Targeting “Daily Scanners” with relevant offers boosts CTR to 3-5%.
* Net Result: Higher GMV with Lower Cost.

10. Dashboard Design — The CEO’s Morning Review

Difficulty Level: Medium

Role: Business Analyst

Source: Executive Reporting

Topic: Data Visualization & KPIs

Interview Round: Managerial (30 minutes)

Business Function: Strategy / CEO Office

Question:
“You are designing the ‘Morning Pulse’ dashboard for Paytm’s CEO (Vijay Shekhar Sharma).

1. What top 5 metrics do you include?

2. How do you visualize them?

3. Why did you choose them over others (e.g., App Downloads)?”

Answer Framework

STAR Method Structure:
- Situation: The CEO has 5 minutes at 8 AM to know if the business is healthy. Information overload is the enemy.
- Task: Select the “Vital Signs” that cover Growth, Profitability, and Reliability.
- Action: Prioritized GMV (Scale), Contribution Margin (Profit), and Success Rate (Tech). Removed “Vanity Metrics” like Downloads.
- Result: Created a “Red/Green” status board that allows instant decision-making (e.g., “Tech is Red” -> Call CTO).

Key Competencies Evaluated:
- Executive Presence: knowing what leaders care about (Money & Risk).
- Metric Quality: Ignoring vanity metrics (Install count) vs actionable metrics (DAU).
- Visualization: Simple trend lines vs complex tables.

Answer (Part 1 of 3): The Top 5 Metrics

1. GMV (Gross Merchandise Value): Total value processed yesterday. (Indicator of Scale).

1. Net Revenue (Commission): How much money we actually made. (Indicator of P&L).

1. Active Users (DAU): Number of unique transacting users. (Indicator of Growth).

1. Transaction Success Rate (TSR): % of failed txns. (Indicator of Experience/Tech Health).

1. Contribution Margin: Revenue minus Direct Costs (Payment Gateway Fees). (Indicator of Viability).

Answer (Part 2 of 3): Visualization Strategy

• Headlines (Big Numbers): Yesterday’s value + % Change vs Previous Day.
  • Example: “GMV: ₹500 Cr (▼ 5%)”.

• Trend Lines (Small Charts): A 7-day sparkline next to each metric to show context (Is this a blip or a trend?).

• Traffic Lights: Green (On Target), Yellow (Warning), Red (Below Alert Threshold).

Answer (Part 3 of 3): Why these (Selection Logic)?

• Why not App Downloads? It’s a vanity metric. A user downloading but not transacting costs us money (marketing) but gives zero value.

• Why Contribution Margin? GMV can be bought with cashback. Contribution Margin tells the CEO if the growth is sustainable or if we are burning cash to get it.