DataVisor Software Engineer Interview Questions
& Process

It was a pretty unprofessional process. I went through 7 rounds of interviews, all of which involved medium-hard Leetcode problems. The interviewers were nice, but communication was tough sometimes because they were from China, and they often didn't have their cameras on. Sometimes there was loud background noise from their homes. HR was really slow to respond, taking over a week, and didn't give much info about the company, just scheduled interviews.

I had a technical phone interview and then seven onsite rounds. I met with engineers, a product manager, and the co-founders. They asked questions about algorithms and background knowledge. I struggled with a couple of questions initially, but the interviewers had a good discussion with me and helped me find the solutions. I had lunch with some engineers, which was nice because they were friendly. They showed me their new office, which was close to the old one. Overall, it was an inspiring and respectful experience.

After being introduced by a staffing firm, I had a phone interview. I was asked to introduce my work and experience. Then, I was given a coding question to solve within 10 minutes. I quickly came up with a feasible solution. When I asked if I could think further for an optimal solution, the interviewer told me to write the code for the feasible solution first. I did that, explained the logic, and discussed the computational complexity, which took about 20 minutes. I was then asked for a better solution. I spent another 5 minutes discussing it with the interviewer and presented a better idea. She seemed to understand and agree, but asked me to write the code for this better solution too. I refactored my old code and rewrote some major logic, which took about 8 minutes. I then offered to walk her through the refactored code again. She said time was up, as the interview was scheduled for 45 minutes and she wanted to leave a few minutes for her questions. Looking back, I realized I might have made a logic mistake in the refactoring, but couldn't fix it. It felt like a setup; if the goal was the best solution, we should have discussed the idea first. The interviewer wasn't very helpful, only checking minor details on the first solution.