CRED Interview Questions India 2026: SDE, PM & Designer (Highest Bar in Indian Fintech)

CRED's interview process is longer than most Indian companies and has no shortcuts:

For SDE roles:

1. Resume Screen: CRED's bar starts here. Sub-par college, no strong product company, no notable open-source or side projects = likely reject without interview. They hire from IIT/NIT + strong product companies (Flipkart, Razorpay, Swiggy, Amazon) and occasionally from top-tier IT services roles for very junior positions.
2. Online Coding Round: 2 problems, 90 minutes. Difficulty: LeetCode Medium-Hard to Hard. No partial marks. At least one problem typically requires graph or dynamic programming.
3. Technical Round 1: DSA + Problem Solving (60–75 min): 1–2 problems with interviewer interaction. Approach discussion is as important as the correct solution.
4. Technical Round 2: System Design (60–75 min): A real CRED product design problem. Not generic 'design Twitter'. Expect 'design CRED's rewards engine' or 'design a credit card statement delivery system at scale'.
5. Technical Round 3: Code Quality + Past Work (45–60 min): Deep dive into your past projects. What decisions did you make, what would you do differently, how does your code handle edge cases.
6. Hiring Manager Round: Culture + ambition + ownership stories.
7. Founder/Senior Leadership Round (for senior hires): Kunal Shah or a senior leader may join for principal/staff engineer levels.

For PM roles: Product sense + metrics + execution rounds, typically 4–5 rounds including a case study assignment.

Timeline: 4–8 weeks from first contact to offer. CRED moves deliberately, not slowly: they take time because they're genuinely evaluating fit, not because the process is disorganized.

CRED's coding bar is Hard by LeetCode standards. Candidates who have only solved Easy and Medium problems will not pass.

Topics that appear regularly (2024–2026 candidate reports):

Dynamic Programming (most common)

• Longest common subsequence
• 0/1 knapsack and unbounded knapsack
• Minimum edit distance
• Word break problem
• Coin change (minimum number of coins)

Graphs

• Shortest path problems (Dijkstra, Bellman-Ford)
• Topological sort
• Finding strongly connected components
• Detecting cycles in directed graphs

Trees and Advanced Data Structures

• Serialize and deserialize binary trees
• LCA (Lowest Common Ancestor)
• Segment trees and Fenwick trees (for senior roles)
• Trie operations

String Algorithms

• KMP pattern matching
• Rabin-Karp
• Anagram groups

CRED-specific framing: Some coding problems are framed around credit card or financial data:

• 'Given a list of credit card transactions with merchant IDs and timestamps, find all suspicious transaction clusters within 5 minutes of each other' (graph + time-window problem)
• 'Design a data structure to quickly query a user's spending in any date range' (segment tree / BIT)

Knowing the fintech context behind these problems helps with follow-up discussions even if the underlying DSA is standard.

Minimum preparation to attempt CRED coding rounds: 150+ LeetCode Medium problems + 30+ Hard problems, with at least 2 weeks spent on DP and graphs specifically.

CRED's system design questions are grounded in their actual product, not generic 'design YouTube' questions. You will be expected to know what CRED does, how it works at a product level, and what scale looks like for a premium 12M-user product.

Common CRED system design topics:

1. CRED Rewards Engine

• How do you design a system that computes rewards in real-time when a credit card payment is made?
• Users earn CRED coins based on bill payment amount, credit score tier, and partner offer rules
• Scale: 12M users, peak at bill payment deadlines (end of month)
• Key challenges: rule engine flexibility (rules change frequently), real-time vs batch processing trade-off, deduplication of reward events

2. Credit Card Statement Processing

• Millions of PDFs ingested per month from 50+ banks
• Extract transaction data, credit limits, due dates
• Key challenges: diverse PDF formats, OCR reliability, handling statement errors gracefully, PII handling

3. CRED Rent / CRED Pay Systems

• CRED Rent: pay rent via credit card (UPI-based NACH for landlord)
• Design the reconciliation system for rent payments that spans credit card network → CRED → UPI → landlord bank

What CRED expects in system design: Go beyond drawing boxes. Discuss consistency guarantees (eventual vs strong), failure modes, retry strategies, and how you'd monitor the system. Generic high-level diagrams without depth fail CRED's bar.

CRED PM interviews test whether you understand the premium credit card user demographic in India and can design for their specific context.

CRED's user: Salaried professional or business owner with a credit score above 750. Uses 2–3 credit cards. Pays bills on time. Is financially sophisticated enough to use CRED for rewards arbitrage.

Sample PM case studies from CRED interviews:

'CRED has a feature that lets users store and manage multiple credit cards. Retention for users who add their second card is 40% higher than users who add only one. Design a flow to increase second-card addition rate.'

'CRED wants to expand into lending (CRED Flash: personal loans to existing users). Design the product experience for a user discovering and applying for a ₹1L personal loan within the CRED app.'

'CRED's bill payment volume is concentrated in the last 5 days of each month. Design a feature to smooth this distribution and improve user payment habits.'

What CRED PM interviews look for:

• Comfort with financial products (credit scores, APR, credit limits, NACH mandates)
• User empathy for the premium segment (not tier-2 users; CRED's user base is the top 3% by credit score)
• Metrics sophistication: not just DAU/MAU but retention cohort analysis, LTV, NPL (non-performing loans) awareness for lending products
• Design polish: CRED's product is known for exceptional UI; PM candidates are expected to care deeply about experience quality

CRED pays among the highest salaries in Indian tech for the roles it hires, reflecting both the high bar and the pre-IPO ESOP risk premium:

Software Engineer:

• Junior SE (SE-1): ₹12–34 LPA total (base + ESOP at FMV)
• Mid SE (SE-2): ₹22–60 LPA
• Senior SE (SE-3): ₹42–114 LPA
• Staff/Principal: ₹95–145 LPA

Product Manager:

• APM/PM-1: ₹17–38 LPA
• Senior PM: ₹30–84 LPA
• Group PM / Director: ₹54–156 LPA

UX/Product Designer:

• Junior Designer: ₹10–29 LPA
• Senior Designer: ₹34–96 LPA

ESOP reality: CRED is pre-IPO (as of July 2026). ESOP grants vest at FMV (Fair Market Value) set at the last valuation round. Liquidity requires an IPO, secondary sale, or employee buyback program. CRED has run secondary sales in the past, but frequency and discount are not guaranteed.

Negotiation: CRED negotiates hard but does not move much on cash. They move on ESOP grants (number of units, vesting schedule). Fixed-to-ESOP ratio at CRED skews more to ESOP than at Razorpay or Swiggy: factor this in when comparing offers.