HighRadius Software Engineer Interview Questions
& Process

So, HighRadius usually has like 2 to 3 interview rounds. First, there's an Online Assessment which is like a 1.5-hour test. It checks your aptitude, logical reasoning, and sometimes coding skills. Then you'll have a Technical Interview where they dive into your resume, projects, and ask questions specific to the role. For example, they might ask about Java concepts like object classes, garbage collection, or the difference between PreparedStatement and Statement. Lastly, there's an HR Interview which is pretty straightforward, covering your personal background, family, and preferences.

So, the interview at HighRadius was pretty structured and gave me a good feel for things. It kicked off with an online test for aptitude and technical problem-solving. After passing that, I had a technical interview where they asked about my past projects, my coding abilities, and how well I understood the key concepts for the job. A cool part was that some of us got a short internship to get a real feel for the work and projects. The last part was an HR round to check how well I communicate, adapt, and fit in with the team. All in all, it was a really organized process, a good chance to show off both my technical and people skills.

First, we had a pseudo-code writing part where no one really checked it. It included counting files in a directory, reversing a string, and something about hashmap implementation. Then came an analytical round, which was pretty silly, expecting people with 5+ years experience to calculate work done, and asking about upstream-downstream and east-west concepts. Finally, there was a presentation round where they give you a topic beforehand, like a dating app, followed by a totally pointless discussion. It felt like a sweatshop and a big show-off place. Almost everyone attended the weekend interviews. The panelists were totally confused about what they were looking for. They invited all these IITians and NITians and wasted their whole weekend. They called people with core development profiles but expected them to work on a completely different profile. It's a big NO for techies or anyone who has ever written a simple a+b=c program; you won't fit in.