Approached by a ServiceTitan recruiter on LinkedIn.

R1: 30-minute phone interview with a lead recruiter.

R2: HackerRank coding challenge (75 minutes). It was good. Easy problem.

R3: Pair programming session with a Senior Manager (1.5 hours). Asked to design a Collection type. Difficulty type: Average.

R4: Pair programming session with a Manager (1.5 hours). The problem was related to asynchronous programming with a concurrency level. It was average. I solved it on time, and then the interviewer asked me to write the unit tests. No unit test frameworks are supported by HackerRank. So, I asked about his expectations, and the interviewer told me to test manually. He said if he understood my test, then it's good. I wrote the tests, and they passed. Then he asked me to write a test to test the concurrency level. First, I was stuck, but a few minutes later, I proposed a POC. I also told him that I knew it was a bad way to test, but it was just for testing. If the POC works, then I will fix my tests. Fortunately, the POC worked. Then, he seemed happy. He then suggested a different way to test that. It was a hint. I discussed with him about that approach he proposed and finally wrote the test as he wanted, and it passed. We both were happy. Then he talked with me for 5 minutes about the size of their teams and the tech stack they use. I thought it went well.

But 4 days later, they sent me an email stating that I didn't pass the coding round. Nothing to say. Waste of time. I think their recruiters might need to fix some interview arrangements each month, otherwise, they will be out of work.

Weight-based ranking.

A typical LINQ problem. Used Select, OrderBy, and Limit.

Difficulty level: Easy