Real, anonymous reports from people who interviewed for Software Engineer at Roima Intelligence, newest first and distilled into what to expect across the loop.
Get your personalized Roima Intelligence Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My process was described to me as a sequence of three stages: an HR round for communication and cultural fit, then a technical round to evaluate skills and knowledge, and finally an offer for selected candidates. The overall framing was structured, and I understood early on that the technical portion would be the main checkpoint.
I didn’t end up with an offer, and I mainly remember the uncertainty around how each stage would be judged, since the process emphasis on stages was clear but the finer details of the actual questions weren’t described in depth. The experience felt more like it was going through the motions of a standardized flow than building a clear picture of how I performed technically.
6 months ago
Difficult Positive India
My first stage was an aptitude written test that also included coding-style questions, all on paper. I remember getting separate sets of questions: one paper that mixed MCQs with some basic coding, and then a second paper shortly after that. In that second paper, the DB-focused part stood out—there were database query questions to reason through, and the other items were more logic/pseudocode based, like producing event-log style outputs.
Once I cleared the written rounds, I moved into an HR conversation and then a technical interview. The technical part leaned into OOPs and SQL. I had to work through medium to harder questions built around Java and SQL thinking, and the coding expectation wasn’t trivial even though the interviews were described as structured.
9 months ago
Average Neutral Ahmedabad
My process felt like a typical three-stage campus flow, though it wasn’t the most pleasant. I started with a simple aptitude set, then I moved into a …
10 months ago
Difficult Negative Ahmedabad
My interview experience started with a written aptitude test and programming questions, and it quickly turned stressful in a way that felt unnecessary…
12 months ago
Average Neutral Ahmedabad
My technical portion felt chaotic and unnecessarily discouraging. In the session, it seemed like the presentation and the team’s communication weren’t…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Stages
The interview process typically consists of three stages: an initial written aptitude and coding test, followed by an HR conversation, and concluding with a technical interview. Candidates noted that the structure was clear but felt rigid and somewhat impersonal.
Three stagesHR roundTechnical interview
Written Aptitude & Coding Test
Candidates experienced a pen-and-paper written test that included multiple-choice questions, basic coding tasks, and database-related queries, which set the tone for the rest of the interview process. The written test was perceived as a significant hurdle, with many feeling it was more about endurance than skill assessment.
Written testMCQsCoding tasks
Technical Interview Focus
The technical interviews placed a strong emphasis on data structures and algorithms (DSA), SQL, and object-oriented programming (OOP) concepts, often requiring candidates to write code by hand. Many candidates felt the questions were more challenging than expected, particularly for entry-level roles.
DSASQLOOP
HR Conversation
The HR round generally focused on behavioral questions and cultural fit, with candidates reporting it as less stressful compared to the technical portion. However, some candidates felt that the HR discussions were more formalities rather than in-depth evaluations.
Behavioral questionsCultural fitHR round
Candidate Experience & Environment
Several candidates reported a stressful and unprofessional atmosphere during interviews, with instances of poor communication from interviewers and a lack of clarity in the evaluation process. This negatively impacted their overall impression of the company.
Candidates expressed that the expectations throughout the interview process were higher than initially described, particularly regarding technical knowledge and problem-solving skills. Many felt unprepared for the level of difficulty presented in the interviews.