Fiserv Interview Questions
& Process

So, first you apply online and they look at your resume. If that looks good, you'll get a coding test, pretty standard stuff with easy-to-medium problems about arrays, hash maps, and strings. If you nail that, then you'll have one or two technical interviews where you gotta solve problems and talk through how you're doing it, plus some questions about working with others and stuff you've done before. Usually, there's a final round, might be behavioral or with the hiring manager, just to see if you're a good fit and how you communicate.

The interview process spanned a few rounds over five weeks, starting with a screening interview where the recruiter was late. Subsequent rounds involved the hiring manager, two team members, and concluded with an in-person interview with senior leadership. I was told a decision would be made by the end of the week following the final round, but there was no communication. A follow-up email to the recruiter a week later also went unanswered. This was, by far, the most unprofessional interview process I have experienced.

I had two virtual interviews. First, an HR interview to discuss my background and interest in the role, essentially checking for culture fit. Then, a technical interview with four engineers. They asked about high-level tech concepts and processes from my resume. One interviewer was really disruptive, constantly interrupting me and others, which seemed unprofessional. The company said they needed to hire fast, but then I was ghosted for weeks after the technical interview. It would have been polite to at least get a rejection email.

The interview process had a few parts. First, a quick chat with HR, either by phone or video, to talk about your background, skills, and why you want this job. They'll also ask about when you can start and what you're looking for salary-wise. Then, there was a technical interview, either with one person or a group, where they'll dig into stuff specific to the job. For roles like product or analysis, they asked about past work, how you get requirements, deal with people you work with, and tools like Jira, SQL, or Confluence. After that, I had to work through a case study or a scenario, like figuring out a process or getting requirements ready, which showed how I solve problems and if I understand the tech stuff. The last part was with the hiring manager, a longer talk about fitting in with the team, the company vibe, and what you want long-term. It wasn't so much about the technical details but more about how you work with others and your general outlook.