Creditas logo

Creditas Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 28 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Creditas.

Showing 3 of 28
Creditas logo
Creditas

Software Engineer

Engineering · a year ago

Mid Easy Negative experience No offer 4 rounds
Interview process
Technical screen Recruiter call Onsite Background check Offer
Interview formats
Technical Coding Behavioral

I went through three interview stages: a screening, a chat with the team manager, and then a technical chat with a specialist dev where I did a cool LeetCode problem. After that, I got a generic email saying I didn't pass. Two months later, they messaged me on a Sunday asking if I was still available to work. They scheduled an interview for the next day with the tech lead, which was more about my life and career situation. I didn't hear anything for another two weeks, and then I got another generic email saying I didn't pass.

Confirmed questions1 question
  • What are you currently finding most difficult in terms of hard skills?
Creditas logo
Creditas

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The process was well-defined and they got back to me quickly with decisions. The people interviewing me were very straightforward about the role, telling me exactly what I'd be working on (tasks, technologies, etc.). I also got access to the role's budget early on, which was a plus.

Confirmed questions1 question
  • How would you handle team members with less knowledge than you?
Creditas logo
Creditas

Software Engineer

Engineering

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Technical screen
Interview formats
Behavioral Technical Coding System Design

My process had 4 stages: 1. Screening, 2. Chat with EM, 3. Architecture Case, 4. Technical Test. Initially, the HR person told me my process would be a bit unusual with only 3 stages, but this changed midway without any prior agreement. Stage 1 was relaxed and informal, focusing on professional history, though the interviewer was almost 30 minutes late (I doubt if I were late by the same amount it wouldn't be held against me). The second stage was the best; the EM was very open and sincere, asked relevant questions, and we had a very productive chat. Following that, the architecture case was also quite interesting, and interaction with everyone was smooth. However, the feedback between stages was very slow (usually 2 weeks or more), and I had to keep chasing the recruiter. After the architecture test, they said they wanted to add another stage (which wasn't initially part of the scope), allowing me to choose between a take-home project or a live test with interviewers. I chose the take-home project and submitted it on time. I then chased for feedback multiple times, and on the last follow-up (almost 3 weeks after submission), I received a vague rejection with no specific reasons or areas for improvement. Overall, I think the company might be good based on the people I spoke with, but the hiring process is disorganized, lengthy, and you don't get structured feedback at the end. Particularly, the lack of punctuality and inability to commit to a response timeline discouraged me during the stages.

Confirmed questions1 question
  • What is your experience with high-volume environments?

Creditas Software Engineer Interview Questions

Quoted word for word from Creditas interview reports.

Tell me about microservices, patterns for migrating from monoliths to microservices, and design patterns.

Read reports

If you could choose between a high-performance team, perfection, or business value, which would you choose and why?

Read report

Have you ever performed application deployments in a cloud environment?

Read report

Formats, difficulty and experience

Across all 28 Creditas interview reports.

Interview formats

Behavioral 35.3%
Technical 35.3%
Coding 17.6%
System Design 5.9%
Case 2.9%

Interview difficulty

Easy 25%
Average 57.1%
Difficult 17.9%

Candidate experience

Negative 32.1%
Positive 57.1%
Neutral 10.7%