Envié una solicitud electrónica. El proceso duró 2 meses. Acudí a una entrevista en Atlassian (New York, NY) en sept 2023
Entrevista
I applied through the website and the process took approximately two months. First, I spoke with a recruiter. Then I did a technical screen over data structures via Zoom. The interviewer had an excellently written question and it was a very positive experience. Then I was transferred to another recruiter who scheduled the full loop and gave notes on what to expect for each round. On the day of the loop, there was an issue with the Zoom meeting and the meeting id had changed but did not update the Zoom invite. This comes into play later. First was the system design. Great interviewer and after the design we discussed scaling, reliability, database systems and overall design. Partway through the interviewer noticed that I missed one of the requirements so I added that to my design. I was not dinged for missing this item. The feedback on this round was that I focused on a REST API and a microservices architecture. I felt this feedback was completely fair. Next was the values. After waiting on the Zoom for 5 minutes I emailed the interviewer to mention the update to the meeting id. The interviewer jumped on shortly after and thanked me for letting them know This was a conversation where I was asked questions regarding past experiences. On this round I recommend just being open and honest. The feedback from this round was very positive. Now the code design round was where the experience fell apart for me. After waiting for 5 minutes on the call, I emailed the interviewer to mention the change to the meeting id. When he got on the Zoom he seemed very upset and perturbed that I had emailed him about the change. The question was ill-defined and when I asked, I was rebuffed with “Everything is there. I don’t care if you talk or not. Just code.” Frankly, I did not understand what I was building at first and the interviewer refused to elaborate. Afterwards he was very explicit in that I was not to email the next interviewer and he would take care of it. My personal impression was that he was irritated that I emailed him when he was late to the interview with the updated meeting id. This was an incredibly negative experience. The last time I had an interview that was so negative was about 10 years ago. Last was the leadership interview. This went well and I was asked primarily about my last project and we dove deeply into it. This was a positive experience and I received positive feedback. The day after the loop I received the No Hire result and I was relieved. If I had, by some miracle, received a Hire result, I am not sure I would have accepted. All I could think is that if 20% of their hand-picked interviewers were this terrible then this might be an awful place to work.
Preguntas de entrevista [3]
Pregunta 1
Data Structures - Implement a voting system with a constant stream of votes.
Code Design – Rate Limiter. Here is the exact question I received. Problem Title: Rate Limiter Problem Description: Imagine we are building an application that is used by many different customers. We want to avoid one customer being able to overload the system by sending too many requests, so we enforce a per-customer rate limit. The rate limit is defined as: “Each customer can make X requests per Y seconds” Assuming that customer ID is extracted somehow from the request, implement the following function. // Perform rate limiting logic for provided customer ID. Return true if the // request is allowed, and false if it is not. boolean rateLimit(int customerId)
Standard process for a platform engineer (SRR) role, around what you have completed. Completing a coding exam on data structures for this role is unusual though. Role seemed more for application development than SRE.
Preguntas de entrevista [1]
Pregunta 1
Coding exam around structures. Example of where you have encountered difficulties in role.
Coding task, algorithms. It was not very difficult, all worked. But probably was not as good as it should be. Interviewer was polite and professional, task was described, we had a chat about solution steps.
Preguntas de entrevista [1]
Pregunta 1
What is the computational complexity of solutions algorithm's?
Solicité el puesto a través de un captador. El proceso duró 2 meses. Acudí a una entrevista en Atlassian (Bengaluru) en sept 2025
Entrevista
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)
Preguntas de entrevista [1]
Pregunta 1
Design a Url Scrapping System for scrapping photos from urls. You are given a list of seed urls and then you need to expand to other sites from there