HR interview questions
Common CRED HR questions, sample answer frames, and STAR tips.
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
Section titled “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
Section titled “Real interview experiences”Experience 1: SDE (Android), fresher with heavy internship background
Section titled “Experience 1: SDE (Android), fresher with heavy internship background”Published GeeksforGeeks write-up. The candidate was a recent graduate but had roughly two years of Android and backend internships, including one at a unicorn startup.
Round 1: take-home assignment (24-hour window)
- Build a proof of concept for an animation-heavy feature in native Android, following Clean Architecture properly - including API handling and view-state persistence.
Round 2: DSA and puzzles (~1.5 hours)
- Medium-difficulty data-structure problems, plus puzzles.
- Notably, code was written in a Google Doc, not an IDE. Nothing compiles or runs, so the explanation of your approach is being assessed as much as the code.
Round 3: core domain depth (~2.5 hours)
- Started at basics (lifecycle questions) and escalated into Clean Architecture in detail.
- Design the app’s high-level architecture, with the interviewer progressively adding complexity to the requirements.
Round 4: system design + managerial (~1.5 hours, with the Head of Engineering)
- Design an analytics SDK.
- Cultural fit and career goals.
Result: Selected - HR confirmed the same day as the final round.
What the candidate highlights: the loop tested development skill rather than grinding DSA, and most rounds had two interviewers, which made them feel like discussions rather than interrogations.
Experience 2: the machine-coding round is where most candidates are filtered
Section titled “Experience 2: the machine-coding round is where most candidates are filtered”Consolidated from public prep write-ups and candidate reports on the SDE loop, since individual accounts vary by track (backend, Android, automation).
- The structure is broadly consistent: take-home assignment → DSA and puzzles → machine coding / low-level design → system design plus managerial with a senior engineering leader.
- Machine coding is the CRED-specific round and the one most often described as decisive. Reported themes: implement an LRU cache, design a key-value store, apply SOLID principles and design patterns, reason about idempotency, and justify a schema.
- Idempotency comes up because of the domain. In a payments and credit-card-bill product, a retried request must not double-charge. Being able to explain why an operation needs an idempotency key is a genuine differentiator here, not a buzzword.
- DSA is medium, not hard. Multiple reports put the problems at LeetCode-medium. The differentiator is clean, explainable code under whiteboard-like conditions.
- The final round is fit-heavy but still technical. Expect to defend design choices from earlier rounds.
Sources for this section
- CRED Interview Experience for SDE - GeeksforGeeks
- CRED Interview Experience for a Software Developer - GeeksforGeeks
- CRED Interview Experience for Automation Engineer, online coding round (fresher) - GeeksforGeeks
- CRED internship drive examination experience - GeeksforGeeks
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “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
Section titled “HR / behavioural”- Why fintech / payments?
- A production bug or outage you helped with
- An integrity / pressure scenario
- Joining timeline
Practical tips for CRED
Section titled “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
Section titled “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.