Summary: Unprofessional and disorganized interview process, misaligned with communicated expectations. Would not recommend pursuing opportunities here. Process Overview: Initial Contact & Screening I was initially contacted by a recruiter and went through a Systems Design screening. This phase was reasonable; I was asked to design a web crawler and received fair feedback. Coding Interview Mismatch I received a preparation guide specifying the use of a local development environment with unit testing, debugging, and scaling. It was communicated that this would be an "open Internet" interview, showcasing problem-solving, resourcefulness, and scalability considerations. Reality: The interviewer disregarded the prep guidelines and insisted on CoderPad, where they had pre-typed the challenge. Challenge Details: The task was to implement an API rate limiter with specific constraints. I discussed various solutions (sliding window, tumbling window, token buckets, CRDT-based distributed options). The interviewer preferred a single-node solution, and I implemented a sliding window. Execution Issues and Misunderstandings Mismatch in Terminology: The interviewer was confused between "sliding window" and "tumbling window" concepts, labeling my solution inaccurately. Trade-off in Precision: They insisted on an O(1) solution without clarification on acceptable trade-offs, creating unnecessary confusion. Post-Interview Feedback & Outcome I followed up with the recruiter, citing the lack of alignment between interview expectations and reality. The recruiter acknowledged this misalignment but shared that the interviewer’s feedback was negative. Due to the disorganized approach and lack of professionalism, I withdrew from the process. Conclusion: Following my experience and additional insights into current culture concerns at Atlassian, I opted to discontinue the interview process, feeling this opportunity was not a good fit.