Evive logo

Evive Interview Questions
& Process

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

Based on 62 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
54.8% Positive experience

Which role are you interviewing for?

17 roles · 62 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Evive.

Showing 4 of 62
Evive logo
Evive

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Take home
Interview formats
Coding Technical

The interview process was super straightforward. It started with basic DSA problems and problem-solving. Then there were coding rounds to check coding skills, plus an aptitude test with 5 different types of problems.

Confirmed questions6 questions
  • Questions about problem-solving basics, data structures, and algorithms.
  • Questions on problem solving, data structures, and algorithms.
  • Questions about basic data structure and algorithm problems.
Evive logo
Evive

Sales Executive

Sales · more than a year ago

Mid Average Positive experience Accept offer 7 rounds
Interview process
Recruiter call Background check Panel Offer
Interview formats
Behavioral Case Presentation

The hiring process took about a month. I talked to an external recruiter first, then the VP of HR. After that, I met with the Chief Revenue Officer. Then there were several panel interviews, where I met individually with the Solution Consultant, VP of Marketing Channels, a Director, and a future peer who is also a Sales Executive. That was the whole process.

Confirmed questions3 questions
  • What are your criteria for choosing a company?
  • Describe your typical sales process.
  • Can you detail a significant deal you've closed?
Evive logo
Evive

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral

The process was alright, though the Hiring Manager seemed a bit all over the place. It included a long session diving into my background. Not many tough questions were actually asked, but we talked about understanding and debugging issues, and how to get better at coding assessments. It seems like what you say doesn't really matter given some of the feedback about the Interviewer. There's even talk that this kind of attitude from Senior Staff could hurt the company long-term. After they told me the result, there was zero communication, and they didn't reply even when I reached out.

Confirmed questions2 questions
  • Were you able to work with the Movie Database API?
  • Can you debug the problem I gave you?
Evive logo
Evive

QA Engineer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 7 rounds
Interview process
Technical screen Technical screen Onsite Take home Technical screen Background check Offer
Interview formats
Technical Coding Presentation Behavioral

So the interview process started with a campus round which had a written test. The written test had a mix of algorithmic, basic programming and some analytics questions. Then, there was a rapid fire round for shortlisted candidates where they asked a tricky programming question. If you got it right, you were given another question, otherwise you were out. Those who passed this round then went for a PI, either individually or in pairs. This interview was quite long, over an hour. They started with basic programming questions, then moved to QA specific questions. I had to take a project I did in my studies, an inventory management system, and write all its test cases along with the development process in a standard format. After that, I was shortlisted again and given an online QA assignment. The next round was with the Bangalore team, focusing entirely on my QA knowledge, including tools like Selenium and various testing methodologies. The final round was an HR round with someone from Chicago, which also lasted about an hour. This round covered everything: technical preferences (likes/dislikes), hobbies, family, other interests. I also got to ask them questions about the company. They probed deeply into my answers, checking if I was genuine or how committed I am to tasks, using examples from my technical preferences or current projects. It was a really positive experience. I got my offer letter the very next day.

Confirmed questions2 questions
  • What is the time complexity of merge sort?
  • Can you outline all test case scenarios for checking if a number is odd or not?

Evive Interview Questions

Quoted word for word from Evive interview reports.

Can you derive a general formula to find the nth Fibonacci number?

Read reports

What is the time complexity of insertion sort and heap sort?

Read reports

Can you find the kth largest number from an unsorted list?

Read report

What are the time and space complexities involved in merge sort?

Read report

What's the difference between validation and verification?

Read report

What's the difference between an array and a linked list?

Read report

Formats, difficulty and experience

Across all 62 Evive interview reports.

Interview formats

Technical 38%
Behavioral 27.6%
Coding 23.3%
Other 5.5%
Presentation 3.1%

Interview difficulty

Easy 16.1%
Average 56.5%
Difficult 27.4%

Candidate experience

Positive 54.8%
Neutral 24.2%
Negative 21%

Reports by job function

Engineering 40
Analytics 7
Marketing 6
Sales 6
Product 1
Consulting 1