The interview process was long and involved multiple calls from a recruiter, then a manager, an online UML test, and finally an onsite interview with three separate people. I believe the process can be expedited if you are in a rush.
During the onsite interviews, they mainly discussed my experience and tried to gauge whether I would be a good fit. They didn't ask me any of the usual technical interview questions, such as those on programming languages, algorithms, or even basic object-oriented concepts. It seems their primary method of technical assessment is to explore your understanding of a system you have worked with previously.
Standards are very high, so you really need to be above average at every stage of the interview process. Overall, it was a well-run process, and I wasn't left with any doubt at the end as to why I didn't receive an offer.
Model a ticketing system.
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.
The following metrics were computed from 6 interview experiences for the Workday Applications Developer role in Dublin, Ireland.
Workday's interview process for their Applications Developer roles in Dublin, Ireland is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Workday's Applications Developer interview process in Dublin, Ireland.