Atlassian principal engineer interview experience

I recently completed a 5-round interview process for a Principal Engineer role at Atlassian. While the early rounds (system design, values, leadership) were well-aligned with clear expectations and positive feedback, the later technical rounds revealed a mismatch between how problems were expanded during the interview and how solutions were evaluated afterward.

In one round, a design that passed all tests and used clean abstractions was evaluated as over-engineered, despite no upfront constraint against extensibility. In another, a streaming problem was progressively expanded (versioning, same timestamps, commit ID), and each extension was handled correctly—yet the evaluation focused more on not asking clarifying questions early than on adaptability or correctness.

This experience reinforced how, at senior levels, implicit expectations can outweigh explicit problem evolution, leading to contradictory evaluations. Clearer expectation-setting on both sides would make Principal-level interviews more consistent and fair.