The hiring process
| Round | Format | What's tested |
|---|---|---|
| Take-Home Assignment (sometimes) | ~24 hr window | Applied build / screening |
| DSA + Puzzles | ~90 min | Problem-solving and reasoning aloud |
| Machine Coding / LLD | ~1.5-2.5 hr | Build an extensible in-memory system |
| System Design + Managerial | ~90 min | Scalable design + leadership fit |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Take-Home Assignment (sometimes)
~24 hr windowFor some roles, a short take-home shared within 24 hours of application, used alongside your projects and experience to shortlist. Clean, working, well-structured code matters.
- Implement a small feature or service
- Model a mini-system with clean OOP
- Handle input parsing and edge cases
- Include basic tests
- Write a short design rationale
- Practice building small, clean, tested services
- Structure code into clear modules
- Write a concise README/rationale
- Cover edge cases and validation
- Sloppy, untested code
- No structure or documentation
- Ignoring edge cases
- Clean, working, tested code
- Clear structure and rationale
- Attention to detail
DSA + Puzzles
~90 minRoughly 90 minutes of mostly medium problems emphasizing arrays and strings, plus logic puzzles. Some candidates code in a shared Google Doc rather than an IDE, so explaining your approach out loud matters as much as the code.
- Array/string medium problems
- Hash-map based logic
- Logic and math puzzles
- Two-pointer / sliding window
- Reasoning through an approach verbally
- Drill array/string mediums (NeetCode, free)
- Practice coding without IDE autocomplete
- Rehearse narrating your reasoning clearly
- Do a few classic logic puzzles
- Silent coding in a shared doc
- Syntax errors without IDE help
- Getting stuck on puzzles without talking it through
- Clear verbal reasoning
- Correct code without IDE crutches
- Strong problem decomposition
Machine Coding / LLD
~1.5-2.5 hrCRED's most distinctive round. You get a product requirement (a contact-management system is frequently reported) and 1.5-2 hours to implement it with good OOP, SOLID, and error handling, using in-memory data structures rather than a real database, verified with your own unit tests.
- Design a contact-management system
- Model an extensible service with clean OOP
- In-memory storage and query operations
- Error handling and input validation
- Write unit tests for your own code
- Build in-memory OOP systems under a 2-hour timer
- Master SOLID and design patterns
- Practice writing your own unit tests
- Make designs extensible and add error handling
- No unit tests
- Monolithic, non-extensible design
- Weak error handling / validation
- Clean, extensible OOP with tests
- Robust error handling
- Working, demonstrable system
System Design + Managerial
~90 minA round (often with senior engineering leadership) where you design a scalable solution to a real-world scenario from CRED's domain, blended with managerial/behavioral questions. Fintech concerns like idempotency and de-duplication feature prominently.
- Design a scalable fintech feature (rewards, payments, statements)
- Idempotency and exactly-once handling
- Data de-duplication and consistency
- Ownership and handling ambiguity
- Why CRED
- Study system-design-primer + idempotency/dedup (free)
- Practice a scalable fintech design end-to-end
- Prepare 4-5 STAR stories with ownership
- Research CRED's product and audience
- No idempotency/consistency plan
- Weak behavioral stories
- No specific motivation
- Correctness-aware, scalable design
- Clear ownership and judgment
- Genuine interest in CRED
What to master
- Arrays and strings (with verbal reasoning)
- Hash maps and logic puzzles
- OOP, SOLID, design patterns
- Machine coding: in-memory systems with unit tests
- Error handling and input validation
- Scalable fintech system design
- Idempotency and de-duplication
- Ownership and STAR stories
Eligibility
SDE-1 through SDE-2+; machine coding is central across levels, and the system design + managerial round scales in depth. CRED shortlists partly on relevant projects and prior experience.
CRED salary & compensation (2026)
Premium-brand fintech unicorn; pays top-of-market fixed plus heavy ESOP, among the highest Indian startup packages.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE-1 | 0-2 yrs | ₹28-45 LPA | — | aggressive fixed + ESOP; targets top campuses |
| SDE-2 | 2-5 yrs | ₹48-75 LPA | — | large ESOP grant; market-leading fixed |
| SDE-3 | 5-8 yrs | ₹80-130 LPA | — | ESOP 30-40% of CTC |
| Staff Engineer | 8-12 yrs | ₹140-200 LPA | — | equity-dominant; small elite teams |
| Principal | 12+ yrs | ₹210-300 LPA | — | among the highest Indian IC packages |
How the package is structured
- Known for paying premiums to attract top talent; both fixed and ESOP run high.
- ESOPs vest 4 yrs; liquidity via buyback events.
- Joining bonus ₹3-7L common at senior hires.
- Lever: CRED bids aggressively against competing offers, so strong alternatives raise both fixed and ESOP substantially.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1-2: Array/string mediums + verbal-reasoning practice
- Days 3-6: Build in-memory OOP systems with unit tests, timed
- Days 7-9: SOLID/patterns + error-handling drills
- Days 10-11: Fintech system design + idempotency/dedup
- Days 12-13: Ownership STAR stories
- Day 14: Full mock loop
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
What is CRED's most important round?
The machine-coding/LLD round. You build an extensible in-memory system (often contact management) with good OOP, SOLID, error handling, and your own unit tests.
Do I use a real database in machine coding?
No. CRED expects in-memory data structures rather than a real database, verified with unit tests you write yourself.
Why might I code in a Google Doc?
Some DSA rounds are conducted in a shared doc without IDE help, so practice coding cleanly by hand and narrating your reasoning.
What fintech concepts appear in design?
Idempotency, exactly-once handling, and data de-duplication feature prominently in the system design round.
Is there always a take-home?
For some roles. CRED shortlists partly on relevant projects and prior experience and may share a short take-home within 24 hours of applying.
How many rounds?
Typically 4: a possible take-home, DSA + puzzles, machine coding/LLD, and system design + managerial.