Real, anonymous reports from people who interviewed for Software Engineer at DataVisor, newest first and distilled into what to expect across the loop.
Get your personalized DataVisor Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter-style outreach, I ended up doing a short sequence of interviews—three rounds total—with two technical conversations and one behavioral slot. The process felt fairly standard and mostly “easy to medium” in difficulty. Interviewing in Chinese was part of the setup only because I could speak it, so the whole flow stayed in that language for me.
For the technical rounds, I ran into straightforward LeetCode-style questions. One round leaned into Java, where I had to work through a JSON-focused job idea using Java. SQL also came up a bit more broadly during the technical discussion; I wasn’t asked to crank out full SQL statements, but I still had to answer questions that probed my understanding of SQL-related concepts. The other technical round included additional coding, and overall it didn’t feel like I was drowning in anything impossibly hard.
5 months ago
Average Negative Canada
My process started with multiple stages that built up to a longer HR loop, but the core was still two technical rounds plus a behavioral-style discussion with HR. I had a phone screen earlier in the chain, then moved into technical interviews where the questions included easy LeetCode material along with an AI-coding component. What surprised me was how much I still needed to communicate clearly—less “type and hope” and more explaining my thinking.
After the technical rounds, I waited about three weeks to get a final decision. During that time, I didn’t just sit idle with silence; I eventually received a verbal offer, but it didn’t turn into a written one. The rest of the process ended with rejection even after that verbal step, and honestly that gap left me pretty disappointed.
10 months ago
Easy Negative Canada
I moved through the usual multi-round path: a phone screening, then a technical interview, with more rounds following only if I continued to pass. The…
> 1 year
Average Positive Canada
Early on, I got pulled into what felt like a “first interview” flow: a technical LeetCode-style prompt that matched an easy tier, followed by follow-u…
> 1 year
Average Negative Mountain View, CA
My interview sequence was unusually structured and felt more corporate than purely technical. I started with an initial phone screen, then moved into …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Rounds
The interview process typically consists of multiple rounds, starting with a phone screen followed by two technical interviews and a behavioral discussion. Some candidates experienced additional rounds, including manager conversations and take-home assignments, leading to a longer overall timeline.
Candidates encountered a mix of LeetCode-style coding questions, often categorized as easy to medium difficulty, with a focus on algorithms and data structures. Some reports mentioned the inclusion of SQL-related concepts and project-style requirements during the final stages.
LeetCodeAlgorithmsSQL
Communication & Collaboration
Effective communication during technical rounds was emphasized, with interviewers often encouraging candidates to explain their thought processes rather than simply providing answers. This collaborative approach was noted positively by some candidates.
CommunicationCollaborationExplaining thought process
Behavioral & Cultural Fit
Behavioral interviews focused on assessing cultural fit and alignment with the company's values, with questions often drawn from candidates' resumes and past experiences. The tone of these discussions was generally respectful and non-adversarial.
BehavioralCultural fitValues alignment
Outcome & Feedback
Candidates reported varied experiences with feedback and outcomes, with some feeling blindsided by abrupt rejections or lack of closure after interviews. The timeline for receiving decisions could also be lengthy, leading to frustration.
RejectionFeedbackDecision timeline
Language Considerations
Interviews could be conducted in Chinese if the candidate was proficient, which added a layer of complexity for some. This aspect was noted as a factor that could influence the overall experience.