CRED HR interview questions and answers

11 CRED HR interview questions with sample answers: why HR asks each one and how to answer. From public candidate reports. Free.

At CRED the HR or recruiter conversation usually comes early, often as a 30 minute call before the machine coding and DSA rounds, and again near the end to close on salary, notice period and joining date. Candidates report the first call happening within a day or two of applying, with the next round scheduled fast. It is conversational, not a stress round, and the person is usually a recruiter or HR business partner.

What the CRED HR round checks:

The first question is always some version of "tell me about yourself". Write your self introduction for the interview (free, no signup).

CRED HR interview questions with answers

3 of these 11 questions appear in public CRED interview reports; the rest are standard HR questions the company is known to ask.

1. Can you describe your career aspirations and long-term professional goals? (reported)

Why they ask: They want to see if your direction lines up with the kind of work CRED does, and whether you will stay long enough to be worth training.

How to answer: Keep it to two horizons: what you want to get good at in the next two years, and the kind of engineer you want to become in five. Tie both to backend or product engineering, not vague growth. Avoid saying you want to move into management soon.

Sample answer: In the next couple of years I want to get genuinely strong at backend engineering, especially designing systems that stay correct under load. I have done [project or internship work] and I liked owning a piece end to end, from schema to API to the on-call fix. Longer term I want to be the person a team trusts with a messy problem, not just a ticket. CRED appeals to me because the scale is real and the product is consumer-facing, so the quality bar is visible.

2. Tell me about your past experience and what you worked on. (reported)

Why they ask: This is the recruiter building a picture of your background before the technical panel reads your resume.

How to answer: Pick two or three things, not your whole resume. For each, say what the product was, what you owned, and one concrete outcome. If you are a fresher, use internships and serious projects the same way. Keep numbers honest, do not inflate.

Sample answer: I am a [year] graduate from [your college]. During my internship at [company] I worked on [feature or service], and my main piece was [what you built]. The part I am proudest of is that we cut [specific thing, like a slow query or a manual step] and it shipped to real users. Before that I built [project] on my own, which is where I actually learned to debug and read other people's code. I am comfortable in [language] and I have used [framework or database].

3. Why CRED, and why are you leaving your current company? (reported)

Why they ask: They are checking whether your reason for moving is pull towards CRED or just push away from your current job, and whether the story holds up.

How to answer: Give one specific reason about CRED's product or engineering culture, not generic praise. For the leaving part, stay factual and non-bitter: limited scope, wrong domain, or wanting more scale. Never badmouth a manager or a teammate.

Sample answer: I have used CRED and I like that it is a product where design and engineering both have to be sharp, because users notice immediately. On the current job, the work is fine but it is [narrow scope or a different domain], and I have stopped learning at the pace I want. I am not running from anything, I am looking for a place where backend problems are harder and the feedback loop is faster. That is the honest reason.

4. What are your salary expectations?

Why they ask: They need a number to check against the band before the offer stage, and they are watching whether you negotiate reasonably.

How to answer: Give a range, not a single number, and anchor it to what you currently earn or what the market pays for your experience. Say the range is negotiable for the right role. If you are a fresher, ask what the standard band is instead of guessing.

Sample answer: My current fixed is [amount] and I am looking for a reasonable step up, so I would say [lower number] to [upper number] depending on the role and the level. I am flexible on the split between fixed and variable if the overall package makes sense. To be honest, the work matters more to me than squeezing the last rupee, but I do want to be paid at market for my experience.

5. How soon can you join, and what is your notice period?

Why they ask: CRED moves fast and they want to know if your timeline fits their hiring plan.

How to answer: State your notice period exactly as it is in your contract, then say what you can realistically do about it. If you can join earlier, say so clearly. Do not promise a date you cannot keep, because it will come up again at offer stage.

Sample answer: My notice period is [number] days, so realistically I can join by [month]. I have already spoken to my manager about it and I can try to shorten it if the buyout is workable, but I would rather commit to a date I can actually meet than promise something and then delay. If you need me earlier, I am happy to discuss how that would work.

6. Are you open to relocating to Bengaluru, and are you comfortable with the work location?

Why they ask: Most CRED engineering roles sit in Bengaluru, and they do not want a relocation surprise after the offer.

How to answer: Answer directly. If you are already in Bengaluru, say so. If not, say you are willing to move and give a rough timeline. If you have a genuine constraint, raise it now, not after the offer.

Sample answer: Yes, I am open to relocating to Bengaluru. I am currently in [city] and I can move within [number] weeks of joining, so it will not delay my start date. I have lived away from home before during my [internship or college], so settling in is not a problem for me. I would just need the joining date a couple of weeks in advance to sort out accommodation.

7. Do you have any questions for us?

Why they ask: They are checking whether you have actually thought about the role and the company, or whether you are just applying everywhere.

How to answer: Ask two or three real questions about the team, the tech, or the process. Good ones: what does the first six months look like, how is the team structured, what is the on-call rotation. Avoid asking only about salary and leave in this round.

