Rithum logo

Rithum Interview Questions
& Process

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

Based on 90 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
58.9% Positive experience

Which role are you interviewing for?

30 roles · 90 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Rithum.

Showing 4 of 90
Rithum logo
Rithum

Analyst

Analytics · nearly a year ago

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

It started with a recruiter screen, then there were two more rounds with the hiring managers and team. They asked questions about analytical thinking, problem solving, and communication. The whole thing was pretty straightforward and professional.

Confirmed questions1 question
  • Could you describe a previous project you worked on that involved analytics?
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

Implementation Specialist

Operations · nearly a year ago

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Presentation Offer
Interview formats
Behavioral Technical Presentation

I applied and a few days later the senior recruiter emailed saying my skills were a good fit. Then these interviews happened: First, I talked with the senior recruiter who told me more about the company and then put me forward for the next step on the same call. Second, I had a 45-minute call with the hiring manager. They asked a bunch of competency questions and briefly explained the day-to-day stuff. Not much personal chat. Third, I had an hour call with the client success Director, who talked most of the time and gave more details on the day-to-day. I was then moved to the final round on the same call. Fourth and last, they sent me an API doc to build an API in POSTMAN to show I could use it, and then I had to give a presentation on my project plan. I did it all. The next day, they told me my presentation wasn't great and I answered some competency questions too long, so I was super close but didn't get the offer. I told the senior recruiter it was a bummer because of those two things and that candidates shouldn't spend hours of their own time preparing a presentation that would normally be done with internal teams. They said they'd pass it on. The role is still up. Hope this helps others.

Confirmed questions2 questions
  • Tell me about your experience with internal situations.
  • Tell me about your experience with client project questions.
Rithum logo
Rithum

Product Marketing Manager

Marketing · a year ago

Mid Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

The interview felt like a weird humiliation ritual. No job description was available, and they were still figuring out the role. The recruiter then mentioned the hiring manager wanted to discuss product marketing, but it turned into something else. The hiring manager asked about an initiative I led and interrupted me constantly, possibly to throw me off. The HM also used convoluted jargon instead of normal terms, like asking about 'defined customer cohorts informing targeting and personalization strategy' instead of 'target audiences,' again likely to throw me off. Because of the interruptions, I only got to tell one story and couldn't showcase my full range of skills. It seemed like a new HM doing a first hire and going on a power trip instead of finding the right person. This job market and candidate process is tough enough without this kind of unnecessary, humiliating experience. I'd end the interview if this happened again.

Confirmed questions2 questions
  • Describe an initiative you managed, including what went wrong and how you handled it.
  • Tell me about the specific customer groups that influence your approach to targeting and personalization.

Rithum 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

Could you separate a sentence based on spaces, handling some complexities?

Read report

What was your reasoning for using ConcurrentHashMap instead of HashMap?

Read report

How would you split a string based on specific criteria?

Read report

Can you describe how to troubleshoot network issues on EC2?

Read report

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

Read report

Formats, difficulty and experience

Across all 90 Rithum interview reports.

Interview formats

Behavioral 33.9%
Technical 30.1%
Coding 18.8%
Presentation 7.5%
System Design 3.8%

Interview difficulty

Easy 14.4%
Average 67.8%
Difficult 17.8%

Candidate experience

Neutral 16.7%
Negative 24.4%
Positive 58.9%

Reports by job function

Engineering 44
Sales 11
Operations 10
Marketing 6
Other 4
Consulting 4