ReviewTrackers Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 64 interview experiences · FREE TO READ
Which role are you interviewing for?
26 roles · 64 reportsCandidate interview experiences
First-hand accounts from people who interviewed at ReviewTrackers.
ReviewTrackers
Backend Software Engineer
Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Technical Behavioral
I first talked to the VP. Then I got a coding challenge to build a web service that scrapes reviews from a URL and had a week to do it. After I sent it back, there was a 2-hour session where two engineers and I did a code review and refactoring. Also, I had brief non-technical chats with two other engineers, another manager, and the VP again. Later that same day, I heard back that they weren't moving forward. The VP mentioned the engineers liked my solution for the coding challenge, but weren't too impressed with the code review part.
Confirmed questions1 question
- When the URL is invalid or missing, ensure your web service returns a 400 status code.
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
Salesforce Administrator
Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical
It was a bit disorganized with some mix-ups like lost emails and wrong appointments, but overall it was what I expected. I had an initial chat with HR, then met with some team members one-on-one. The manager let me know I was progressing, but then it took 3 weeks to hear back that the position was filled. While the disorganization was a bummer, the people were nice and the company seemed to have good reviews.
Confirmed questions4 questions
- Regarding the Salesforce admin role, could you detail your knowledge of specific objects?
- What has been your experience working with Salesforce flows?
- Can you tell me about your Apex experience?
ReviewTrackers
Office Manager
Mid Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Phone screen Take home Onsite Panel Background check Offer
Interview formats
Behavioral Other
I applied on the company website and a recruiter reached out a day or two later to set up a phone interview. It was a 30 minute call going over my resume. Then I moved on to a phone screen with the VP of Ops. This call was more in-depth, asking about past experiences and my reasons for leaving my current job. Next, I had a take-home assignment to check attention to detail and time management. After submitting it, I had an in-person meeting with the VP of Ops and the CFO, which was about 1.5 hours. The next day, I spoke with the CEO. After that, I was asked for 3 references. Then I got an offer!
Confirmed questions3 questions
- What are your reasons for wanting to leave your current employer?
- Describe your ideal job.
- Can you recall a time you felt unmotivated at work?
ReviewTrackers Interview Questions
Quoted word for word from ReviewTrackers interview reports.
“When the URL is invalid or missing, ensure your web service returns a 400 status code.”
Read reports →“Can you provide detailed instructions on how to make a peanut butter and jelly sandwich?”
Read reports →“What will the console log after this code runs (code not provided)?”
Read reports →“Could you build a web service to pull specific details from a webpage?”
Read reports →“What's the biggest thing people get wrong about you?”
Read report →“Could you explain the distinctions between a mock, stub, and spy?”
Read report →“Could you write code for a mock API endpoint?”
Read report →“Which is more critical, the discovery meeting or the closing?”
Read report →“In one word, how would your closest friends describe you?”
Read report →Formats, difficulty and experience
Across all 64 ReviewTrackers interview reports.