0% found this document useful (0 votes)
265 views3 pages

CRED - Interview Process (Backend) - Campus

The CRED interview process consists of four rounds: a coding round on Hackerrank lasting 90 minutes, a project round also on Hackerrank for 150 minutes, a technical round lasting 75 minutes, and a HM discussion for 60 minutes. Candidates should prepare by familiarizing themselves with the Hackerrank platform and the required programming languages. The process emphasizes problem-solving, coding skills, and alignment with CRED's values.

Uploaded by

Aum Buddhadev
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
265 views3 pages

CRED - Interview Process (Backend) - Campus

The CRED interview process consists of four rounds: a coding round on Hackerrank lasting 90 minutes, a project round also on Hackerrank for 150 minutes, a technical round lasting 75 minutes, and a HM discussion for 60 minutes. Candidates should prepare by familiarizing themselves with the Hackerrank platform and the required programming languages. The process emphasizes problem-solving, coding skills, and alignment with CRED's values.

Uploaded by

Aum Buddhadev
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

CRED - interview process

Introduction​

We will be conducting the interview process on-campus. The candidates are requested to
ensure that they have optimal internet connectivity for a seamless experience during the
interview rounds.

We will be conducting the following interview rounds as described below

Interview rounds

R1 - coding round​

The coding round will be conducted on the Hackerrank platform. Please familiarize yourself with
the Hackerrank platform to ensure that you are comfortable with the online setup along with the
programming language of your choice (along with the version Ex: Python3, Java 8, etc).

This round would comprise 3 questions and a duration of 90 minutes. The questions would
range across topics of problem-solving, leveraging data structures & algorithms to solve
the problem elegantly.​

Skills: Problem-solving, Data Structure, Algorithms​

FAQs on Hackerrank as a platform
1.​ How to debug code
2.​ How to write code
3.​ How to submit my code
4.​ More FAQs

PS: Don’t use mobile, or leverage AI or earphones during this round.

R2 - project round
The project round would be conducted on the Hackerrank platform (project module) and would
have a duration of 150 minutes (2.5 hours). The intent of this round is to gauge how well you
can contribute to a real-world problem and a structured codebase.
The expectation during this round from you is to understand the problem statement (real-world
and ambiguous), able to break down and implement the same through the code. ​

We will also be providing basic code structure & skeleton to avoid cold start problems. You will
be expected to navigate through the code and understand the current setup before you could
start adding the implementation at the appropriate places.

Skills: Hands-on Coding, Solving real-world problems, Clean Code, familiarity with OOPS
methodology (Encapsulation, Abstraction, Modularity, Extensibility), SOLID, DRY principle.​

You will be evaluated on the basis of the above points and functional completeness of the
project.

The choice of programming language would be limited in the project round to the following
●​ Java 8
●​ Python 3.5+
●​ NodeJS
●​ C++

PS: Don’t use mobile or earphones during this round.

R3 - technical round
The technical round would be conducted virtually/ in person for a duration of 75 minutes.

During this discussion, you will interact with the CRED team members and the topics would
range from problem-solving, applying first principles to break down & solve them, leveraging
data structures, algorithms, and CS fundamentals along with domain modeling of real-world
problems.

PS: We promise to not ask standard questions like “Find a loop in Linked List” and make this an
interesting discussion

R4 - HM discussion
The HM discussion would be conducted virtually/in person for a duration of 60 minutes. In this
discussion, you will interact with senior tech team members and leaders.

This conversation would be centered around you and we would like to know and learn more
about you - your behaviors and values & belief system that has shaped you. Along the way, we
will also discuss how that resonates with the CRED values.

PS: No questions about “where you see yourself in 5 years” from us


Resources & Links
●​ Sample code - https://github.com/gauravrmsc/calculator
●​ 42 IntelliJ IDEA Tips and Tricks
●​ How to write clean code? Lessons learnt from “The Clean Code” — Robert C. Martin
●​ Clean Code - Uncle Bob - Playlist
●​ google/libphonenumber - C++
●​ Git basics
●​ Git Basic Commands

You might also like