The first interviewer hinted that preparing for the technical interview would be very challenging, comparing it to getting ready for a space mission. However, when it came to the actual technical interview, the task was surprisingly simple, more like a basic school project.

Even though you showed deep knowledge, coded a perfect solution, followed good coding practices, thoroughly tested your code for all scenarios, and paid careful attention to concurrency issues, the technical recruiter still found a petty reason to reject you. Specifically, they thought you made generating a random string too complicated.

What made it more frustrating was that whenever you asked if you were on the right track or if your approach was what they were looking for, the recruiter always responded positively, which didn't provide useful feedback. Additionally, the recruiter would sometimes roll their eyes when your answer didn't meet their expectations.

The technical recruiter also seemed unhappy or disinterested, making them appear insensitive. This made me question the company's hiring process and what it says about their work environment. It's strange that a company known for high standards doesn't even use basic quality checks, like having someone else review decisions. And it doesn't make sense to conduct technical interviews one-on-one.

Implement a URL shortener.

General questions about how a HashMap works.