In summary, "academics" should not waste their time here.
I was contacted by one of their recruiters based on my sysops background and experience. Over a period of a month, I had four telephone screening interviews/conversations. I was then invited to a series of face-to-face interviews (5 hours -- 6 sub-panels with a total of 8 people, plus an HR person).
The interviewers were nice, and there was nothing particularly difficult with the set of questions; all were very conversational. The range of topics included a recap of my background and experience, project and team management, operations & sys admin, Cloud, DevOps, networking, etc. So far, so good.
After a week, I was contacted with the news that although they considered me to be technically excellent, they were not going to proceed any further because my background was too "academic." I have published papers on system architectures & DevOps and have professionally worked on complex, large-scale distributed computing infrastructures.
Given that Workday was well aware of my "academic" background, I feel they wasted a good chunk of my time that I could have used productively elsewhere. There is also an inference that an "academic" is not capable of adjusting to a commercial environment. Personally, I always considered myself a professional sysadmin and managed my infrastructures accordingly.
How can you extract the top 10 occurring URLs and their return codes from a log file?
How would you scale this to multiple machines with terabytes of data?
How have you contributed to a project (of your choice)?
The following metrics were computed from 5 interview experiences for the Workday Devops Engineer role in Dublin, Ireland.
Workday's interview process for their Devops Engineer roles in Dublin, Ireland is extremely selective, failing the vast majority of engineers.
Candidates reported having negative feelings for Workday's Devops Engineer interview process in Dublin, Ireland.