The technical interview felt robotic.

The interviewer seemed to have already decided on a specific approach to the problem. If a candidate didn't follow that exact approach, they were marked as failed.

However, there can be many valid approaches to the same problem.

I was asked to implement a Load Balancer with 10 back-end server addresses.

The requirements stated:

• If the number of addresses exceeds 10, throw an exception.
• If duplicate server addresses are provided, throw an exception.

My proposed approach was to implement the Load Balancer using a Strategy pattern. This would allow for easy extension with new load balancer types, ensure testability, adhere to SOLID principles, maintain loose coupling with the back-end IP address list, and result in well-organized code.

But the interviewer insisted on having everything within a single class, which I found quite unusual.

Implement a LoadBalancer in Java with 10 back-end server addresses.

If addresses exceed 10, throw an exception. If duplicate server addresses exist, throw an exception.