W. Ray Wallace Interview Questions
& Process

It started with an aptitude test that included verbal MCQs to check grammar, vocabulary, comprehension, sentence correction, and logical reasoning. Then there were two technical rounds. The first one focused on basic technical knowledge and problem-solving in my field, likely with coding or technical questions. The second technical round was tougher, with more in-depth questions to assess advanced problem-solving, my project experience, and how I'd handle real-world scenarios.

I was rejected because I wasn't prepared and didn't know the topics they asked about, like databases, frameworks, and data models. If you prepare well, you can definitely pass. Good luck!

The interview was pretty thorough, covering a bunch of parts to check if I could code well, solve problems, and if I'd fit in. First, there were some initial checks and technical tests. After that, I had deeper chats with the team and people higher up. They kept me in the loop and got back to me fast, which was nice. Every step gave me a better idea of what the company cares about and what they're looking for. It was tough, but it was put together well, showing they really want to hire the best people. All in all, it was a good experience where I got to talk with people and see how they're building a solid team that matches their plans and ideas.

The process started with an Online Assessment on HackerRank, which had 2 questions and lasted 90 minutes. If you passed that, you'd get an email about interview dates and technical rounds. Then there were 3 technical rounds and 1 HR round. The technical rounds involved an introduction, a discussion about skills and tech stacks from your CV, questions about your projects (make sure you know them well), and a coding question on codeshare.io, usually from LeetCode easy-medium.