Giving back to the leetcode community.\nI gave 3 rounds of interview.\n\n\n**DS/Algo** - Given a company\'s hierarchy graph with Employees and departments, I had to find the closest department between a list of employees. Working solution was required and I had construct the dependency graph as well. The starting point was company which had multiple departments and in the deparments, there were multiple employees.\nI gave the Lowest Common Ancestor approach and ran the solution for multiple test cases. The verdict was NO Hire. The reasons provided from the HR -\na. No clarifying questions were asked.\nb. The edge cases like - if the employee didn\'t exist wasn\'t covered. (I had a discussion with the interviewer on this specifically and implemented the fail safe)\nc. Time complexity wasn\'t computed correctly.\nPS - To make the approach more efficient, I proposed to store the paths from the root to the deparments and just check which deparment the employee belongs to while getting the closest department. But the interviewer didn\'t let me discuss on this approach and kept insisting on making the LCA approach better without sheding any light on what exactly he felt the issue was.(space or time?)\nPlease write in the comments if you have a better solution.\n\n\n**HLD Round** - Atlassian Tags management.\nThe interviewer was a Principal engineer and maturely handled the interview. Asked the API design, DB schema, microservices and then moved on to discussion on scaled up system. He asked questions on which components can act as a bottleneck and how can they be scaled.\nThe verdict was positive.\n\n\n**LLD Round** - Mobile Snake system design\nI was a bit overwhelmed because i hadn\'t attempted this question before and there were multiple requirements that were needed to be implemented. Finally, the interviewer wanted to see the position of head and tail in the console. I gave a working solution and was able to run all the use cases which were asked.\n\n\nThe verdict was NO Hire. The reasons provided from the HR -\na. Unit Test cases were not written\nb. Exception handling wasn\'t done.\nc. corner cases weren\'t covered\n\n\nPS - I was proud of myself after implementing a running solution. But the HR feedback was absurd.\n\n\nWhat do you guys think?\nHope I will be able to help others planning to give Atlassian interviews.

Giving back to the leetcode community.\nI gave 3 rounds of interview.\n\n\nDS/Algo - Given a company\'s hierarchy graph with Employees and departments, I had to