Verifone Interview Experience for SDE | Off-Campus 2021
Interview Experience
I had an interview with VeriFone India Bangalore for the Software Development Engineer position (2021 Graduates). It was an off-campus opportunity, I applied through an em...
Full Details
I had an interview with VeriFone India Bangalore for the Software Development Engineer position (2021 Graduates). It was an off-campus opportunity, I applied through an employee referral. I got a call from HR within 10 days of applying regarding the interview process. The overall process was smooth and mainly focused on data structures and algorithms and core java concepts. Round 1(Online Assignment): 30 mins We have 30 mins to solve 30 questions. Basic aptitude and puzzles related questions. A very easy test you just need speed to clear this round. The cutoff for this round was 26/30. Round 2(Interview 1): 1hr 10mins The first round of interview begins with the introduction, first, he briefs his journey as a software developer at Verifone then he asked me to introduce myself. Then he briefs me regarding the whole interview process and the total number of rounds. He said there will be a total of 3 interview rounds (2 technical and 1 managerial) and still if they have any doubts regarding the candidature they can extend it to 4 rounds. After that interviewer moved on to a few coding questions while asking me to share my screen and open any IDE to code. The first question he asked was to Sort 0, 1, 2 array . At first told him an algorithm using simply counting 0s,1s,2s and then rearranging them. Time and space complexity for this is O(n). Then he asked me to think of an algorithm with O(1) space complexity. Finally, told him the 3 pointer approach having O(n) time and O(1) space complexity. Then he asked me to code this in JAVA and print the output for different test cases. Then he asked me a graph-related question. The question was if there are 4 files containing code let say A, B, C, D and there are dependencies like (A-->B, A-->C, A-->D, B-->C, C-->D, D-->B) here dependencies means we cannot load file A without loading file B, C, D. He asked me to come up the with the order in which we can load files there can be multiple answers. Then he asked me another question based on graphs I don't remember the exact question but the solution for this was DFS of the graph. He asked me to write code for it in JAVA. I used the iterator in the above question, so he asked me to tell the difference between for loop and iterator and write code for the same. Then he asked me to tell the difference between iterator, enumerations, and list iterator. Round 3(Interview 2): 55mins This round is more focused on core java concepts, but first, there was a discussion about projects mentioned on my resume. The interviewer asked me questions about multithreading, error handling, Collections. She also asked me questions about inheritance in java, abstraction concepts, etc. Round 4(Interview 3): 35 - 45 mins This is the managerial round where we had a discussion about the job, some behavioral questions were asked. 2 week later I got a call from HR that I got selected for the job.
About This Question
This is a candidate experience report from a verifone interview for a swe role during the recruiter round reported in 2025.
It covers the following topics: Graphs, Arrays, Graph .
Difficulty rating: Easy
More Verifone Interview Questions
About Verifone Interview Reports
This question was reported by a candidate who interviewed at Verifone. 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 Verifone are the higher-signal extractions to take from this report.
For broader preparation context, the Verifone 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 Verifone reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Verifone 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 Verifone 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.