Trov Interview Questions
& Process

Applied online and got a quick response. Was asked to answer a couple of questions via email, which I did promptly. A few days later, they contacted me to set up an interview. I interviewed on Google Hangouts the next week and was told I'd hear back in a couple of weeks. It's been over a month now and I haven't heard anything. Sent several emails and still no response. I'm okay with not getting the job, but really unhappy with how this was handled.

The application had more questions than I'm used to, which I found a bit much at first. But as I went through the process, I actually liked having the time to think about and write out my answers instead of having to come up with them on the spot during a phone screen. Then there was a phone call with the Hiring Manager, which seemed like a casual chat to get to know each other and for them to tell me about the company. I'm not totally sure what they were assessing there. After that, I got a take-home coding exercise. They asked me for an estimated completion time, and I sent them a link to a code repository once I was done. Lastly, I had a technical interview over video call with two people for about an hour. It was a pretty typical technical interview with some questions and coding. What really stood out was seeing how the two interviewers interacted, which gave me a great sense of what it's like to work there.

The interview process included a phone screen, followed by a take-home project that took about 2-5 hours to complete. After that, there was an online technical interview and a final interview to check for fit. They used an online code-sharing tool for actual engineering questions, no tricks involved. The questions were pre-defined, and I had to fill in missing logic or fix existing bugs.

Started with a recruiter call, then a 30 min phone interview where they went over my resume and I got to ask questions about Trov from the lead DevOps Engineer. Finally, an in-person meeting with two people where I took a test. The questions were more discussion-based, not simple yes/no.