Fiserv Software Engineer interviews reported by candidates typically combine a recruiter screen, resume-driven technical conversations on Java, Spring Boot, SQL and OOP, and a hiring-manager or HR round. Formats vary by team.
$110K
Avg. Base Comp
$140K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Fiserv Software Engineer interview as mostly resume-driven and fundamentals-heavy rather than puzzle-heavy. Several people were asked to walk through past projects, the decisions behind them, and in one case a real production problem and how they fixed it.
The technical content skews toward Java. Reports mention Java and OOP basics, REST concepts, Spring Boot scopes, and backend topics such as database locking and multithreading. Some panels mixed front end and back end, with Angular or JavaScript fundamentals alongside core Java. SQL also came up, including a SQL query in a round that also had a Python code question. A few candidates reported small coding exercises, such as reversing a string or returning the number with the highest frequency from a list. Others described no live coding at all.
Design appears in some processes. One candidate described a simple API design question and a live coding portion that leaned toward system design. Another got a practical question about choosing the best data type for storing large student data with the same name. Expect to explain tradeoffs from your own work.
Behavioral questions show up too: strengths and weaknesses, why you want the job, and STAR-format examples like dealing with a difficult personality on a team. Recruiter calls often cover background, tech stack, salary expectations and availability. One candidate was also questioned on specific legacy tools in the team's existing setup, so be ready to connect your experience to older stacks.
Outcomes in the reports are mixed. Some candidates mentioned communication gaps or a process that dragged on, so ask your recruiter about next steps early.
Synthesized from 19 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 Fiserv process.
The interview process at Fiserv was surprisingly conversational across both rounds. I started with a 15–30 minute phone screen that felt more like a casual discussion than a technical interrogation. The interviewer asked me to walk through my background and explain some of my key projects in detail. They seemed genuinely interested in understanding how I think and approach problems rather than quizzing me on data structures or algorithms.
The second round was with the hiring manager and lasted about an hour. Again, it was very conversational—no LeetCode questions, no whiteboarding, just a discussion about my experience and how I'd handled various situations. I found it refreshing compared to the intense technical rounds I'd prepared for. The whole vibe felt collaborative, and the interviewers were patient and let me fully explain my thoughts before moving forward. By the end, I felt like they were trying to get to know me as a person and teammate, not just testing my recall of CS fundamentals.
Prep tip from this candidate
Fiserv's process can vary significantly—some candidates get behavioral-focused rounds while others encounter technical depth questions on SQL and data structures. Prepare stories about handling complex projects and resolving ambiguous problems, but also brush up on fundamentals like joins, indexing, and type systems in case your interview leans technical.
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 Fiserv
Write a function n_frequent_words that returns the top N frequent words and their frequencies, and state its run-time
| Question | |
|---|---|
| Valid Anagram | |
| Target Indices | |
| Counting File Lines | |
| Offer Matching API Design | |
| Optimistic vs Pessimistic Locking | |
| Diagnosing Query Speed Degradation | |
| Converted Sessions | |
| Testing Constraints | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Merge Sorted Lists | |
| Total Spent on Products | |
| Top 3 Users | |
| String Shift | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Last Transaction | |
| Like Tracker | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a short recruiter call, sometimes about 15 minutes, covering background, tech stack, work eligibility, salary expectations and availability. Some describe it as a quick fit check rather than a technical filter. Have your salary expectations and a concise project summary ready.
Candidates typically report one or two technical conversations, some with a panel of several engineers. Topics include Java and OOP fundamentals, Spring Boot, REST, SQL, Angular or JavaScript, and backend concepts like multithreading. Coding is usually light, with examples such as string reversal and frequency counting. Several interviews started from the resume, so be ready to explain your project decisions.
Some candidates describe a design-oriented portion, such as a simple API design question or a live coding exercise that leaned toward system design. Practice explaining layers, responsibilities and data flow for systems you have built.
Candidates report conversations about fit, career background and behavioral examples, often in STAR style. Some also report an HR round. Prepare examples of teamwork, difficult colleagues and why you want the role.
