Reported pattern - GenC / GenC Next / Programmer Analyst
Source: consolidated from public student write-ups of Cognizant’s 2025 fresher hiring. Candidates are usually put through one funnel and mapped afterwards to GenC, GenC Next, GenC Pro or GenC Elevate based on performance, rather than applying to a track and sitting a different exam. Reported end-to-end timelines run to about a month, sometimes longer.
Round 1 - Communication assessment (Versant, ~60 minutes)
Voice-based English test on the AMCAT platform, and in several 2025 accounts it comes first, before aptitude - a reversal from older write-ups.
- Sections cover fluency, grammar, listening and speaking
- The audio-repetition portion is the part candidates flag: the clip plays once only
- Reported as genuinely eliminative, and strong communication scores matter most for the client-facing Elevate track
- Practical: quiet room, wired headset, no interruptions
Round 2 - Aptitude and reasoning (~80-90 minutes)
Also on AMCAT. Recent accounts describe a hybrid: a conventional aptitude block of roughly 30 questions followed by around four gamified reasoning sections.
- Candidates report that progressing through the gamified levels, not just answering correctly, is what strengthens the score
- Generic reasoning prep helps for the MCQ block; the gamified sections reward practising the specific formats
Round 3 - Technical assessment (~120 minutes)
This is the section that most surprises people, because it is not a pure DSA test. One detailed 2025 account reports three parts:
-
SQL - 2 questions: JOINs,
GROUP BY, aggregate functions -
Programming - 2 questions in C#, Java or Python: strings, arrays, sorting
-
Web development - 1 question: HTML/CSS, sometimes with JavaScript
Another candidate reports the same shape (2 Java problems, 2 SQL queries, 1 web question) and completing four of the five parts, skipping the JavaScript one.
Takeaway from the accounts: SQL and basic web are scored components, not optional extras.
Round 4 - Technical + HR interview
Reported as a combined round, sometimes with two interviewers and running long - one account describes a 90-minute session, others 30-45 minutes.
Technical ground reported:
-
OOP concepts - consistently the heaviest area, and interviewers reportedly want explanation in your own words rather than textbook definitions
-
DBMS and SQL
-
DSA fundamentals plus live coding. Reported problems are simple: finding common elements between two arrays, finding a repeated character in a string
-
Project discussion, in depth
A concrete failure mode worth knowing: one candidate was required to code in Java, understood the logic but was slow on Java syntax, could not switch to their stronger language (C++), and was rejected. Check which languages the interview permits, not just which the assessment permits.
HR portion (~10-15 minutes): described as short and conversational - why Cognizant, relocation, willingness to work in any technology, career goals. Reported as less probing than TCS and less formal than Infosys.
Key takeaways: Communication comes first and eliminates. The technical assessment spans SQL and web, not just DSA. OOPs and project depth carry the interview. Confirm the permitted language before the interview.