Ridecell logo

Ridecell Software Engineer Interview Questions
& Process

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

Based on 18 interview experiences · FREE TO READ

4.4 Rounds average
Average Typical difficulty
38.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Ridecell.

Showing 3 of 18
Ridecell logo
Ridecell

Software Engineer

Engineering · nearly a year ago

Mid Average Positive experience No offer 6 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Coding System Design Behavioral

First, they check out your resume to see if you've got the right stuff and any cool achievements. Then, a recruiter might hit you up for a quick chat about what you've done and if you're into the job. After that, you'll probably do some technical phone interviews, like 45-60 mins each, where you gotta code and solve problems. If that goes well, it's time for the main event: the onsite (or virtual) interviews. There will be a bunch of these, about 45 mins a pop. You'll tackle coding questions (think data structures and algorithms), and if you're going for a more senior gig, you'll get hit with system design questions. They also wanna see if you're a good fit and have leadership potential, so expect some Googliness/behavioral chats. After all that, a hiring committee will look at everything and decide if they wanna move forward with you. If they give you the green light, they'll try to find a team that fits. Once you're matched with a team, they'll send you the offer.

Confirmed questions1 question
  • Can you share your proudest accomplishment?
Ridecell logo
Ridecell

Software Engineer

Engineering · more than a year ago

Senior Easy Negative experience No offer 4 rounds
Interview process
Take home Technical screen Onsite Background check Offer
Interview formats
Coding Technical Behavioral

Before my interview, I didn't check Glassdoor, but I did afterward and found experiences similar to mine. The interview process involved one telephonic coding assignment that took 2-3 hours, followed by two face-to-face discussions about the coding. Then there were two managerial rounds and an HR round. I had already passed interviews at about 10 companies before interviewing at Ridecell, Pune. After the coding assignment, I spoke with an interviewer who was supposed to review my code. This interviewer seemed unfamiliar with Java 8 features I used, didn't understand the difference between design patterns or basic design concepts/principles. They were primarily interested in a working REST service, which I hadn't built. It was quite disappointing to be interviewed by someone lacking fundamental knowledge. The second technical face-to-face discussion wasn't hard; after clearing 10 other company interviews, the questions felt like a cakewalk. I'm confident in my performance and unaffected by any negative feedback from the interviewer. I strongly believe Ridecell, Pune might be using interviews to train their developers, given the interviewers' apparent lack of understanding. The Pune development center is about 1.5 years old. I hope Ridecell Pune's internal culture stays positive with good people in the coming years.

Confirmed questions6 questions
  • Coding assignment on Parking Spot.
  • Discuss Strategy vs Factory design patterns.
  • Write code to arrange Red and Blue balls in an array such that blue balls are on the left and red balls are on the right.
Ridecell logo
Ridecell

Software Engineer

Engineering

Entry Easy Positive experience No offer 5 rounds
Interview process
Take home Recruiter call Technical screen Onsite Presentation
Interview formats
Technical Coding Presentation Behavioral

first I had to finish an online assignment. After like 2 weeks, the recruiter reached out via email for a followup. Then, a recruiter phone screen with some basic questions. The onsite involved meeting the entire team, which was 4 people at the time. Each person had about 30 minutes for questions covering different areas. There was also a 45-minute whiteboarding session, a 3-hour coding challenge, and a 30-minute presentation.

Confirmed questions1 question
  • Can you explain how you structure your React components?

Ridecell Software Engineer Interview Questions

Quoted word for word from Ridecell interview reports.

Write code to find the maximum length palindrome in an array of characters.

Read reports

Write code to arrange Red and Blue balls in an array such that blue balls are on the left and red balls are on the right.

Read reports

How do you find a subset of integers within a larger integer?

Read reports

Could you build a REST API for a parking reservation web service?

Read report

Formats, difficulty and experience

Across all 18 Ridecell interview reports.

Interview formats

Technical 30.9%
Coding 27.3%
Behavioral 25.5%
Presentation 9.1%
System Design 5.5%

Interview difficulty

Easy 27.8%
Average 72.2%
Difficult 0%

Candidate experience

Positive 38.9%
Negative 61.1%