The process took 6 days. I interviewed at Granicus (New Delhi)
Interview
Got a call from recruiter for initial screening.
Later week they sent a behavioral test link, which includes basic maths and behaviour related questions. And the end of assessment you will get the result based on the situational questions.
Ex 1) more often you socialize with the team
A. Agree
B. Disagree
C. Can't say
Based of 60 questions like this byrq decided whether you fit or not . The questions are not at all related to the position you applied. For a HR socialize is required and for an team manager.
Why the reason for a software engineer socializing is in top priority and most of the questions are not straight forward, some are diplomatic. You feel like wasting your 1 hour time. And the end you will get a result.
like others metioned thier experience here. Dnt waste your time on this. They will not reply and justify their hiring process. You will get automated mail stating that you are not behavioral fit for them.
I applied online. I interviewed at Granicus in Oct 2025
Interview
The Cognitive Assessment at Granicus is a brief but challenging online test designed to evaluate logical reasoning, problem-solving, and pattern recognition skills. It typically includes timed multiple-choice questions involving numerical reasoning, verbal logic, and abstract patterns. The test measures how quickly and accurately you process information, rather than specific technical knowledge. Most candidates find it fair but fast-paced, requiring strong focus and time management. It serves as an initial screening step to assess analytical thinking before moving forward to the technical interview rounds.
I applied online. The process took 1 week. I interviewed at Granicus (Bengaluru) in Aug 2024
Interview
The focus on logical thinking throughout the process was truly impressive. It encouraged clear reasoning and problem-solving, allowing for effective communication of ideas. Even the use of pseudocode was acceptable, which made it easier to convey the core logic without worrying about syntax. Additionally, both the low-level design (LLD) and high-level design (HLD) discussions were very well-structured and detailed. They provided a solid understanding of the system from both architectural and implementation perspectives, making the entire process smooth, efficient, and easy to follow.
