Solace interview questions

Initial screening is standard, but be prepared that their coding challenge does not utilize the same tech stack as what’s listed in the job. I explicitly asked the recruiter what the coding challenge was going to cover so that I could prepare appropriately, but was just told it was what was listed in their tech stack. I was coming over from a separate tech stack and was still given a chance, but I failed because I was given incorrect information and prepared for the wrong technologies. Either make your coding challenge the same tech stack as the company or make sure the candidates are aware of what it will cover.

The first interview was a one-hour coding session in a large repo. I’d recommend using a large monitor because the setup has four different panels open at once: the IDE, preview, instructions/explanation, and command line. The task itself was fairly manageable. However, communication afterward was slow. I did not hear back from the recruiter, so I followed up after a week and only then learned that I had passed. The second interview was scheduled three weeks later, so by that point I was already about a month into the process. This interview focused on implementing pagination. There were two interviewers, and they were great. They were easy to talk to, polite, and professional. That said, the task was demanding for a one-hour interview. I was expected to quickly understand a codebase I had never worked with, implement new functionality, and fix bugs in an unfamiliar environment, all while two people were watching. I do not necessarily blame them. Maybe they are looking for candidates who can move extremely quickly in that kind of setting. I was not able to complete the full pagination implementation within the hour. After the interview, communication was again an issue. I did not hear anything for a week, so I emailed the recruiter and did not get a response. About 3 days later, I received a rejection. So whole process took 6 weeks. Overall, I would say the technical interview experience itself was better than typical FAANG-style LeetCode interviews. The tasks were closer to real work, which I appreciated. However, the process still seemed to favor speed, pattern recognition, familiarity with the exact tech stack, and a bit of luck.