The process is painfully slow. I applied online and got a call next day from one of their recruiters. We scheduled a code test for the next week and she got back to me with good feedback the next day and told me to expect a second round of interviews. Didn't hear from them for a month, then scheduled a phone interview which was more to review some of my background with a team lead. An onsite round of interviews was scheduled 2 weeks after this. I had 4 onsite interviews and a tour of their headquarters, which is not quite Google but it is a great collaborative and creative environment.
It was one very technical interview with some OOP concept questions, whiteboard algorithms and different questions about what the output of a specific code would be. The other 3 interviews were one with the director of the department that was more personality, and 2 group interviews, one with the team leads and another one with the integration managers, both a combination of technical, personality and experience, mostly questions about past experiences.
I didn't feel any question was very hard. I would say the hardest part was the code test. They give you a console application with the main method complete and tell you what they expect back when it runs. You have to create all of the classes for it. They are looking for you to use your OOP concepts. I was just nervous between the time and having someone watching me code every single line.
The following metrics were computed from 48 interview experiences for the UKG Software Engineer role in United States.
UKG's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for UKG's Software Engineer interview process in United States.