Sample answer: A few things. What does the first three to six months look like for someone joining this team, is there a defined ramp-up or do you own something from week one? How is the team split between backend, platform and product engineers? And what does the on-call or release process look like in practice? I am asking because I want to know what I am signing up for, not just the title.

8. Walk me through your resume and any gaps or switches in it.

Why they ask: Recruiters check for consistency between what you claim and what the documents will show later.

How to answer: Go chronologically and briefly. If there is a gap or a switch, explain it in one plain sentence without over-explaining. Keep dates and titles matching what is on your resume and what your payslips will show.

Sample answer: Sure. I did my B.Tech in [branch] from [your college], graduating in [year]. After that I joined [company] as [title], where I worked on [area] for [duration]. Then I moved to [current company] for [reason, like a better backend role]. There is a [number]-month gap between [period] and [period], which was [reason, like preparation or a family matter], and I was doing [what you did] during that time. Everything else is straightforward.

9. What are your strengths and one area you are working on?

Why they ask: They want self-awareness, not a rehearsed list of adjectives.

How to answer: Pick one real strength and back it with a small example. For the weakness, choose something genuine but not disqualifying, and say what you are actively doing about it. Do not use the fake weakness like 'I work too hard'.

Sample answer: My strength is that I stay with a problem until it is actually fixed, not just until it compiles. During [project or internship] I spent two days on a bug that turned out to be [cause], and it was worth it because it was breaking [impact]. The thing I am working on is that I used to go quiet when I was stuck instead of asking early. I have started writing a short status note when I am blocked for more than a few hours, and it has helped my team and me.

10. How do you handle pressure or a deadline that looks impossible?

Why they ask: CRED ships fast and they want to know you will not freeze or silently miss a date.

How to answer: Describe a simple method: break the work down, flag the risk early, and agree on what gets cut. Give one short real example. The point is that you communicate before things go wrong, not after.

Sample answer: First I figure out what is actually fixed and what is negotiable in the deadline. Then I tell the people who need to know, early, what is at risk and what I would cut to hit the date. In my [internship or project] we had a release in [timeframe] and one part was not going to make it, so I flagged it on day two and we shipped the core and pushed the rest. Nobody was surprised, which is the main thing.

11. Are you interviewing anywhere else, and where does CRED stand for you?

Why they ask: They are gauging how fast they need to move and how serious you are about CRED specifically.

How to answer: Be honest about having other processes, but do not use it as a threat. Say clearly where CRED sits and why. If CRED is your first choice, say it plainly, because recruiters act on that.

Sample answer: Yes, I am in a couple of other processes, but they are at different stages. CRED is genuinely one of my top choices because [specific reason about the product or the engineering]. I am not using other offers to play games, I just want to be transparent so we are not wasting each other's time. If things move here, I am ready to move quickly on my side too.

What candidates report about the CRED HR round

Recruiter call timing. Candidates report the first HR or recruiter call coming within a day or two of applying, sometimes right after a DM to a recruiter, and the next round being scheduled for the following day or the next weekend.

Round length. The recruiter call is reported as roughly 30 minutes, covering previous experience, projects, why CRED and why leaving the current company.

Process order. Reports show HR or recruiter contact early, then a machine coding or LLD round of 2.5 to 3 hours, then DSA and further interviews, with HR closing again at offer stage.

Location. Engineering roles are reported in Bengaluru, so relocation and joining timeline come up in the HR conversation.

Salary and notice discussion. Commonly reported for Indian product companies: the recruiter asks for current fixed pay, expected range and notice period before the offer stage, so have these numbers ready and consistent with your documents.

Document checks. Commonly reported for Indian tech firms: payslips, offer letters and education certificates are verified before or during onboarding, so keep your resume dates and titles matching your paperwork.

How to prepare

Practise the CRED HR round in a free 5-minute mock

CRED technical rounds

Quick answers about the CRED HR round

What is asked in the CRED HR interview?

Candidates report questions such as: Can you describe your career aspirations and long-term professional goals; Tell me about your past experience and what you worked on.; Why CRED, and why are you leaving your current company; What are your salary expectations. Each one is answered on this page.

How long is the CRED HR round?

At CRED the HR or recruiter conversation usually comes early, often as a 30 minute call before the machine coding and DSA rounds, and again near the end to close on salary, notice period and joining date. Candidates report the first call happening within a day or two of applying, with the next round scheduled fast. It is conversational, not a stress round, and the person is usually a recruiter or HR business partner.

Can I fail the CRED HR round?

Yes. Candidates are rejected in the HR round for unclear answers on relocation, shifts or the package, for contradicting their resume, or for seeming uninterested in CRED. Decide your honest answers before the call.

Are these questions official?

No. They come from public candidate reports and are unofficial. PortLume AI is not affiliated with CRED.

Sources

Based on 12 public reports: LeetCode Discuss (6), AmbitionBox (3), Reddit (2), Glassdoor (1), last updated Oct 2026.

Unofficial guide from public candidate reports. PortLume AI is not affiliated with CRED. HR questions for other companies · all company interview guides.

Featured on FoundrList

PortLume AI

Loading…