Software Applications Engineer applicants have rated the interview process at Workday with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 84% positive. To compare, the company-average is 55.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Applications Engineer roles take an average of 22 days to get hired, when considering 37 user submitted interviews for this role. To compare, the hiring process at Workday overall takes an average of 29 days.
Common stages of the interview process at Workday as a Software Applications Engineer according to 37 Glassdoor interviews include:
Phone interview: 31%
One on one interview: 26%
Presentation: 14%
Group panel interview: 11%
Background check: 7%
Skills test: 6%
IQ intelligence test: 1%
Other: 1%
Drug test: 1%
Personality test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Workday (Pleasanton, CA)
Interview
Applied online for an applications engineer role and within a few days the recruiter set up an initial phone screen with me. Nothing out of the ordinary on this phone call other than a brief question about an OOP example. Pretty straightforward.
About a week later was an hour long interview with the hiring manager for the given requisition. This was split into a behavioral and technical portion over a video chat. The behavioral portion was very conversational and pleasant. The technical portion was an OOP exercise using UML class diagrams. Basically given a UML diagram representing some system, find ways to improve it.
About a week later was a virtual onsite. This onsite consisted of a total 6 interviews, of which 2 were technical. Met various members of the team & organization. The behavioral interviews were standard questions, again geared in a conversational format. Of the two technical interviews, one was a shared screen UML class diagram exercise where given some requirements, design a system. The other technical interview was a coding round (unexpected, as other Glassdoor experiences indicated there wouldn't be any) about finding the longest distance to a leaf on a binary tree given some node.
Interview feedback was provided within 3 business days. Was told they went in a different direction based on technical needs, which wasn't a huge surprise since I hadn't used UML until I started prepping for this interview, and was certainly not expecting a coding question.
Overall, the process was good even though I didn't make it through. Big thanks to the recruiter for keeping me well updated and acting promptly for each subsequent interview step. Everyone I spoke to was really kind, and it made me appreciate the company's culture. However I did get the vibe that Workday recruits and puts together teams of people from very similar academic backgrounds, which certainly doesn't help with diversifying teams.
Interview questions [2]
Question 1
Design a UML class diagram for a college enrollment system
I applied online. The process took 3 weeks. I interviewed at Workday (Atlanta, GA)
Interview
1)Hiring Manager: Give a brief intro about company and a basic class diagram 2)Technical Interview: Asks for UML diagram, I am asked ridesharing app. Later there is a demo about their language
Interview questions [1]
Question 1
1)Hiring Manager: Give a brief intro about company and a basic class diagram 2)Technical Interview: Asks for UML diagram, I am asked ridesharing app. Later there is a demo about their language
Had multiple rounds of interviews. Technical was based on UMLs. Otherwise was mostly focused on behavioral. Recruiter was very responsive and kept informed on all steps of the interview process.
I applied online. The process took 3 weeks. I interviewed at Workday in Feb 2023
Interview
I first had a phone call with the recruiter, which was mostly about the company, the position, and my qualifications. Later, I had almost five interviews, which were mostly focused on behavioral questions, UML class diagrams (object-oriented programming, classes, attributes, and relationships), and improving the model (such as how to simplify existing relationships, minimize methods and attributes, and determine cardinality).