Veriff logo

Veriff Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
28.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Veriff.

Showing 3 of 7
Veriff logo
Veriff

Senior Software Engineer

Engineering · nearly a year ago

Senior Easy Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

I sent in my application for this role on December 14th and then got an invite for the HR interview fairly quickly. After that, I didn't hear anything back, which was a bit strange given my past experiences.

Confirmed questions2 questions
  • Can you tell me about your background and what you've produced?
  • Could you describe your background and the production you have made?
Veriff logo
Veriff

Software Engineer

Engineering · a year ago

Mid Difficult Positive experience Accept offer 6 rounds
Interview process
Recruiter call Take home Presentation Technical screen Onsite Background check Offer
Interview formats
Technical Presentation Behavioral

Started with an initial screening, then a challenging take-home task that took about a week to prep for. After that, I had to present the take-home task. Then I interviewed with the engineering manager and later the co-founder. Lastly, an HR call to sort out the offer details.

Confirmed questions3 questions
  • Tell me about your technical field-specific knowledge.
  • How would you handle hypothetical questions about their use cases?
  • What are your thoughts on culture questions?
Veriff logo
Veriff

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Technical

Applied on LinkedIn. The interview process was pretty straightforward and well organized. There were 2 rounds: one with a recruiter and one with the team lead. After that, I got home assignments. This is where everything went sideways. First, the company doesn't give estimations for the tasks, so you have to estimate yourself, which often leads to spending too much time on the test assignment. Second, the stack they're hiring for and the stack in the home assignment could have nothing in common. Third, the person responsible for checking the results doesn't respect the objectives in the task description. Even a typo can be a reason for rejection. On the positive side, you do get feedback in the end. Overall, it was the worst experience I've had so far. I hope, at some point, the company will at least respect the candidate's time a bit more and look at the results more carefully.

Confirmed questions3 questions
  • Can you tell me about your past experience?
  • What's your experience with the tech stack?
  • What are your reasons for wanting to switch jobs?

Veriff Software Engineer Interview Questions

Quoted word for word from Veriff interview reports.

How would you handle hypothetical questions about their use cases?

Read reports

Can you tell me about your background and what you've produced?

Read report

How have you worked with people who aren't technical, and how do you decide what to work on first?

Read report

Tell me about your technical field-specific knowledge.

Read report

Formats, difficulty and experience

Across all 7 Veriff interview reports.

Interview formats

Technical 42.9%
Behavioral 35.7%
Coding 7.1%
Presentation 7.1%
Other 7.1%

Interview difficulty

Easy 28.6%
Average 57.1%
Difficult 14.3%

Candidate experience

Negative 71.4%
Positive 28.6%