I applied through LinkedIn for a relocation position and was contacted by a recruiter after one or two days.
The first step was an online Java test, which served as a screening. This test was composed of multiple-choice questions and coding. It wasn't easy, but it was fair.
After less than a day, the recruiter called me to tell me I had passed with good results. He even detailed the topics I had gotten wrong.
The next step was online coding using Skype. I received a partially working system, added it to my IDE, and for an hour, we engaged in TDD and pair programming while discussing the problems and how to solve them. I LOVED it!
Once again, after a day, the recruiter contacted me and asked how I felt. I received feedback again—a very detailed summary of pros and cons. I really liked the feedback idea; it was highly professional.
The third step I did not pass. I had an interview with a manager and a senior developer. They asked me about the system I am currently working on. I described it, but apparently, I didn't do very well.
After getting feedback for this interview, I understood what went wrong. Most of the parts, I simply didn't explain very well.
Overall, it was fun and interesting. The interviewers and recruiter were very professional. I LOVED their feedback system.
I had to create a tree traversal with given classes and interfaces.
It's not the usual tree we know of.
The code had some interfaces and classes, and I had to implement some parts in order to run in a specific traversal order.
It's a common ancestor of some kind of graph.
The following metrics were computed from 1 interview experience for the Atlassian Java Technical Architect - Integration role in Israel.
Atlassian's interview process for their Java Technical Architect - Integration roles in Israel is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Atlassian's Java Technical Architect - Integration interview process in Israel.