Federal Reserve Bank of Kansas City Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Federal Reserve Bank of Kansas City.
Federal Reserve Bank of Kansas City
Technical Lead
Lead Average Negative experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral
The interview was about two hours of unfocused grilling. The first hour was with technical folks who seemed extremely arrogant and focused on making me feel stupid. They gave zero emotional feedback and dismissed any good answers as unimportant, so it wasn't a good experience. The second hour was the usual 'what do you really want to do' type questions, also with no emotional cues or feedback. I think it's some interview technique they use.
Confirmed questions1 question
- Can you describe your ideal 'xxxx' job?
Federal Reserve Bank of Kansas City
Senior Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Phone screen Technical screen Onsite
Interview formats
Technical Coding
The recruiter was unprepared, which continued with this interview. Also, they use outdated tech and pay below market. Questions weren't vetted and had inaccuracies. I'd already done a first-round phone tech screen, but the second-round team didn't know. As the interview went on, it was clear expectations (duration, content, format, balance, and why I was chosen) wouldn't be met, making me less willing to continue. When I asked about the number of unplanned whiteboard questions expected, given the time left, technical limits, and video conferencing challenges, it led to an impasse. They said these questions represented daily work, which I found absurd for a remote role where you can use all resources. It felt like they expected me to do whatever they asked. That was it for me, so I decided to leave the interview and decline further engagement.
Confirmed questions1 question
- Can you whiteboard a Binary Search Algorithm in Java?
Federal Reserve Bank of Kansas City
Software Engineer
Entry Easy Positive experience Accept offer 2 rounds
Interview process
Recruiter call Onsite Background check Offer
Interview formats
Behavioral
I had an on campus interview that was about 30 minutes and was strictly behavioural questions. A few weeks later, I was invited to the bank for two more interviews, also behavioural. Then we had a tour of the bank, were served lunch, and then there was a Q&A. The whole thing took about 4 hours and was with about 40 other people applying for various full time and internship roles.
Confirmed questions2 questions
- Tell me about a challenging problem you encountered and how you solved it.
- How would you integrate yourself into an existing team you are assigned to?
Federal Reserve Bank of Kansas City Software Engineer Interview Questions
Quoted word for word from Federal Reserve Bank of Kansas City interview reports.
“What are the differences between a primary key and a foreign key?”
Read reports →“Can you whiteboard a Binary Search Algorithm in Java?”
Read reports →“Can you define enums and explain their use cases?”
Read reports →“Can you explain what a Linked List is?”
Read reports →“Could you describe polymorphism and inheritance?”
Read report →“And what about your least favorite course?”
Read report →“What things should a company provide to make employees feel included?”
Read report →“Were there API related questions on frameworks?”
Read report →“Which programming languages do you feel you are strongest in?”
Read report →Formats, difficulty and experience
Across all 12 Federal Reserve Bank of Kansas City interview reports.