Software Developer at UKG

How it went

What they would tell you

How to prepare

Their background

Round by round

1. 1

   Online Assessment60 min

   • Coding Challenge: Single algorithmic problem testing programming fundamentals
   • Database Query: SQL problem focusing on data manipulation and retrieval
   • Approximately 20 multiple-choice questions covering computer science concepts
2. 2

   Technical Assessment 160 min

   Started with scenario-based problems like implementing browser navigation using doubly linked lists and tab management with map + DLL approach (LRU-style). Discussed my projects focusing on JWT authentication, bcrypt implementation, and MongoDB vs RDBMS choice. Solved SQL join query for employee-department with null handling and explained Rotate Linked List problem approach without coding.

   • Rotate Linked List
3. 3

   Technical Assessment 260 min

   The second round was all about getting my hands dirty, metaphorically speaking. The interviewer wanted to see if I could actually build what I talked about. I had to walk them through creating a linked list from scratch, all the main functions like insert, delete, and search. From there, we took a deep dive into authentication. I explained the entire user journey with JWT, from the moment they log in to how their session is securely managed. We even got into the nitty-gritty of how a system can tell a 'buyer' from a 'seller' based on their token. The session ended with a classic but crucial topic: ACID properties in databases. I did my best to give real-world examples to show I didn't just memorize the acronym.

   • Linked list implementation
4. 4

   Director Interview60 min

   This felt like the boss level, an interview with a Director. It was a 60-minute marathon that tested the breadth and depth of my CS knowledge. We started way out in theoretical territory, discussing things like NP-Complete problems and the Traveling Salesman problem. He wasn't looking for a solution, just to see if I understood the concepts. Then we moved on to algorithms I use more often, like Dijkstra's, DFS, and BFS, and I had to defend why I'd choose one over the other in different scenarios. The rest of the time was a rapid-fire discussion on tech I've used: SQL query optimization, what Java Streams are good for, and my take on stateless components in React. The most interesting part was a debate on RDBMS vs. NoSQL, it felt like a real architectural design meeting.

   • Travelling Salesman Problem
   • Dijkstra's algorithm
   • DFS
   • BFS
5. 5

   HR30 min

   The final round was a welcome change of pace, a chat with HR. It was way more relaxed and felt like they genuinely wanted to know who I was beyond my resume. We talked about my family and what I do for fun. The interviewer asked what I knew about UKG, and I shared my understanding of their work in the HR tech space. When they asked about my preferred location, I was honest and said Pune felt like the right fit for me, both for my career and personal life. It was a short, 30-minute conversation, but it left me with a really positive feeling about the company culture.

What came up