Rithum logo

Rithum Software Engineer Interview Questions
& Process

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

Based on 31 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
64.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Rithum.

Showing 3 of 31
Rithum logo
Rithum

Software Engineer

Engineering · nearly a year ago

Entry Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Coding Technical

It started with a basic recruiter chat. Then, a 60-minute Codility test with 2 questions of varying difficulty, which expires a week after you get the invite. Unfortunately, I got rejected after that. I wasn't told beforehand that Codility records you through webcam and your whole screen, which was quite off-putting. The recruiter didn't give any hints about the difficulty or topics for the Codility round, making it hard to prepare. The difficulty of the first Codility round doesn't really match the salary range, in my opinion. I've had easier questions in the first round at Google. Since I didn't practice DP, I had trouble with one question. My advice for candidates is to really grind LeetCode array and string patterns, plus some DP questions. My advice for Rithum is to provide at least some prep info, which is pretty standard nowadays, and to let candidates know about screen and webcam recording.

Confirmed questions3 questions
  • Find the longest unique substring
  • A dynamic programming question about maximum profit
  • A variation on a greedy algorithm problem
Rithum logo
Rithum

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience No offer 4 rounds
Interview process
Recruiter call Take home Onsite Technical screen
Interview formats
Coding Behavioral Technical

So recruiter reached out on LinkedIn, we had a quick call. Then I got a take home test, it had two parts: one was algorithms and the other was OOP. After they reviewed that, I interviewed with the hiring manager for cultural fit. Then there was a live coding session with an engineer. I guess I did okay, but my application is paused now because of hiring freezes in the US.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Rithum logo
Rithum

Software Engineer

Engineering

Mid Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding System Design

I had an HR call for about 20 minutes that involved soft skills questions. After that, there was a take-home assignment which took about 75 minutes and included two Codility questions in TypeScript. Finally, there was a live coding interview that lasted an hour and consisted of 2 Codility questions and a system design chat.

Confirmed questions4 questions
  • What soft skills do you possess?
  • Can you solve these two Codility questions in TypeScript?
  • Solve these two Codility questions.

Rithum Software Engineer Interview Questions

Quoted word for word from Rithum interview reports.

How would you design a database for words including their definitions, types, antonyms, and synonyms?

Read reports

What was your reasoning for using ConcurrentHashMap instead of HashMap?

Read report

How would you split a string based on specific criteria?

Read report

What could you use to decrease the number of classes you used?

Read report

Formats, difficulty and experience

Across all 31 Rithum interview reports.

Interview formats

Coding 37.3%
Technical 35.8%
Behavioral 19.4%
System Design 7.5%

Interview difficulty

Easy 12.9%
Average 64.5%
Difficult 22.6%

Candidate experience

Negative 22.6%
Positive 64.5%
Neutral 12.9%