Evive Software Analytics Interview Experience | Set 1 (On-Campus)
Interview Experience
Evive Software Analytics visited our campus.Round 1:This was an online test. The test consisted of 17 descriptive questions on probability, permutations and combinations, ...
Full Details
Evive Software Analytics visited our campus.
Round 1 This was an online test. The test consisted of 17 descriptive questions on probability, permutations and combinations, binary trees, time complexity, C programming snippets, and aptitude. Test duration was 1 hour. The test was easy. Questions were mainly focused on probability and binary trees. 197 students appeared for the test. Only 6 were shortlisted. I was one among them:)
Round 2 This was a technical interview round on hangouts. They asked simple questions on Java. Some of them were: Your major is Electronics and Communication. How do you know C, C++, Java, Python, HTML, CSS, SQL? Was it a part of your curriculum? What are the four major concepts in Object Oriented Programming? Explain with an example for each one. Derive time complexity of binary search and merge sort. How do you implement stack and queue? What is the time complexity of the following program: for (i=0;i<n;i=i*3) { do something; } How will you change it to O(log N)? Some students had 2 technical rounds. But I had only one. 3 students were shortlisted for the
next round.
Round 3 This was an HR interview on phone. She asked standard questions: Tell me something about yourself Why do you want to continue your career in software even though you are from Electronics and Communication? What are your stressbusters? Do you share your problems with others? Why Evive? What do you know about us? If you get an offer how long will you stay with Evive? Only 2 students got offers from Evive.
About This Question
This is a candidate experience report from a evive software analytics interview for a swe role during the oa round reported in 2018.
It covers the following topics: Oop, Trees, Binary Search, Sql, Stack Queue, Sorting, Probability Stats, Queue, Stack .
Difficulty rating: Easy
More Evive Software Analytics Interview Questions
About Evive Software Analytics Interview Reports
This question was reported by a candidate who interviewed at Evive Software Analytics. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Evive Software Analytics are the higher-signal extractions to take from this report.
For broader preparation context, the Evive Software Analytics interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Evive Software Analytics reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Evive Software Analytics Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Evive Software Analytics reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.