CRED Interview Questions and Answers
Last updated 2026-11-19
CRED handles credit card bill payments, rewards and a growing set of financial products for a high-trust user base, and its engineering interviews, as candidates describe them, put weight on code quality: a timed machine-coding build judged on class design, then DSA, then a design and managerial conversation. This page gives practice questions with worked answers on those areas.
They are practice questions on the topics the rounds are commonly reported to cover, not a record of what any candidate was asked. For code, see CRED coding round questions. The process is covered in how to crack the CRED interview.
| Typical rounds | Machine coding, DSA, system design plus managerial (commonly reported) |
|---|---|
| Entry route | Largely through internships (reported) |
Rounds as commonly reported
Reports describe a machine-coding or low-level design round of about two and a half hours, judged on class design and correctness, then a DSA round with medium to hard problems and puzzles, and a final round combining system design with a managerial discussion with engineering leadership. Entry for freshers is reported to be largely through internships.
CRED does not publish its rounds, so these are candidate-reported and vary.
Hiring status
We have no sourced hiring statements for CRED to quote, and this site has no CRED page under /hiring. Check the company's careers site at careers.cred.club for current roles.
What this implies for preparation
Practise writing a complete, running program in a fixed time, then read it as a reviewer would. Check naming, duplicated logic, error handling and whether adding a new rule would need edits in many places.
CRED Interview Questions and Answers: questions with worked answers
1 How would you design a reward and coin system for bill payments?
mediumModel a Reward with a rule (percentage, cap, minimum bill, expiry), and an Account with a ledger of credits and debits rather than a single mutable balance. When a payment succeeds, publish an event; a rewards service applies matching rules, writes ledger entries with an idempotency key so replays do not double credit, and notifies the user. Keep rules as data or strategy objects so campaigns change without redeploying.
2 Design the bill-payment reminder system.
mediumStore each card with its due date and a reminder schedule. A scheduler scans for upcoming dues, bucketed by date and sharded by user id, and puts reminders on a queue. Workers send through push or SMS according to preferences, and skip users who already paid, which they check just before sending. Retries use backoff, and sends are de-duplicated by user, bill and reminder type.
3 What makes a good machine-coding submission?
easyWorking code first, then structure: clear entities, single-responsibility classes, enums for fixed sets, interfaces for varying behaviour, and a driver demonstrating the flows. Validate inputs, avoid duplicated logic, name things for what they mean, and keep concurrency in mind. Resist over-engineering: a clean 300-line program beats a half-finished framework.
4 How do you handle money amounts in code?
easyUse integers in the smallest unit (paise) or a decimal type, never binary floating point because 0.1 + 0.2 is not 0.3. Define rounding rules once, in one place, for splits and percentages, and make sure splits sum to the total by giving the remainder to one party.
5 Explain the Observer pattern with a payments example.
easyA Payment publishes events when its state changes. Observers such as the rewards service, notification service and analytics subscribe and react independently. The publisher knows only the observer interface, so a new subscriber needs no change to payment code. In a distributed system the same idea is a message queue with consumers.
6 How would you build a search over a user's transactions?
mediumIndex transactions by user with fields for merchant, amount, date and category in a search engine, or for small scale a database with composite indexes on user and date. Support prefix and fuzzy match on merchant names, filter by date and amount range, and paginate by cursor. Keep search data eventually consistent with the ledger and say so.
7 How do you design for graceful degradation when a dependency such as the credit bureau is slow?
mediumSet timeouts and a circuit breaker, serve the last known good data with a timestamp where acceptable, queue the request for later refresh, and show the user clear messaging instead of an error. Monitor the dependency separately so you know when it recovers.
8 Describe how you would test a rewards calculation function.
mediumCover boundaries (zero bill, exactly the minimum, exactly the cap), rounding of fractions, expired and overlapping campaigns, large amounts, and idempotent reprocessing. Use table-driven unit tests and one property test, such as the reward never exceeding the cap. Keep time injectable so expiry tests are deterministic.
9 How would you migrate a large table without downtime?
hardCreate the new schema alongside the old, write to both (dual writes) or capture changes, backfill historical rows in small batches, verify counts and checksums, switch reads gradually behind a flag, then stop writes to the old table and remove it later. Keep a rollback at each step.
10 Why CRED, and what do you value in a team?
easyBe specific about what draws you to the product and its engineering standards, such as design quality or reliability, and give an honest answer about team values with an example of how you acted on them, such as thorough code reviews or documenting a decision.
11 Tell me about a time you pushed back on a decision.
easyUse STAR. State the decision and your concern with evidence, how you raised it respectfully and to whom, what the group decided, and how you committed to the outcome. If you were wrong, say what you learned.
12 Walk me through a project you are most proud of.
mediumChoose one with real trade-offs. Give the goal, your specific role, one design choice with the alternative you rejected, a problem you hit, and how you verified success. Close with what you would change now.
Frequently asked questions
How long is the CRED machine-coding round?
Candidate reports mention about two and a half hours. Check your invite for the exact time.
Does CRED hire freshers?
Reports suggest entry is largely through internships. For current programmes check the company's careers site.
What language should I use?
The one in which you write clean, working code fastest. Java and Python are commonly used.
Are puzzles asked in the DSA round?
Reports mention medium-hard DSA and puzzles. Practise a few classic ones aloud.
Sources
Related guides
More in Company Interview Questions
- Cyient coding round questions
- Cyient interview questions and answers
- D. E. Shaw Coding Round Questions With Solutions
- D. E. Shaw Interview Questions and Answers
- Delhivery Coding Round Questions
- Delhivery Interview Questions with Answers
- Dell Coding Round Questions with Solutions
- Dell Technologies Interview Questions and Answers for India Freshers
- Deloitte coding round questions
- Deloitte interview questions and answers
- Deutsche Bank coding round questions with solutions
- Deutsche Bank interview questions with answers (technology graduates)