
Evive Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 25 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Evive.
Software Engineer
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.
- Were you able to work with the Movie Database API?
- Can you debug the problem I gave you?
Software Engineer
The interview process kicked off with a subjective online test covering practical Data Structures and Database management concepts. After that, 25 of us moved on to the second round, which was a 1.5-hour coding challenge with two problems: one on String Manipulation and another on the Relative degree of prime numbers. The third round, held on Google Hangouts, involved about 15 minutes of questions on C programming and Data Structures. The fourth and final round, also on Hangouts, was brief, around 7-10 minutes, and focused on Hashing. Unfortunately, I didn't make it past this round, though two candidates were selected for the final HR stage.
- Questions on Data Structures and C programming were asked.
- They focussed on practical applications of DS.
Programmer
The recruitment process had 5 phases. First, a Written Test with 10 questions covering OS, Probability, and C fundamentals, plus 3 coding problems requiring code and test cases. Second, a Face-to-Face (F2F) round discussing my projects and questions from the written test. Third, another F2F Technical interview with one coding question and queries on Data Structures and OS. Fourth, a Google Hangout interview, the most challenging, with OS, Discrete Math, and Hashing questions, where time was tight and pressure was high. Despite missing about 30% of answers, I advanced. Fifth, an HR round via Hangout asking general HR questions, my dream profile, why I want to join Evive, and how I'd improve in weak technical subjects. The whole process spanned 4 days.
- Can you tell me the drawbacks of the FIFO page replacement algorithm and suggest a superior alternative?
- Could you explain basic math concepts like the L-Hospital Rule and the Binomial Theorem?
Evive Software Engineer 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 are the time and space complexities involved in merge sort?”
Read reports →“Do you know where they find biriyani?”
Read reports →“Can you count the number of iterations in a program?”
Read reports →“Could you write a recursive program for merge sort?”
Read report →“Can you explain the differences and uses of Java interfaces and abstract classes?”
Read report →“Can you explain the merge sort algorithm?”
Read report →“Can you tell me the drawbacks of the FIFO page replacement algorithm and suggest a superior alternative?”
Read report →“Regarding Android projects, how are buttons added and what are their functionalities?”
Read report →Formats, difficulty and experience
Across all 25 Evive interview reports.