I applied through a recruiter. The process took 2 months. I interviewed at Workday (Dublín, Dublín) in Apr 2016
Interview
A long process that involved multiple calls from recruiter then a manager, an online uml test and finally an onsite interview with 3 separate people. I believe the process can be sped up at your request if you're in a rush.
During the onsite interviews they mainly discuss your experience and try to get a feel for whether you would be a good fit. They didn't ask me any of the usual technical interview questions like programming languages, algorithms or even basic object oriented concepts. It seems the main way they assess you technically is to explore your understanding of a system you have worked with before.
Standards are very high so you really need to be above average in every stage of the interview process. Overall a well run process and I wasn't left with any doubt at the end why I didn't get an offer.
Draw a system model diagram of a system you are familiar with? You need to know this inside out and be able to expand on how you would improve various aspects of it including scalability and security.
I applied through college or university. The process took 2 days. I interviewed at Workday in Feb 2016
Interview
I talked to a few recruiters at a career workshop they held in my college. They reached out a day later (via text), and scheduled an interview to meet with me on campus. The interview was one on one (with, I assume, my would-be manager), and lasted around 45 minutes.
Interview questions [1]
Question 1
The question concerned UML diagrams, and how I would label/organize the various classes in a company, and the relationships between them. There were no coding/algorithm questions.
I applied through college or university. The process took 4 weeks. I interviewed at Workday (Pleasanton, CA) in Feb 2016
Interview
Overall it was a comprehensive (a technical interview, a few psuedo technical interviews, and a lot of behavioral interviews) and positive experience. The technical interview shouldn't be that bad if you know how to design classes and basic OO and UML, but it can get tricky (I got REALLY stumped on one part). Of the 6-7 interviewers that interviewed you, I'd say a few of them were either overly serious or condescending. Some didn't even come prepared--they just wanted you to ask THEM questions. Eh I guess that's fine.
Interview questions [1]
Question 1
Design a Google Docs File Sharing Sytem using UML. You'll have to use an enumeration class, just saying.
Also, "tell me about yourself" and "why workday", and a lot of questions about OO stuff, like interfaces, abstract, and when to use them.
ALSO, some tricky but basic programming problems, too: how to reverse a String, etc