Atlassian interview notes, page 5 of 11

“The part that tripped me up was how persistent they were.” The rest of the author's notes on Machine Learning Engineer interview at Atlassian, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I sorted the array first which was the right instinct, but then I fumbled around trying to brute force placements before realizing binary search on the answer was the cleaner path.” The rest of the author's notes on Data Scientist interview at Atlassian, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had a decent story ready about a modeling approach I pushed back on, but the follow-ups got granular fast.” The rest of the author's notes on Machine Learning Engineer interview at Atlassian, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had a decent story ready but I spent too long on the problem setup and rushed the trade-offs section, which was probably what they actually cared about.” The rest of the author's notes on Machine Learning Engineer interview at Atlassian, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the data model which felt safe, users, roles, permissions, resources, the join tables.” The rest of the author's notes on Software Engineer interview at Atlassian, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I jumped straight to adjacency list because it's the first thing that comes to mind, and the interviewer let me run with it for a bit before asking how I'd handle fetching all descendants efficiently.” The rest of the author's notes on Software Engineer interview at Atlassian, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I'd done a version of LCA before so I thought I was fine.” The rest of the author's notes on Software Engineer interview at Atlassian, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew sliding window conceptually but freezing up on the dual-window constraint cost me time.” The rest of the author's notes on Data Scientist interview at Atlassian, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with full-file SHA-256 hashing and the interviewer immediately pushed back on what happens when two files differ by one line.” The rest of the author's notes on Software Engineer interview at Atlassian, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is the kind of question where I spent too long on diagnosis and ran out of time before getting to concrete solutions.” The rest of the author's notes on Product Manager interview at Atlassian, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.