Pegasystems Software Engineer Interview Questions
& Process

The interview at Pega usually goes for a few rounds. You can expect technical, manager, and HR parts. The exact number of rounds and what they focus on can change, but generally, it's a mix of technical tests, questions about your behavior, and talks about your past work and where you want to go in your career.

A recruiter reached out about job ID 21632. She was helpful and explained the salary details, admitting they couldn't match my current pay, which I respected. Since I was open to a change and the Hyderabad office was close, I decided to proceed. The first round, a few days later, involved algorithmic puzzles, a simple linked list problem, discussions on time complexity, and some concurrency concepts. After that went well, a second technical round was set up. The HR said it was another technical interview, but it started with the interviewer asking about my reasons for switching jobs within a year. This chat lasted about five minutes. Then came a question about taking a better-paying job on monolithic apps versus microservices, leading to another ten minutes of conversation. After a few more questions, more suited for a director level, he finally seemed to remember it was a technical round and asked me to merge two sorted linked lists. I coded it in Notepad because he was against using an IDE. There might have been a missing parenthesis in a while loop. When I asked if he was sure it would run and was production-grade, suggesting we open an IDE to test it, he abruptly ended the interview, saying, 'Okay, I’m done. Do you have any questions?'

I applied for an associate system architect role on a low-code platform, but they were looking for only technical people for the role with a good package. The first round went well with a coding question and a couple of puzzle questions, and we had a general talk about me. I qualified for the second round but couldn't clear that round.