Atlassian has a very vibrant developer community. The company brings together engineers from diverse backgrounds, creating an environment where collaboration and knowledge-sharing thrive.
Atlassian places a strong emphasis on inclusivity. Through various company-hosted events, I was able to interact with engineers from different teams, learning from their experiences and gaining valuable insights into different aspects of software development. These events helped with building networking-related relationships.
What I found particularly unique about Atlassian is its approach to development. Because the company specializes in collaborative software, the projects and development cycles are both dynamic and innovative.
While my experience at Atlassian was overwhelmingly positive, one challenge I encountered was a lack of clear project scope in my assigned work. At times, this made it difficult to fully understand the long-term impact of my contributions or how my tasks fit into the bigger picture. More structured project guidelines or clearer objectives could have helped.
That said, this was a minor drawback in an otherwise fantastic experience. The supportive work culture, engaging development projects, and strong sense of community more than made up for it, making Atlassian a great place to grow as a student and upcoming developer.
It was pretty chill. I had a behavioral interview followed by a technical one. The technical interview featured a standard LeetCode question focused on class creation. Specifically, it centered on a file system and the creation of helper functions.
I interviewed a bit over a year ago, so there may have been some changes since. The onsite interview is pretty standard: * Three technical interviews * A values interview * A manager interview The interview process was great, and I had a fan
Submitted application online via the career portal. After about a week of waiting, I was sent a link to complete an online coding challenge. I was given around two hours to answer approximately four questions.
It was pretty chill. I had a behavioral interview followed by a technical one. The technical interview featured a standard LeetCode question focused on class creation. Specifically, it centered on a file system and the creation of helper functions.
I interviewed a bit over a year ago, so there may have been some changes since. The onsite interview is pretty standard: * Three technical interviews * A values interview * A manager interview The interview process was great, and I had a fan
Submitted application online via the career portal. After about a week of waiting, I was sent a link to complete an online coding challenge. I was given around two hours to answer approximately four questions.