Finacle (EdgeVerve) Software Engineer candidates commonly report an aptitude or coding screen followed by two to four interviews covering projects, Java/OOP, SQL, DSA, and HR-style communication.
$128K
Avg. Base Comp
$159K
Avg. Total Comp
2-4 rounds
Typical Rounds
3 months
Process Length
Finacle (EdgeVerve) Software Engineer interviews in these reports range from a single technical conversation to a broader campus-style process with an online assessment, technical discussion, and HR interview. Aptitude and coding preparation both matter. Reported assessments covered quantitative aptitude, logical reasoning, verbal ability, basic coding, and general problem-solving, although not every candidate encountered an assessment.
Technical discussions were often led by the candidate’s résumé and projects. Be ready to explain what you personally built, the technologies or datasets involved, and the reasoning behind implementation choices. Java and OOP appeared repeatedly, including strings, variables, encapsulation, and immutable objects. Candidates also reported SQL and DBMS questions covering joins, queries, database comparisons, and ACID properties. Other fundamentals included operating-system scheduling, arrays, linked lists, stacks, trees, graphs, traversal, and time complexity.
Coding difficulty varied. Some candidates wrote straightforward programs such as factorial or quadratic-root solutions, while another received several basic-to-medium data-structure questions, including adding numbers represented by linked lists. Practice explaining the logic aloud and checking complexity rather than only producing code.
HR conversations may test self-introduction, career goals, relocation, communication, and the ability to respond comfortably as topics change. The available reports lean toward entry-level or campus-style hiring, so use the recurring fundamentals as preparation priorities without assuming every stage will appear.
Synthesized from 18 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Finacle(Edgeverve) process.
The technical interview was about 45 minutes and was straightforward but broad. After a brief introduction, the interviewer went through my resume, projects, and internship work, asking me to explain what I had personally done and the datasets or technologies involved. Since I had listed MongoDB and MySQL, I was asked to compare them, so I would make sure you can defend every tool on your resume rather than only memorizing definitions.
The technical portion covered basic-to-medium data-structure problems along with core CS fundamentals. I was given three programming questions and asked to write a program for the prompt. One representative problem involved two linked lists whose nodes store integers: add the numbers represented by the lists and produce a third linked list containing the sum. The interviewer also checked fundamentals such as the differences between arrays and linked lists, time complexity for operations on arrays, linked lists, stacks, trees, and graphs, and traversal concepts including DFS and preorder. Beyond coding, I was asked about OS scheduling algorithms, an SQL query, DBMS concepts such as ACID properties, and OOP concepts.
The overall difficulty was manageable if your fundamentals are solid, but the breadth made it important to switch quickly between coding, CS theory, SQL, and resume discussion. I did not receive an offer. My main takeaway is to practice explaining linked-list logic aloud, revise OS scheduling and ACID properties, and be ready to compare any databases or frameworks you list on your resume.
Prep tip from this candidate
Practice implementing the linked-list addition problem, then revise operation complexities and traversals alongside OS scheduling, ACID properties, and a database comparison such as MongoDB versus MySQL if those tools appear on your resume.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Finacle(Edgeverve)
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| String Shift | |
| Customer Orders | |
| Comments Histogram | |
| Random SQL Sample | |
| Minimum Change | |
| Prime to N | |
| Upsell Transactions | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Bagging vs Boosting | |
| Raining in Seattle | |
| First Touch Attribution | |
| Maximum Profit | |
| Retailer Data Warehouse | |
| Job Recommendation | |
| Find the First Non-Repeating Character in a String | |
| Recurring Character | |
| Size of Joins | |
| Daily Retention Summary | |
| Last Transaction |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial online or campus assessment that may combine quantitative aptitude, logical reasoning, verbal or English questions, pseudocode, writing, and programming. Some reports instead describe a dedicated coding test, including timed DSA problems.
Where a coding round is used, candidates report basic programming tasks as well as more demanding arrays, linked-list, graph, tree, or dynamic-programming problems. Timed formats may require completing one of two problems or reaching substantial test-case coverage.
Candidates commonly report a resume-led technical discussion covering project contributions, Java or other listed languages, OOP, data structures, algorithms, SQL, DBMS, and OS fundamentals. Live coding or SQL writing may be included; the exact stack varies with the candidate background.
Some candidates report a second technical or managerial conversation. It may probe project architecture, technology choices, React or API knowledge, system design at a basic level, or the reasoning behind a coding solution.
Candidates report self-introductions, future plans, teamwork scenarios, academic or project background, and relocation questions. This conversation may be standalone or combined with a technical interview, and some candidates describe a fast pace.
