What questions are asked in CRED interviews?

CRED interviews commonly cover DSA or aptitude screening, core CS (OOPs, SQL), project discussion, and domain topics such as credit lines, reward systems, bill payment flows. Behavioural rounds check ownership, teamwork, and why CRED.

How many rounds are there in the CRED interview?

CRED typically has 4 stages: Online Assessment (90 min), Technical Round 1 (45-60 min), Technical Round 2 (45-60 min), HR / Culture (20-30 min). Some drives skip a round or merge HR with managerial. Check that cycle's college placement email.

How should I prepare for CRED interviews?

For CRED, practise timed DSA or aptitude mocks, revise OOPs and SQL, prepare one crisp project narrative, and read up on credit lines and reward systems. Use STAR for behavioural answers.

CRED Interview Experiences

How CRED fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

CRED placement process includes: 1. Online Assessment (OA) - 90 minutes with 2-3 medium to hard coding problems, 2. Technical Interview Round 1 - 45 minutes focusing on data structures and algorithms, 3. Technical Interview Round 2 - 45 minutes covering system design for FinTech systems, 4. Managerial Round - 45 minutes with behavioral questions and technical discussions, 5. HR Round - 30 minutes for general discussion. Total duration: 2-3 weeks from application to offer.

Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.

Fresher package ballpark (from student reports): ₹18-25 LPA. Confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Online Assessment	90 min	Coding (DSA) + sometimes MCQs
Technical Round 1	45-60 min	DSA + backend / payments concepts
Technical Round 2	45-60 min	System design (payments / ledger)
HR / Culture	20-30 min	Motivation, integrity, relocation

Real interview experiences

Experience 1: SDE / backend engineer (2025)

Profile: B.Tech CSE, ~8.0 CGPA, tier-2 college, one internship, steady DSA practice

Online assessment

Timed coding on a platform (HackerRank or similar). Clean, passing solutions beat partial cleverness.
Shortlist mail typically arrived in a few days.

Technical rounds

Coding: Design an LRU cache, expected approach: HashMap + doubly linked list. They probed complexity and edge cases.
Follow-up: Implement a rate limiter, sliding window / token bucket.
Domain chat around credit lines and reward systems. Plain explanations worked better than buzzwords.
Detailed project discussion: stack choice, hardest bug, and what you would rebuild.

HR / managerial

Why fintech / payments?
A production bug or outage you helped with
Keep answers short, situation, what you did, result.

Result: Selected
What helped: Talking through the approach before coding, and connecting project work to CRED’s world (credit lines).

Experience 2: SDE / backend engineer (2024-2025)

Profile: B.Tech IT / ECE, ~7.2 CGPA, strong projects, average contest rating

What differed

Screening felt tighter on time; one question needed an optimised pass to stay competitive.
Later round leaned into bill payment flows: APIs, data choices, and failure modes at a fresher depth.
Warm-up: Merge overlapping time intervals, sort + sweep.

Mistakes that hurt other candidates

Coding before clarifying constraints
Treating HR as a formality
System-design jargon without a simple bottleneck story

Result: Selected after HR / managerial
Takeaway: At CRED, clear DSA plus a coherent story on credit lines usually beats a high CGPA with weak explanation.

Questions that come up often

Coding / technical

Design an LRU cache. Usually expects HashMap + doubly linked list
Implement a rate limiter. Usually expects sliding window / token bucket
Merge overlapping time intervals. Usually expects sort + sweep
Discussion on credit lines and reward systems, bottlenecks, failure modes, simple APIs
Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

Why fintech / payments?
A production bug or outage you helped with
An integrity / pressure scenario
Joining timeline

Practical tips for CRED

Clear the screening round first. Timed practice beats last-minute topic hopping.
For domain questions, explain credit lines in plain language, inputs, outputs, what breaks at scale.
OOPs and SQL still open a lot of CRED panels. Do not skip fundamentals.
HR answers should be concrete. One story with a result beats five slogans.
If you do not know something, say so and outline how you would find out.

HR interview

After technical rounds, CRED usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions

Common CRED HR questions, sample answer frames, and STAR tips.

CRED HR Interview Questions, common HR questions and how to structure answers
CRED Preparation Guide, round-wise prep plan
CRED Coding Questions, practice problems with approaches
CRED Previous Year Papers, past papers and patterns
CRED Placement Papers, eligibility, process, and papers

Similar companies

Razorpay · PhonePe · Paytm · Flipkart · Swiggy · Zomato