What Is the CRED Interview Process Like? (Round by Round)

Candidates report four to six rounds at CRED, and the exact set depends on the role and the level. The common path starts with an online coding test on HackerRank. Reports describe three problems in about 90 minutes, and one report describes 105 minutes. A project or machine coding round, also reported on HackerRank and lasting about 150 minutes, usually follows.

Then come one or two technical interviews on video, each about 75 to 90 minutes. The last round is a culture fit or managerial conversation of about 60 minutes. Several candidates report that it is with a senior engineering leader. Reports also describe rounds scheduled on consecutive days once the process starts.

Quick Overview

Stage 1: The Online Coding Test

Candidates report a proctored test on HackerRank with three problems. An online assessment is a timed coding test you take alone, with no interviewer present. Reported durations are about 90 minutes in one account and 105 minutes in another. Reports describe the problems as unusual rather than textbook, with topics such as greedy logic, bitmask dynamic programming, and combinatorics.

Campus candidates report that most applicants are removed at this step, and one report describes about 200 people taking the test with about 20 moving forward. If you want the general format, read what an online technical assessment is.

Stage 2: The Project or Machine Coding Round

This is the round candidates describe as the hardest to prepare for. A machine coding round is a long session where you build a small working program from a written requirement list. Reports describe about 150 minutes on HackerRank, with the code submitted at the end and then reviewed. You are graded on whether the program runs, how the classes are organized, and whether a new requirement can be added without a rewrite.

Reported problems include a file manager with insert, delete, move, and search operations, a payment processor, a cache, and a search box with suggestions. The full topic list is in the CRED system design interview.

Stage 3: Technical Interviews

Reports describe one or two live technical rounds of 75 to 90 minutes each, and the content varies by role. Some candidates report data structure problems at medium difficulty, solved by talking through the approach rather than in a full editor. One report describes this round in a shared document instead of an IDE.

Other candidates report questions on object oriented programming, databases, operating systems, and their own projects. Expect the interviewer to ask why you chose each approach.

Stage 4: Culture Fit or Managerial Round

Candidates report a final conversation of about 60 minutes with an engineering lead, and it covers teamwork, communication, ownership, and career direction. Some reports describe technical discussion inside this round as well, including schema design and failure handling.

A CRED engineering leader has said publicly that the company looks for people who solve problems elegantly, so be ready to explain a decision you made and the reason behind it. Prepare the motivation question with how to answer why CRED.

How the Campus Path Differs

On-campus and internship drives start with the same coding test on HackerRank, and one campus report describes an eligibility filter on CGPA before the test. Campus reports then describe a single technical interview, which covers the work from the coding round and the project round. That interview focuses less on system design and more on fundamentals.

Timeline and Decision

Reports describe a compressed process once scheduling begins, with rounds on consecutive days in several accounts. One candidate reports a decision on the same day as the final round. Other candidates report flexible scheduling that let them space the rounds about a week apart.

Reported waits after the loop vary widely, and at least one candidate reports waiting for a result long after the round. The full picture is in how long it takes to hear back after a CRED interview.

Questions to Ask Them

Every round leaves time for your questions, and the good ones here are specific to the product. Ask how payment failures are handled between the app and the bank. Ask how the team measures reward correctness. Ask how design and engineering work together, since CRED describes itself as a design-first company, and ask what the first three months look like for a new engineer.

How to Prepare

• Practice timed problem solving. Grokking the Coding Interview teaches the patterns behind the medium and hard problems in the online test.
• Build small programs under a time limit. Write a working console program in two hours, with clean classes and a test for each requirement.
• Study fintech system design. Grokking the System Design Interview covers queues, caches, and databases, which every payment design uses.
• Prepare one project story in depth. Interviewers ask for decisions, alternatives, and failures, not a feature list.