I am describing my experience with the live coding interview.

This was the first of their six-step process.

I was given a service to implement that performed a relatively simple task, involving straightforward business logic.

My approach was to seek all necessary clarifications at the beginning to ensure that my implementation would require minimal changes.

After completing the first requirement, the second requirement necessitated a significant refactor and introduced a new concept that had no explicit requirement. Typically, introducing a new concept would include its own set of business use cases.

The third requirement followed in the same manner. I became somewhat confused with the refactoring process, but my interviewer helped me stay on track in solving the challenges that arose, such as refactoring previous tests.

Another minor point was perhaps understanding the interviewer due to a distinct foreign English accent.

At the end, I had the opportunity to ask questions, and the interviewer did his best to answer them.

All in all, it was a great experience, but perhaps unnecessary when hiring a senior engineer.

I see you have this method here. Is there a way that we can eliminate it?

Is this data structure thread-safe?