FHLB Indianapolis logo

FHLB Indianapolis Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 10 interview experiences · FREE TO READ

1.8 Rounds average
Average Typical difficulty
70% Positive experience

Which role are you interviewing for?

6 roles · 10 reports

Candidate interview experiences

First-hand accounts from people who interviewed at FHLB Indianapolis.

Showing 4 of 10
FHLB Indianapolis logo
FHLB Indianapolis

Data Management

Analytics · more than a year ago

Mid Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding

First, you'll have an HR round, then 1 or 2 technical rounds. Expect questions about data management, Power BI, and SQL. HR should contact you within 2 weeks.

Confirmed questions4 questions
  • Can you explain DAX functions?
  • Tell me about your experience with Power BI.
  • Describe your data management skills.
FHLB Indianapolis logo
FHLB Indianapolis

.NET Developer

Engineering · more than a year ago

Entry Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

The job description and the interview questions are totally different. They're looking for someone who can build APIs, not someone with broad expertise. It seems like they're focused on a short-term objective.

Confirmed questions6 questions
  • Can you list all the .Net framework version numbers you've worked with?
  • Be ready for API security questions.
  • They are focusing on Microservices (API) development, so prepare for questions related to that.
FHLB Indianapolis logo
FHLB Indianapolis

Intern

Engineering

Intern Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral

So, first there was a phone screening, and then an on-site interview. The on-site was really something else. They had several intern openings and a ton of candidates for each. Like, 6 to 8 people were brought in for each spot. I was literally sitting at a table with 5 other people, all interviewing for the same gig. It felt like a huge waste of time because by the time it was my turn, the hiring manager didn't even seem that interested in me. She had this form to fill out and take notes, and she was rushing through it, asking me questions. She'd cut me off mid-answer to ask the next question so she could finish her form. Then she just rushed me out. It was super insulting. I figured they already had someone picked and just had to interview me, but didn't really want to hear what I had to say. I don't care about not getting the job, I just hate that they wasted my time. If you interview with them, definitely have backup plans, 'cause they bring in a lot of people for on-site interviews.

Confirmed questions1 question
  • Behavioral questions were asked during the on-site interview, which honestly felt like a joke. There were multiple intern positions available, and a large number of candidates were being interviewed for each. For every position, they brought in about 6-8 people. I was literally seated at a table with 5 other individuals, all waiting to interview for the same role. It felt like a complete waste of time because by the time it was my turn, the hiring manager didn't seem interested in me at all. She had a form to fill out and record the interview, and she was rushing to complete it while asking me questions. She actually interrupted my answers to ask the next question so she could finish this pointless form. Afterward, she hurried me out. It was the most insulting experience. I suspected they already had their preferred candidate and just had to give me a chance, but they didn't seem to care much about hearing my responses. I don't mind not getting the job, but I do mind that my time was wasted. If you have an interview with this company, make sure you have other options, because they do bring in many candidates for on-site interviews.
FHLB Indianapolis logo
FHLB Indianapolis

Quantitative Analyst

Analytics

Entry Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral

It was a pretty technical interview. We discussed the job role and the kind of work the team does. They tested my knowledge in Python, like libraries and coding approach. Also asked questions about masters courses, stochastic calculus, and risk management.

Confirmed questions1 question
  • Could you explain what Value at Risk is and how to make adjustments for different time periods?

FHLB Indianapolis Interview Questions

Quoted word for word from FHLB Indianapolis interview reports.

How would various events impact bond prices, or how would they move with interest rate changes?

Read reports

What are the key considerations when designing a microservices architecture?

Read reports

Could you explain what Value at Risk is and how to make adjustments for different time periods?

Read reports

Can you list all the .Net framework version numbers you've worked with?

Read report

What are your career aspirations for the next five years?

Read report

Formats, difficulty and experience

Across all 10 FHLB Indianapolis interview reports.

Interview formats

Behavioral 53.3%
Technical 26.7%
Coding 20%

Interview difficulty

Easy 20%
Average 50%
Difficult 30%

Candidate experience

Positive 70%
Negative 30%

Reports by job function

Analytics 2
Engineering 2
Other 2
Finance 2
HR 1
Operations 1