I was contacted by HR about a week after I applied. There was a short 15-minute phone screen to gauge my interest and talk about the role. We then scheduled a second interview for the following week.

The second interview was one hour with three software engineers (all senior or above), which made it more nerve-wracking, and I think that showed. It was a more conversational interview than I've had before; they didn't mind me asking questions during technical discussions or problems. There was only one coding challenge at the very end that was fairly simple.

I received an e-mail about a week later informing me that they decided on someone else for the position. I was very nervous in the interview and wasn't thinking clearly on some of the questions, so I can't blame anyone but myself. They were overall incredibly kind and welcoming, and it was the best interview process I've gone through so far.

What are your first steps when you're given a user story in an Agile workflow? What's your process?

How much experience have you had with the React Developer Tools for debugging? (This specific position was more front-end, so you might not have this.)

What is Test-driven Development (TDD)? Have you used it in the past?

What's your process for error handling? How do you identify errors and pinpoint their causes?

Java - what's an immutable object? What makes an object immutable?

What is a Singleton class?

Say that you've got 10 million integers and you need to count how many of each integer exists - would a List, Set, or Map be most efficient?

Following up on the last question, what is the time complexity to find a specific integer key-value pair in a Map?

Given two strings of equal length, write a function that determines if they are anagrams (that is, if one string can be rearranged to form the other string).