ReviewTrackers Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at ReviewTrackers.
ReviewTrackers
Software Engineer
Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Behavioral Coding Technical
The hiring process was really straightforward. First, I had a one-on-one with the hiring manager. After that, I was given a take-home coding assignment. Finally, there was a two-hour interview session where I met several team members, someone from HR, and the VP. Everyone was really nice and welcoming, and they were quick to provide updates at every stage. The whole thing took about 3 weeks because it was around the winter holidays, but I'd guess it normally takes about 2 weeks or less.
Confirmed questions4 questions
- What programming languages have you used in the past?
- What qualities do you seek in a team environment?
- Could you write code for a mock API endpoint?
ReviewTrackers
Software Engineer
Entry Difficult Negative experience No offer 2 rounds
Interview process
Phone screen Take home
Interview formats
Technical Coding
It started with a phone screen, which I really enjoyed speaking with the SWE lead. So I thought this would be a great process. The next day I got a coding assessment with 3 days to complete it. I'm not happy because I was told to ask questions if needed, I had a couple of questions that were very reasonable. But I was ignored, which I found unprofessional. I don't know what that was about but I just assumed it wasn't the place for me.
Confirmed questions1 question
- Can you discuss your experience with software testing?
ReviewTrackers
Software Engineer
Mid Average Positive experience No offer 2 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Coding
I had a 30-minute call with the VP of Engineering. After that, I was given a code challenge to complete over a few days, which was then reviewed by an engineer. The engineer I spoke with was pretty cool and answered my questions, explaining the company's approach to problem-solving. He even gave me feedback on my code challenge. That was the end of the line for me, but it was a good experience, especially if you like Ruby. It was a fun challenge.
Confirmed questions1 question
- Could you build a web service for collecting reviews, following a given set of specifications?
ReviewTrackers Software Engineer Interview Questions
Quoted word for word from ReviewTrackers interview reports.
“What will the console log after this code runs (code not provided)?”
Read reports →“Could you write code for a mock API endpoint?”
Read reports →“What is your understanding of ReviewTrackers as a company?”
Read reports →“Could you build a web service for collecting reviews, following a given set of specifications?”
Read reports →“Explain how you would go about fixing a minor bug identified in your submitted code.”
Read report →“What have you learned recently?”
Read report →“What are your hobbies outside of work?”
Read report →“How do you approach learning new things?”
Read report →“Could you explain your decision to use mongoDB in a past project?”
Read report →Formats, difficulty and experience
Across all 13 ReviewTrackers interview reports.