Interviewed at Sydney HQ. Contacted by recruited via Linkedin. 30min HR phone call. 1hour onsite coding interview. Users/Groups assignments. The day before they sent me pdf + code.zip (password protected) and at the site interviwer gave me the password. 3 tasks, the first one has multiple sub tasks. I was managed only fixed the first one with subtasks. Expectations are to fix them all. After the interview in the feedback there were something along the line: "a bit slow, not enough experience..." So for the future candidates, don't worry about your thinking process too much, just go ahead with the debugger and find the cause - much much faster. Since the project isn't very big it's easy to debug. They invited me to the next round, 1.5hour onsite, technical interview with two interviwers. Asked to describe a recent project, my problem was that I peaked the project by the size and complexity and it wasn't recent (finished 1.5 year ago), so some of the details about it I didn't remember at the interview. Then the interview continued to questions/answers about Java, design, architecture, scalability. I had wrong expectations about that interview, I thought it would mainly be about system design. But they asked me a lot of questions related to java, mem management, leaks - main causes, how to fix, deadlocks, thread dumps (how to read and generate), what would I fix in java, my second favourite language besides java and why. Good design of REST api etc. GC related, how it works etc. The third part of the interview was coding of thread pool (classic). The feedback what I received was that they didn't understand what my project was about, has a very shallow knowledge about java. Coding part was good. Conclusion: should have prepared more like a normal java developer interview for questions/answers section. The recent project should be well defined. Advise for the future candidates, ask for clarification something like: "does that answer your questions?"