Chatham Financial logo

Chatham Financial Software Engineer Interview Questions
& Process

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

Based on 28 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
53.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Chatham Financial.

Showing 3 of 28
Chatham Financial logo
Chatham Financial

Software Developer

Engineering · more than a year ago

Entry Easy Negative experience No offer 7 rounds
Interview process
Recruiter call Technical screen Onsite Technical screen Onsite Onsite Onsite
Interview formats
Behavioral Technical Coding

This whole thing took about 3 weeks. It started with a 30 minute call with the recruiter. Then I had an online assessment that included a coding problem and one open-ended question. After that, I got a call for an interview with two engineers. If I did well, I would have had more interviews with more engineers. Then I had 3 more interviews, which was the final round, with two engineers each. The first of those was a mix of behavioral questions and leetcode problems. The last two were just behavioral. I think I did well in all of them, answering problems optimally and the interviewers seemed to like me. But after the final interviews, they ghosted me. It's normal to get ghosted when looking for jobs, but reaching the final round and not even getting a rejection email for closure was disappointing, especially since everything else went so well.

Confirmed questions1 question
  • Can you compare and contrast the waterfall and scrum methodologies?
Chatham Financial logo
Chatham Financial

Software Developer

Engineering · more than a year ago

Mid Difficult Positive experience No offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Technical Coding Behavioral Presentation

So, I had a phone screening first. Then, a video technical interview followed. After that, they invited me for an on-site day of interviews in Utah, and they covered all my travel expenses. The on-site part was supposed to be half a day but it was actually a full day, from 9:15 am to 4 pm. It included a Javascript coding problem, which you could also do in C# or Java, that took about an hour. Then there were four sessions with what seemed like team leaders, each involving a coding assessment and Q&A. The first session was about the Javascript code, and the others used a whiteboard for algorithmic, pseudo-code problems. They mentioned they aren't filling just one spot, suggesting they hire all suitable candidates. I was told I'd hear back in 1.5 to 2 weeks, but they let me know the week after that they weren't moving forward, citing a skills fit issue. Honestly, given the travel commitment, they should've done more of the interview process online, maybe be 90% sure about offering the job before flying someone out.

Confirmed questions1 question
  • Count Islands. Given a 2D array of "L" (land) and "W" (water), return the number of islands, ie contiguous pieces of land, found in the array. Land is connected N, S, E, and W, but not diagonally.
Chatham Financial logo
Chatham Financial

Software Engineer

Engineering · more than a year ago

Intern Average Positive experience Accept offer 5 rounds
Interview process
Technical screen Onsite Panel Background check Offer
Interview formats
Technical Coding Behavioral

The interview process kicked off with a technical video interview, involving two interviewers. They inquired about my past projects and the courses I was taking, along with some technical questions like explaining SQL joins and their different types, and the differences between SQL and NoSQL. After a three-week wait, I was invited for an onsite interview. The onsite part was a full-day affair. It started with a recruiter giving me a tour of the office and explaining the work culture. Following that, I had four consecutive interviews. Each of these was a 2-on-1 session where they first asked about my projects and previous work experience, then moved on to LeetCode problems to assess my coding skills. The LeetCode questions were all easy, and I had to write the code on a whiteboard. After two interviews, there was a lunch interview with a panel where we discussed company events, fun activities, and sports. The final interview was with a senior director, focusing on leadership qualities through numerous behavioral questions.

Confirmed questions6 questions
  • What's the best time to buy stock?
  • Can you traverse a tree in-order?
  • Explain SQL joins and their types.

Chatham Financial Software Engineer Interview Questions

Quoted word for word from Chatham Financial interview reports.

Write a function to calculate the maximum profit from buying and selling a stock once, given an array of its chronological stock prices.

Read reports

Can you write a program to check if a given string has valid parentheses?

Read reports

Given four jars of pills, three with 1-gram pills and one with 1.1-gram pills, and a scale that can only be used once, how would you identify the jar with the heavier pills?

Read reports

How would you develop an algorithm to count islands in a grid?

Read report

Formats, difficulty and experience

Across all 28 Chatham Financial interview reports.

Interview formats

Technical 33.3%
Coding 30.4%
Behavioral 26.1%
Other 5.8%
Presentation 2.9%

Interview difficulty

Easy 17.9%
Average 64.3%
Difficult 17.9%

Candidate experience

Negative 28.6%
Positive 53.6%
Neutral 17.9%