Get tailored insights about working at RethinkDB in one quick step.
RethinkDB interview questions
based on 7 ratings - Updated Nov 23, 2021
Averageinterview difficulty
Mostly positiveinterview experience
How others got an interview
60%
Applied online
Applied online
20%
Other
Other
20%
Staffing Agency
Staffing Agency
Interview search
7 interviews
Viewing 1 - 5 of 7 Interviews
RethinkDB interviews FAQs
Glassdoor users rated their interview experience at RethinkDB as 57.1% positive with a difficulty rating score of 3 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Software/Systems Engineer Intern and Software Engineer rated their interviews as the hardest, whereas interviews for Customer Success Manager and Office Manager roles were rated as the easiest.
The hiring process at RethinkDB takes an average of 8 days when considering 7 user submitted interviews across all job titles. To compare, the average duration of hiring at similar companies like BlackRock, Inc. is 14 days, Fabricated Software, Inc. is 2 days, and Apple Inc. is 21 days. Candidates applying for Systems Engineering had the quickest hiring process (on average 2 days), whereas Software Engineer roles had the slowest hiring process (on average 12 days).
3 interviews.
Same person interviewed me.
Easy questions.
Very casual
Pleasant
Zoom interviews for all three interviews
Provided access before to the platform prior to the interview
Told me about he job
Did not provide a job description
I applied online. I interviewed at RethinkDB in Jan 2015
Interview
Found the job posting online and interested in what they were doing. One round of phone screens with 2 algorithm questions. Found rounds online interviews focused on data structures and algorithms
I applied online. The process took 1+ week. I interviewed at RethinkDB in Aug 2015
Interview
Early August. Found job posting through HackerNews, emailed them my resume and cover letter. They quickly got back to me. First round was 30-45 minutes of skyping, two programming questions. The first had to do with graph traversal, the second was calculating the sum of Manhattan distances between a certain number of points. I was then asked to optimize it.
The second round, a 2-hour coding challenge, was to write a calculator. Mine passed their test cases, but either wasn't good enough or I used poor coding practices because I was rejected.