Atlassian interview questions

Had a great interview experience at Atlassian. The HR of company are friendly and responsive, interviewers are knowledgeable and positive during interview. I had a total of 6 rounds of interview 1. HR - HR just asks about your experience and check skills based fitment. 2. System Design - Question - Design a Url Scarping System. I was able to solve this. However the expectation is go deep and design the core Scrapping API. Which I was able to do after the interviewer insisted. So be ready to show case your API design skills, URL, Request, Response, Data Model etc. Also be ready to provide the tech stack along with tradeoffs. 3. Leadership and Craft - Lot of questions around delivery, project management, stakeholder management, mentoring etc. I did pretty well in this. 4. Values - This is about atlassian values, HR will tell you how to prepare for this. I did pretty well. 5. Data Structure - Last Hero Problem. In an F1 race find the person who has done fastest lap in all of race. I solved it using HashMap of racer and max lap time. Later on I sorted the map and gave the last lap hero. I made a silly mistake and my test cases were failing. Hence I did not make it. 5. LLD - I dont remember the question. It was around Most Popular content. I used HashMap for storing content and frequency (thumbs up/thumbs Down)

Some interviews were good experiences, but there was one with a Product Head who looked liked he really was being forced to interview, or was pre-determined to be intentionally rude. This was my PM craft mastery round. 1. It was clear he was working on something else and not paying attention - very discouraging to do your best in an interview. 2. He first asked me to pick a product we could talk about, I asked him if wanted one from my experience or a product i like, he explicitly confirmed it can be anything. Then I mentioned one I like and started explaining why, but he cut me off saying no I want you to pick one you have worked on. There after I got his confirmation before i deep dived into things, which he said is not needed - honestly i couldn't understand what he wanted to talk about. 3. I had to understand from him what he was evaluating - should we talk about designing a product or improving it? Kept the question so open ended and when I picked a path, it was not good enough - he wouldn't ask a specific question and yet get annoyed when I sought clarification. 4. After partially listening to what I was saying, he would rephrase what I said in the most trivialising manner as if to put down my achievements. There is one thing to think it, something completely else to say it out loud to a candidate in an ongoing interview. Poor interviewing skills for a product head in my opinion. Best of luck, but don't expect any feedback from recruiters after the interviews. They make you go through 4 rounds of interviews and inform you via generic email. If you reach out for feedback nobody responds to you.