Process
I applied to two positions online and was contacted a week later to set up a call with a recruiter.
The call was a standard "get to know you" conversation. However, the recruiter wanted me to interview for a position on a different team than the ones I had applied for, believing it better fit my background. I decided that was acceptable, even though I genuinely want to move away from the tech stack I have the most experience with (C#/.NET).
I then had a technical screen over Zoom. I worked with an engineer to solve a straightforward problem. The engineer was friendly and helpful, and I felt the interview went very well. We had a good conversation afterward.
My recruiter contacted me about a week after the technical screen to say I had passed and the engineer enjoyed talking to me. However, they filled the position with another candidate. The recruiter mentioned they wanted to stay in contact as new positions would open up in the "next few weeks." I thanked her for the transparency and planned to wait a week or two before continuing to the next stage of the process.
Unfortunately, I haven't heard back from the recruiter in almost three months. I sent a follow-up email a few weeks after her message, inquiring about new roles, but it was ignored.
It seems rather inefficient for them to ghost someone who was already halfway through their recruiting process. I suspect the recruiter only contacted me because my background matched the tech stack for the alternate role they had me interview for, and they doubt my ability to learn different technologies. If that is the case, they need to better recognize how easily transferable baseline computer science/software development knowledge is to various tech stacks.
Questions
I was working through a pretty straightforward problem with another engineer. I liked it much more than your typical DS&A interviews. There's no need to know a bunch of random algorithms that you're never going to use in your day-to-day job.
Was this helpful?
Interview Statistics
The following metrics were computed from 60 interview experiences for the Atlassian Software Engineer role in United States.
Success Rate
Atlassian's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having mixed feelings for Atlassian's Software Engineer interview process in United States.
Atlassian Work Experiences
- 4.0Best job I've had. Not all sunshine and rainbows, thoughSoftware Engineer • Current EmployeeSydney, New South Wales, AustraliaJune 23, 2021Pros: Psychological safety is very important. People feel free to speak their minds even if it goes against project goals. You're encouraged to not save anything for yourself, and you don't have anything to be afraid of. People will hear your arguments! People really hold the company's values to heart, and I think they are one of the great culture-defining things the company has. Employee wellness feels like a top priority. Work-life balance, for me at least, has been great, and I feel free to regulate it as long as work is getting done. For me, I have never seen a blame game take place. If there is a problem, people only try to understand it to prevent it, not to find someone to blame. Through these challenging times (cliché much?), the thought Atlassian has been putting towards employees is truly heartwarming. I'm proud to work here. Work is technically engaging. You work with smart people, and you're exposed to excellence quite often. You will learn stuff here.Cons: Promotions are a HUGE con for me. As someone not interested in bureaucracy, I'm fortunate to be in a place in my life where I'm not in need of the extra responsibility & money attached to a promotion to the next level. Even though I fully believe I'd be qualified for the next position, the process to prove it is so grueling and cumbersome that I feel I'll never even want to partake in it. It will definitely be easier to look for a new job than to get promoted here. This gets brought up in every engineering all-hands, and the answer is always the same with different words. To paraphrase, the answer is always something like: "Yeah, I hear you, but we need to keep quality, and we believe it's fine like this, so nothing's gonna change." At least they are transparent about it. To get promoted, you have to build a paper trail (evidence, links, dates, testimonies, Slack conversations, Zoom recordings, pull request links, etc.) of performing at the next level for a whole year. It's always a fight, but if you ace the interview, you can still get hired into that level for one witty afternoon. I honestly feel that the paperwork for visas is way easier than this. I think although the need to keep the bar high is 100% true, there must be a better way. The company would be a 5-star from me if this was not an issue. If there was a 3.5-star option, I'd give it that (hence 4 stars) because when I learned this was the process, it broke my spirit and my drive to move up the ladder here. On the other hand, if you are someone that navigates office politics well, you'll not suffer this much, I reckon.
- 5.0Great place to workSoftware Engineer • Current EmployeeMountain View, California, United StatesNovember 16, 2022Pros: Awesome work culture. Good growth opportunities. Lot of flexibility.Cons: Nothing that I can think of.
- 1.0There is no such thing as "TEAM"Software Engineer • Current EmployeeFebruary 25, 2016Pros: Location is very good. It is in the heart of the CBD.Cons: Poor software engineering practices. Many projects are in big trouble because of high employee turnover. Sometimes we need to redesign whole projects from scratch. Recruiters are working very hard to find good engineers.
Atlassian Interview Questions
