CRED - interview guide

CRED interview questions - a complete guide

CRED's machine coding round looks for clean OOP and extensibility, not just working code. Every round is reported to be a knock-out.

Language:EnglishHinglish

About CRED

CRED is an Indian fintech app for credit card bill payments and rewards, known for its design and user experience. Its engineering works on payments, rewards and large scale.

This guide covers 13 CRED interview questions with answers - what each question checks and how to answer it - plus the CRED interview process, round by round, a 7-day preparation plan for freshers, tips and the mistakes to avoid.

CRED hiring process

  1. Coding round

    Sometimes 3 questions on HackerRank (~90 minutes), sometimes a take-home assignment.

  2. Machine coding and technical

    Emphasis on OOP and extensibility; medium-hard, application-based DSA.

  3. Hiring manager and HR

    Projects and fit - every round is a knock-out.

CRED does not publish its India fresher interview process in detail (as of our check). This is based on candidate reports - many of them for experienced roles, so the fresher process can differ. Confirm with the recruiter.

Sources (checked 16 October 2026): CRED Careers. Hiring processes change - read the official notice before you apply.

CRED interview questions and answers

Machine coding

  1. 1.Machine coding: build a rewards points system.

    What they're checking
    Domain + OOP.
    How to answer
    User, Transaction, RewardRule (different rules as different classes), a points ledger. Adding a new rule should be easy - that is extensibility.
  2. 2.What does extensible code mean? Give an example.

    What they're checking
    Reports name a lack of OOP and extensibility as a rejection reason.
    How to answer
    Adding a feature shouldn't mean breaking old code - interfaces and strategies. A new payment method is just a new class.
  3. 3.Design a credit card bill reminder system.

    What they're checking
    Domain thinking.
    How to answer
    Each card's due date; a scheduler; reminders (3 days before, 1 day before) - and stop if it is already paid.

DSA and puzzles

  1. 4.If a linked list has a cycle, find the node where the cycle starts.

    What they're checking
    A cycle question has been reported.
    How to answer
    When slow and fast meet, move one pointer to the head; move both one step at a time - where they meet is the start.
  2. 5.Spot a fraud-like pattern in transactions: more than 3 in one minute.

    What they're checking
    Application-based DSA.
    How to answer
    A sliding window (deque) of timestamps per user; flag when the window has more than 3.
  3. 6.Find the minimum number of coins for an amount (coin change).

    What they're checking
    DP.
    How to answer
    dp[x] = min(dp[x - coin] + 1) over each coin; -1 if it can't be made.
  4. 7.Puzzle: 100 doors - how many stay open?

    What they're checking
    Puzzles have been reported.
    How to answer
    Only the perfect-square doors (1, 4, 9...) stay open - 10. Because they have an odd number of divisors.

Hiring manager

  1. 8.Name a product whose design you love - why?

    What they're checking
    CRED is design-focused.
    How to answer
    A specific product, what you liked (simplicity, speed, detail), and what you learn from it.
  2. 9.What was the best design decision in your project?

    What they're checking
    Engineering thinking.
    How to answer
    The decision, the alternatives, and why it was better - even better with numbers.
  3. 10.Why CRED?

    What they're checking
    Motivation.
    How to answer
    Fintech and a premium user experience - whatever genuinely appeals to you.
  4. 11.Tell me about a time you changed your code after feedback.

    What they're checking
    Learning.
    How to answer
    What the feedback was, what you changed, and what you watch for now.

More questions

  1. 12.What happens if you don't pay a credit card bill on time?

    What they're checking
    Understanding CRED's domain.
    How to answer
    A late fee, interest on the unpaid amount, and a bad effect on your credit score.
  2. 13.How would you write unit tests in machine coding?

    What they're checking
    Code quality - CRED values design and quality.
    How to answer
    Tests for normal, edge and invalid input for each important class; swapping dependencies through interfaces makes testing easy.

7-day preparation plan for the CRED interview

  1. Day 1: OOP and SOLID principles.
  2. Day 2: Machine coding - a rewards system with extensible design.
  3. Day 3: Linked lists and sliding windows.
  4. Day 4: DP - coin change, knapsack.
  5. Day 5: A second machine coding problem.
  6. Day 6: Puzzles and hiring manager stories.
  7. Day 7: A mock round.

Preparation tips

  • Pay special attention to OOP principles and extensibility in machine coding.
  • DSA up to medium-hard - practise application-based questions.
  • Every round is a knock-out - prepare fully for each.

Mistakes to avoid

  • Working code with weak design in machine coding - not enough for CRED.
  • Easing off in a round that seems 'easy' - every round is a knock-out.
  • Not thinking about the product in design questions.

Frequently asked questions

What does CRED look for in machine coding?

According to reports, OOP principles and extensibility along with working code.

How hard is CRED's DSA?

Commonly medium to hard, application-based questions.

Is there a take-home assignment at CRED?

A take-home assignment has been reported for some roles.

Does CRED ask puzzles?

Some reports mention a round with puzzles alongside DSA.

Ready for your CRED interview?

Practise these questions with Cuelyte AI: add your resume, type a question and get a clear answer in your own words - in English, Hindi or Hinglish. Free to start.