CRED, the Bengaluru members' app for credit card bill payments and rewards, is known for its design-led product. Engineering candidates report a strict loop that opens with a long machine coding round, where code quality and extensibility weigh as much as a working answer. This page covers what CRED builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.
What CRED builds and who it hires
CRED's engineers build bill payments, rewards, its commerce and lending products, and the apps that carry its distinctive visual style. CRED has open-sourced NeoPOP, its design system, for Android, iOS, Flutter and web, and an engineering lead has said in an interview that the back end and data platform use Java and Go, with Kotlin, Swift and Flutter on mobile and React on web.
- Back-end engineers: Java and Go services.
- Android and iOS engineers: polished, animation-rich apps.
- Front-end engineers: React web.
- Data platform engineers: pipelines and analytics.
What the process tends to look like
| Stage | What happens | How to prepare |
|---|---|---|
| Recruiter call or referral | Role, level (SDE-1, SDE-2 or SDE-3), team and timeline | Know the product, the team and your own résumé in detail |
| Machine coding | A HackerRank-hosted build, reported at up to 2.5 hours, introduced by an interviewer | In-memory systems with clean OOP and room to extend |
| Technical discussion: DSA and LLD | Problems plus a design, such as a service that polls an endpoint on a schedule | Schedulers, retries and class design |
| Hiring manager | Projects, judgment and craft | Stories about quality and attention to detail |
Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.
Machine coding, design and product craft
Working code is not enough. One reported machine coding task was an in-memory database with primary and secondary indexes. A candidate who got the code working but did not follow OOP principles or leave room for extension believes that cost the offer. Plan interfaces before you type.
Rounds are knockouts. Candidates describe each round as eliminatory, so prepare evenly: one weak round ends the loop.
Product craft. CRED cares about how the product feels. Mobile and front-end candidates should be ready to discuss animation performance, reusable components and design systems such as NeoPOP; back-end candidates should show they understand the user flow their API supports.
Representative problem types
These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.
- Build an in-memory database with primary and secondary indexes.
- Build a file manager with nested folders and operations.
- Design a scheduler that calls an endpoint at a fixed interval with retries.
- Design a rewards ledger that awards and redeems points.
- Design bill reminders across many card issuers.
- Mobile: build a reusable animated button component.
- Medium DSA problems on trees and hash maps.
What interviewers score
- Working code: a solution that runs, handles edge cases and is readable by the next engineer.
- Practical judgment: the trade-offs you name and the simplest design that meets the requirement.
- Product sense: understanding who the user is and what failure looks like for them.
- Ownership: examples where you shipped, measured and fixed things yourself.
The behavioral side
Technical rounds decide most outcomes, but every CRED loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:
- Something you shipped end to end. Cover the user problem, your decisions, what you measured and what you would change.
- A disagreement with a teammate. Show how you made the decision on evidence and kept the relationship.
- Why this company? Connect its product and engineering problems to the work you want to do next.
Structures and sample answers for the common questions are in our software engineer behavioral answers guide.
A three-week prep plan
- Week 1: practical coding: build small features against an API, parse and transform data, and write tests, in the language you will interview in.
- Week 2: system design for the company's domain, plus two behavioral stories about shipping and fixing something under pressure.
- Week 3: timed mixed problems, a mock interview every other day, and research into the product and its engineering blog.
For practice lists, use LeetCode company-tagged questions, the Striver A2Z sheet or the Love Babbar 450 sheet, and if your drive starts with a test, read our guide to new-grad online assessments.
Where CoPilot Interview fits
Most of a CRED loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What programming language should I use in a CRED interview?
Use your strongest object-oriented language; Java and Go suit back-end roles, Kotlin or Swift suit mobile, and JavaScript or TypeScript suits web.
Does CRED send an online assessment?
Most reports describe an intro call followed by a machine coding round on HackerRank rather than a separate screening test. Internship hiring may differ.
What does CRED look for in machine coding?
Candidates report that a working solution is necessary but not sufficient: interviewers look for clear OOP structure, extensibility, sensible names and modular logic. Spend the first minutes designing interfaces and entities, keep the core flow working early, and leave the code easy to extend with a new requirement.
How should I prepare for CRED coding questions?
Practice practical problems under time limits, build small features against an API in your interview language, and prepare one system design in CRED's domain. Explain every solution out loud, because follow-up questions about trade-offs matter as much as the first answer.
Can I use AI tools in a CRED interview?
Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview