Cognizant Software Engineer Interview Questions & Rounds
Cognizant GenC campus drive: communication and aptitude tests, then a technical assessment with SQL and coding questions, followed by interviews.
On this page
How to Crack Cognizant: The Software Engineer Interview, From Real Experiences
Last updated November 20, 2026 · 27 min read · For GenC, GenC Pro and GenC Next candidates, Digital Nurture trainees and 2026 AI-track applicants
Built by the Codinzhub team. This guide is built from Cognizant software engineer (GenC) interview experiences that candidates shared, including experiences and assessment questions on Codinzhub. The process changes by year, track, cluster and college, so treat this as a map, not a promise.
The 30-second version. Cognizant hires most freshers through GenC campus drives on Superset. You take a communication test and an aptitude test with puzzle games, usually from home, then a technical assessment in your skill cluster: usually 2 SQL and 2 coding questions, often with a small web task, in 120 minutes in most reports. Your score and certificates decide whether you are interviewed for GenC, GenC Pro or GenC Next. The interview is one technical round of usually 25 to 45 minutes, mostly on Superset, covering OOP, exceptions, SQL and short string or array programs, and ending with yes/no HR checks on relocation and shifts. Some GenC Next candidates get a second 30 to 40 minute interview. Results took 4 to 5 days to about 5 weeks. The habit that matters most: write clean code in your cluster language, saying your logic as you type.
What this guide is, and what it is not
This guide is built from 37 candidate records of Cognizant's entry-level software hiring: 7 experiences and 8 assessment question sets shared on Codinzhub, plus 22 public write-ups. It also draws on 3 official Cognizant sources. Most are from 2023 to 2026 Indian campus drives, across the GenC tracks, Digital Nurture training routes and the 2026 AI track.
It is:
- A map of the process, stage by stage, as candidates described it
- The question patterns that keep coming back, and the follow-ups to expect
- A six-week plan and practice problems matched to those patterns
It is not:
- A list of leaked questions or a promise of what you will be asked
- An official description of Cognizant's process
- An offer rate. Outcomes in candidate posts are self-reported and are not a statistical sample.
Important things to know before you start
These Cognizant-specific facts change how you should prepare.
Your cluster language is fixed. The skill cluster you pick on Superset (Java by default, C# or Python) sets the language for the technical assessment, and in 3 reports for the interview too. One 2025 interviewer refused C++ and the candidate was rejected after buggy Java. Practise writing it without an IDE's help.
The interview runs on Superset, sometimes with two interviewers. Superset, with a built-in code editor, appears in 10 of 15 reports naming a platform; in 8 reports one interviewer sat in the room and one joined online. Practise typing short programs in a plain online editor.
The HR checks are real filters. Relocation (22 of 26 candidates), shifts (15) and tech-stack flexibility (9) were asked at the end of most interviews. One 2024 report says answering No on the application meant no shortlist.
Round-by-round breakdown
Candidates described five stages: an application on Superset, two screening tests (communication, then aptitude with puzzle games), a technical assessment in their skill cluster, a technical interview ending with HR questions (plus a second interview for some GenC Next and Pro candidates), then an interim offer, a letter of intent and joining.
Stage 1: Application, where candidates applied
Every record comes from India, and most are campus hires. Applications ran through Superset, the placement portal used for these drives, in 9 reports: you fill a profile, upload marksheets, a resume and certificates, and pick a skill cluster.
| Channel | What candidates said |
|---|---|
| On-campus drive | The main channel. One 2023 candidate got the shortlist and test dates within two weeks of registering. |
| Pool or off-campus drive | One 2025 pool drive ran on AMCAT; one off-campus candidate waited about a month for the first test link. |
| Digital Nurture training routes | A qualifier test, 5 weeks to 2.5 months of training, then an in-person interview. |
Skill clusters. In 2025 drives you chose Java (the default), C# with SQL and web, or Python with cloud questions, and your coding language followed it. Reported eligibility: 60 percent in 10th, 12th and degree with no active backlog (2023), and above 6 CGPA for a 2024 cloud track.
What helped. Candidates credited a certification (Salesforce, cybersecurity, ServiceNow or cloud) for a GenC Pro interview, and choosing the cluster in their strongest language. One warned that applying twice cancels your first application.
Stage 2: Shortlisting, how candidates moved forward
Most drives ran two online screening tests before any coding, usually from home.
- Communication assessment. An automated spoken-English test: sentence repetition, listening comprehension, grammar and speaking on a topic. It ran 60 minutes in 5 of the 9 reports giving a length (others: 45 or about 30). Two reports said the audio plays only once. Reports disagree on whether it eliminates: three batches said no, a 2024 Digital Nurture route and a 2024 cloud track said you had to clear it, and one 2025 candidate said communication and aptitude scores were combined for the coding shortlist.
- Aptitude and gamified assessment. About 25 to 30 quantitative and logical questions (profit and loss, time and work, percentages, speed and distance), then 4 puzzle games such as the Deductive, Switch and Grid challenges, which get harder as you clear levels. It ran 80 minutes in 5 of the 8 reports giving a length. Two reports mention a cut-off; at one 2025 college, 204 of about 500 candidates cleared it.
- Application answers. One 2024 candidate warned that answering No to relocation or technology flexibility on the form meant no shortlist.
What candidates advised. Practise the games to reach high levels, manage time in the aptitude section, and use a quiet room with a headset for the communication test.
Stage 3: Technical assessment
There is no phone screen. GenC candidates take a proctored technical assessment in their skill cluster, and the score decides which track you are interviewed for. A separate 2026 AI track at premium campuses used its own coding and GenAI test.
Technical assessment (GenC skill clusters)
How it works. The test usually has 2 SQL and 2 coding questions in your cluster language (15 of 18 reports). Most add a small HTML, CSS and JavaScript task or web questions (11 of 18), and 6 reports had 10 MCQs on the cluster: Java topics for Java, cloud fundamentals for Python. In four 2025-26 reports it was written offline at the college. Partial credit counts: one candidate passed 7 of 10 test cases on a C# question and still reached GenC Next. One 2024 report says solving 3 of 5 questions meant GenC, 3 or 4 plus a certification meant a GenC Pro interview, and all 5 meant a GenC Next interview.
At a glance
- Length: 120 minutes in most reports (6 of 9); 90 minutes in 2; about 60 minutes in one 2025 cybersecurity-track test
- Questions: 2 SQL + 2 coding, plus a web task or 10 cluster MCQs
- What was asked: SQL joins, aggregates and date functions; easy-to-medium array and string programs; a small web edit
- Most common: SQL join queries written from a given schema (5 reports)
| Question | What it tests | Level |
|---|---|---|
| SQL join queries written from a given schema | SQL joins and aggregation | GenC, GenC Pro, GenC Next |
| Build or restyle a small page with HTML, CSS and JavaScript | Front-end basics | GenC, GenC Next |
| SQL queries using built-in date functions | SQL functions | GenC, GenC Next |
| Find the maximum number of consecutive ones | Array scan with a running count | GenC Next |
| Sum of numbers that appear consecutively exactly k times | Run-length counting | GenC Next |
| Print the frequency of each character in a string | Character counting | GenC Next |
OA questions shared on Codinzhub.
| Question | Drive | Topic |
|---|---|---|
| Maximum team size from start and end arrays (overlapping intervals) | Chandigarh University | Intervals |
Coding and GenAI assessment (2026 AI-track drives)
How it works. In June 2026 Cognizant announced an Ace Team programme that hires full-stack AI engineers. It officially tests data structures, prompt engineering, retrieval-augmented generation (RAG, where a model answers from documents you retrieve), agentic AI and front-end work. Forwarded official notices say the 2026 technical assessment runs in the HackerRank desktop app, webcam on, one attempt, with no AI tools such as ChatGPT. Codinzhub pages from IIT (BHU), IIT (ISM), IIT Guwahati and IIIT Allahabad, dated 26 October to 4 November 2026, show the format below; they do not name the track.
At a glance
- Length: Not reported
- Questions: 3 coding questions plus 15 MCQs on Python and GenAI (3 of 4 drives listing a pattern); IIIT Allahabad had 2 build tasks
- What was asked: DSA problems, React components, RAG and prompt-engineering tasks, GenAI MCQs
- Most common: No single repeated question
| Question | What it tests | Level |
|---|---|---|
| Build a RAG-based airport service chatbot with conversational context | RAG with chat history | Not reported |
| Build a timer application in React | React state and effects | Not reported |
| Birthday Records React component that sorts a list of people | React component plus sorting | Technical ACE |
| GenAI MCQs, e.g. which option explains hallucination and bias | GenAI concepts | Technical ACE |
| Minimum Password Changes | Not reported | Technical ACE |
| RAG implementation from an answer string and a prompt string | RAG | Not reported |
OA questions shared on Codinzhub.
| Question | Drive | Topic |
|---|---|---|
| Build a RAG-based airport service chatbot | IIIT Allahabad | GenAI |
| Birthday Records React component | Technical ACE round | Front-end |
| Fewest changes to make a string periodic and a palindrome | IIT Guwahati | Strings |
| Beautiful Graph | IIT (ISM) Dhanbad | Graphs |
| Meeting Room | IIT (BHU) Varanasi | Not reported |
| Palindrome-based coding plus a prompt-engineering question | DTU Delhi | Strings, GenAI |
See every assessment question in the question bank.
Stage 4: The interview loop
For most candidates the loop is one technical interview that ends with HR questions, usually 25 to 45 minutes long (15 of 18 reports), on Superset in 10 of 15 reports naming a platform. You often join from your college or a Cognizant office. Some GenC Next and GenC Pro candidates had a second interview weeks later.
What a 30-minute technical interview looks like
| Time | What usually happens | What to do |
|---|---|---|
| 0–3 min | Self-introduction, with resume interruptions | Keep it to 90 seconds; end on your best project. |
| 3–10 min | Project and resume deep dive: role, stack, challenges, certifications | Explain one challenge and how you fixed it. |
| 10–18 min | 1 or 2 short programs typed on the platform in your cluster language | Say the logic first; expect "now without built-ins". |
| 18–27 min | OOP, Java or Python, and SQL theory; often a query | Give a one-line definition and a real-world example. |
| 27–30 min | Yes/no HR checks: relocation, shifts, tech stack; your questions | Answer plainly and have one question ready. |
Seven reports describe this order; one interviewer asked the HR checks first.
Technical interview (technical plus HR)
At a glance
- Length: usually 25 to 45 minutes (15 of 18); 50 to 90 minutes in 3 reports, including a 90-minute hybrid interview with 4 coding problems in a 2025 GenC Next pool drive
- Questions: 1 to 3 short coding programs plus OOP, Java or Python, and SQL theory, ending with HR checks
- What was asked: OOP pillars, exception handling, SQL joins and normalization, easy string and array programs, projects
- Most common: Explain the OOP pillars with real-world examples (12 of 28 candidates)
You code in your cluster language: one 2025 interviewer refused C++ and rejected a candidate who could not write clean Java. Questions followed the resume and Superset profile in 4 reports, and track topics (cybersecurity, Salesforce, React and .NET) in 4.
| Question | Follow-up | Level |
|---|---|---|
| Explain the OOP pillars with real-world examples | Polymorphism in detail; how OOP applies in your project | GenC, GenC Elevate, GenC Pro, GenC Next |
| Walk through your project: your role, tech stack and challenges | Challenges you faced and how you solved them | GenC, GenC Next, JavaFSE |
| Exception handling: checked vs unchecked, try-catch-finally, the hierarchy | How many exceptions are there in Java? | GenC, GenC Elevate, GenC Next, JavaFSE |
| Normalization and the normal forms | Not reported | GenC Elevate, GenC Next |
| Types of SQL joins, then left vs inner and self join | Left vs left outer join | GenC, GenC Pro, GenC Next |
| Abstract class vs interface, and when to use which | Not reported | GenC, GenC Elevate, GenC Next |
| Reverse a string, then again with a variation | Do it in one line, or with two pointers | GenC |
| What is an index, and what types of indexing exist? | Not reported | GenC, GenC Next |
Second technical interview (GenC Next and Pro)
At a glance
- Length: 30 to 40 minutes (2 reports)
- Questions: 1 or 2 coding programs plus Java, SQL or framework theory
- What was asked: strings, binary search, collections, Spring Boot and REST, JavaScript basics
- Most common: No single repeated question
Only two 2025 reports describe this round, both online through Superset; in one it came about three weeks after the first interview, only for candidates who did well in the assessment.
| Question | Follow-up | Level |
|---|---|---|
| Square root of a number using binary search | Not reported | GenC Next |
| Reverse a string with StringBuilder, then with a loop | Re-implement using a loop | GenC Next |
| Remove special characters from a user-input string | Not reported | GenC Next |
| SQL: find persons whose name contains 'a' | Not reported | GenC Next |
| Spring vs Spring Boot, annotations and REST APIs | Not reported | GenC Next |
| Collections: overview, HashMap use, ArrayList vs LinkedList, wrapper classes | Not reported | GenC Next |
| Can constructors be overloaded? | Not reported | GenC Next |
| JavaScript: let vs var, and what NaN is | Not reported | GenC Next |
HR questions
At a glance
- Length: a few minutes at the end of the technical interview; a separate 5 to 10 minute HR round in one 2023 report
- Questions: Not reported as a count
- Themes: relocation, shifts, tech-stack flexibility, joining date; occasionally strengths, teamwork and client scenarios
This is usually a short block of yes/no checks; one 2025 GenC Next candidate said there were no situational questions at all. It still filters: one interviewer asked these checks first "to make sure it will be worth interviewing".
Reported questions.
- Are you willing to relocate? (22 of 26 candidates)
- Are you comfortable with shifts, including night shifts? (15 of 26)
- Are you open to any technology stack or role? (9 of 26), then which technology you would not want
- Do you have any questions for us? (8 of 26)
- Rate yourself in Java, SQL or coding, then questions pitched to your rating (4 of 26)
- Can you join by a given date, or immediately? (3 of 26)
- Tell me about your hometown, school or campus life (3 of 26)
- Strengths and weaknesses, then how you will work with that weakness (2 of 26)
- If a project needs a technology you do not know, how will you manage? (2 of 26)
Stage 5: Results, letter of intent and joining
Result. There is no hiring committee or team match in the data. Results reach your placement office or show on Superset, where an "Interim Offer" status meant selection in the reports that mention it. Results came 4 to 5 days after the interview in one 2025 drive, about a month later in 3 reports, and about 5 weeks later in 2. End to end, five reports ran from about 6 weeks to about 4.5 months.
Track allotment. In one 2025 drive, GenC Pro and GenC Next lists came 2 to 3 days after the GenC offers, based on total scores, and candidates not moved up kept the GenC offer.
Offer and joining. A letter of intent followed the result by 1 to 3 weeks in two reports, and two reports describe an internship before joining. Cognizant's careers site says onboarding happens in batches, so accepting an offer does not mean joining right away.
Pay (candidate-reported). GenC about 4 LPA, GenC Pro about 5.4 LPA, GenC Next about 6.75 LPA, consistent across 6 reports from 2024 to 2026.
The Codinzhub Next-Round Playbook
Candidates who moved forward chose the right cluster, coded cleanly in it, and answered the HR checks plainly.
To get past application and shortlisting
- Fill every Superset profile section and upload certificates; in 2024-25 reports these and your scores decided the track.
- Choose the cluster in your strongest language. One candidate said friends who picked at random regretted it.
- In the puzzle games, push for higher levels; two reports said the score depends on how far you get.
To get past the technical assessment
- Bank the SQL first: join queries from a schema were the most common question.
- Submit partial solutions. One candidate passed 7 of 10 test cases on one question and still reached GenC Next.
- For the 2026 AI track, expect a proctored HackerRank test with no AI tools.
To get past the technical interview
- Code in your cluster language without help. One 2025 candidate was refused C++ and rejected.
- Say the logic before you type, then expect a variation: "now in one line", "now with a loop".
- Answer theory with a definition plus an example; the OOP pillars came up for 12 of 28 candidates.
To get past the second technical interview
- On the GenC Next path, revise Java collections (asked in one report of this round) and Spring Boot, annotations and REST (asked in the other).
- Expect a short algorithm with an efficient answer, such as a square root by binary search, and clear explanation over speed (one report).
To get past the HR questions
- Decide on relocation, shifts and tech-stack flexibility beforehand; relocation came up for 22 of 26 candidates.
- Give an honest self-rating; in 4 reports the questions followed it.
To get through results and joining
- Watch Superset: "Interim Offer" meant selection, and a letter of intent followed weeks later in two reports.
- Plan for a wait of 4 to 5 days to about 5 weeks for results, then batch onboarding.
How the loop differs by level
Every record is an entry-level hire, so "level" means the GenC track you are allotted. Assessments are shared; interview depth and domain questions change. No track had a system design round.
| Track | What candidates describe |
|---|---|
| GenC (Programmer Analyst Trainee) | Screening tests, the cluster assessment, then one technical + HR interview of 25 to 50 minutes in these reports (one undated report said 10 to 20). Examples: reverse your name after removing spaces, remove duplicates from a list, set vs tuple. Reported pay about 4 LPA. Based on 9 reports. |
| GenC Elevate (2022-23 name) | Chosen at registration; Elevate took a technical test (2 SQL and 3 Java questions in one report) where GenC took aptitude only, then one 27 to 35 minute interview on OOP, Fibonacci, palindrome and normalization. Based on 2 reports. |
| GenC Pro (certification or domain tracks) | Same assessments, then a 30 to 45 minute interview weighted to the domain: cybersecurity, Salesforce or cloud. A certificate helped candidates reach it. Reported pay about 5.4 LPA. Based on 5 reports. |
| GenC Next (Programmer Analyst) | Needs a top assessment score. First interview covers the same ground (second highest salary, normalization, final vs finally vs finalize); two 2025 reports add a 30 to 40 minute second interview with binary search, collections, Spring Boot and REST. Reported pay about 6.75 LPA. Based on 9 reports. |
| Digital Nurture and FSE training routes | A qualifier test, 5 weeks to 2.5 months of training, then a 35 to 60 minute in-person interview on the trained stack (Salesforce; .NET with React; Java full-stack). Based on 4 reports. |
| 2026 AI track (Ace Team, Technical ACE) | Official: communication, aptitude and HackerRank technical assessments, then an in-person interview; a candidate mapped to Senior Associate and not selected is checked for Associate in the same interview. Codinzhub pages show coding, GenAI MCQs, React and RAG tasks. Interview questions: Not reported. |
Most-asked topics
Across 36 reports that described a technical assessment or interview, questions concentrated in a few topics. Classic DSA is rare: GenC questions are definitions and short programs, except in the 2026 AI-track assessment.
| Topic | What it means | Seen in | Reported examples |
|---|---|---|---|
| OOP and core Java or Python theory | Pillars, exceptions, keywords and collections | 20 of 36 reports | Explain the OOP pillars with real-world examples; abstract class vs interface; final vs finally vs finalize |
| Projects and track topics | Your projects, plus your track's subject | 18 of 36 reports | Walk through your project; cloud service models; phishing and penetration testing |
| SQL queries and DBMS theory | Writing joins and aggregates, plus keys, normalization and indexes | 16 of 36 reports | SQL join queries written from a given schema; second highest salary; normalization |
| Array and counting programs | Single-pass loops, sets and maps over arrays | 15 of 36 reports | Common elements of two arrays; maximum consecutive ones; remove duplicates |
| Short string programs | Reverse, palindrome, character counts, word lengths | 15 of 36 reports | Reverse a string, then with a variation; duplicate character in a string; longest word |
| Number programs | Primes, Fibonacci, patterns and binary search | 13 of 36 reports | Prime check with least complexity; Fibonacci with recursion; square root by binary search |
| Front-end and web basics | HTML, CSS and JavaScript edits, React, APIs | 13 of 36 reports | Restyle a small page with HTML, CSS and JS; == vs ===; build a React timer |
The question patterns that keep coming back
Most Cognizant questions fall into seven patterns. For GenC tracks the skill is a clean definition, a real-world example, and working code in your cluster language.
1. OOP and core Java or Python theory
The most common pattern: 20 of 36 technical reports. Explaining the OOP pillars with real-world examples (12 candidates) was the most repeated interview question, and exception handling came up for 7. Follow-ups go one level deeper: polymorphism types, overloading vs overriding, interface vs abstract class. How to answer: a one-line definition, a real-world example, then a 3-line code sketch. Python-cluster candidates got mutability, lists vs tuples and __init__ instead.
Reported examples. OOP pillars with examples; checked vs unchecked exceptions; abstract class vs interface; final vs finally vs finalize; how a HashMap works; multithreading basics.
2. Projects and track topics
18 of 36 reports. Interviewers asked about your project's stack and challenges (8 candidates), certifications, and your track's subject: security, cloud or GenAI. How to answer: for each resume item, know what it is, why you used it and one problem you solved with it.
Reported examples. Walk through your project; cloud service models, EC2 and S3; phishing and penetration testing; OSI layers; supervised vs unsupervised learning.
3. SQL queries and DBMS theory
16 of 36 reports, in both the assessment and the interview. Join queries from a schema were the most common assessment question (5 reports). How to choose: "second highest" means an ordered subquery or LIMIT/OFFSET; "per group" means GROUP BY; "rows with or without a match" means LEFT JOIN; "remove duplicates" means DISTINCT to read and a self-join to delete.
Reported examples. Joins from a schema; second highest salary; highest and lowest salary; normalization; DELETE vs TRUNCATE vs DROP; delete duplicate rows.
4. Array and counting programs
15 of 36 reports. Single-pass problems: scan once with a counter, a set or a map. How to choose: "common" or "duplicate" means a set or map; a "consecutive run" means a counter that resets; "second largest" means two variables in one pass.
Reported examples. Common elements of two arrays; maximum consecutive ones; sum of values that repeat exactly k times in a row; remove duplicates; second largest element.
5. Short string programs
15 of 36 reports. Reversing a string was the most repeated interview coding task (4 candidates in the first interview, 1 more in a second), usually with a variation: one line, two pointers, or a loop instead of StringBuilder. How to choose: reverse or palindrome means two pointers; "frequency" or "appears twice" means a count array or map; "words" means split, then handle punctuation.
Reported examples. Reverse a string; palindrome; duplicate character; frequency of each character; longest word, then handle full stops.
6. Number programs
13 of 36 reports. First-year programs, but interviewers asked for the efficient version. How to choose: a prime check loops to the square root; Fibonacci can be iterative or recursive (say which); a value in a sorted range means binary search.
Reported examples. Prime check with least complexity; Fibonacci, then recursively; star pattern; square root by binary search.
7. Front-end and web basics
13 of 36 reports. The cluster assessment often has a small HTML, CSS and JavaScript edit, and the 2026 AI track added React builds. How to choose: for a web edit, read every requirement and change one thing at a time; for React, know props down, callbacks up, useState and useEffect.
Reported examples. Restyle a small page; == vs ===; let vs var and NaN; React child-to-parent data; a React timer app.
Preparing for the HR questions
The HR part is mostly yes/no checks at the end of the technical interview (see Stage 4), with an occasional behavioral prompt.
Decide your answers before the day. Know your stance on relocation, shifts, any technology and your joining date. Cognizant's careers site says you may not choose your location, role or business unit, so only say yes if you mean it.
Prepare a few real stories for the rarer prompts. Use your own experiences, say "I", and keep each under two minutes.
| Theme | Reported prompt (paraphrased) | Follow-up to expect |
|---|---|---|
| Self-assessment | Strengths and weaknesses | "How will you work with that weakness?" |
| Learning new tech | A project needs a technology you do not know | "How long will you take to learn it?" |
| Responsibility and teams | A time you handled a responsibility; motivating a team | Challenges you faced as a project lead |
| Deadlines and clients | How do you meet a deadline? | "How would you convince a client after missing one?" |
| Motivation | Why Cognizant? Why this domain? | Not reported |
| Self-rating | Rate yourself in Java, SQL or coding | Questions pitched to your rating |
Rate yourself honestly. In 4 reports the interviewer asked for a self-rating and then questioned at that level. One candidate who rated 3 out of 5 in React, C# and SQL was selected for GenC Next.
A six-week plan
The plan follows the patterns above, most common first, then mocks. Plan on two focused hours a day, in your cluster language.
- Week 1: OOP and core Java or Python theory. Pillars with examples, overloading vs overriding, interface vs abstract class, exceptions, final vs finally vs finalize, collections, static, multithreading basics. Habit: answer each topic aloud as a definition, an example and a 3-line sketch.
- Week 2: SQL queries and DBMS theory. Joins from a schema, GROUP BY, second highest salary, LIKE, deleting duplicates, date functions; keys, normalization, indexes, views, DELETE vs TRUNCATE vs DROP. Habit: write each query by hand before running it.
- Week 3: Short string and array programs. Reverse a string three ways, palindrome, character frequency, duplicate character, longest word, common elements, consecutive ones, second largest. Habit: solve each with and without library help.
- Week 4: Projects and your track. What, why and one problem solved for every resume item; then cloud basics, security and networking, Salesforce, or GenAI and RAG terms, depending on your track. Habit: write a one-line definition for every term on your resume.
- Week 5: Number programs and front-end basics. Prime check to the square root, Fibonacci both ways, star patterns, binary search; HTML, CSS and JavaScript edits, == vs ===, let vs var. Practise the communication tasks and puzzle games too.
- Week 6: Mocks. Two timed 120-minute assessment mocks (2 SQL, 2 coding, 1 web task) and four 30-minute mock interviews in a plain online editor: intro, project, 2 programs, theory, HR checks.
GenC Next hopefuls should add Spring Boot and REST in week 4; AI-track candidates should swap week 5 for DSA, React and a small RAG build.
Only two weeks? Four days on OOP and language theory, three on SQL, three on string and array programs, one on your resume and track, and three on timed mocks and HR answers.
Practice problems that match these experiences
These are well-known practice problems that match the patterns above. They are not claims about Cognizant's question bank unless a row says the problem was asked as-is. OOP theory and projects have no coding analogue.
| # | Practice problem | Pattern | Seen in these experiences as |
|---|---|---|---|
| 1 | Second Highest Salary | SQL ordering and subqueries | Asked as-is in one GenC Next interview; a variant asked for the 2nd highest marks across two joined tables |
| 2 | Combine Two Tables | SQL joins | SQL join queries written from a given schema, the most common assessment question |
| 3 | Max Consecutive Ones | Running counter | Asked as-is in one 2025 GenC Next technical assessment |
| 4 | Intersection of Two Arrays | Set or two pointers | Common elements of two arrays, into a new array |
| 5 | Reverse String | Two pointers | Reverse a string, then with a variation |
| 6 | Valid Palindrome | Two pointers | Palindrome program |
| 7 | First Letter to Appear Twice | Character counting | Find the duplicate character in a string |
| 8 | Prime Number | Square-root bound | Check whether a number is prime with the least complexity |
| 9 | Sqrt(x) | Binary search on the answer | Square root of a number using binary search (second interview) |
| 10 | Build a timer application in React | React state and effects | Asked as-is in a 2026 IIIT Allahabad assessment |
How to handle a question you have never seen
Interview programs are short but arrive with variations, so a repeatable method beats memorised code.
- Repeat the problem and one example. Say the input and expected output back ("for 'hello' you want 'olleh'?") before you type.
- Say the simple approach and its cost. Name the loop and its complexity; one interviewer wanted the least-complexity prime check.
- Name the bottleneck. Repeated lookups suggest a set or map; comparing ends suggests two pointers; a sorted range suggests binary search; "per group" in SQL suggests GROUP BY.
- Say when you are stuck. Interviewers gave hints when candidates paused, and one who needed a hint on sub-queries carried on.
- Code in small pieces in your cluster language, while talking. Some reports had a compiler on the platform, so run the core loop first, then add input handling and edge cases.
- Dry-run one case and fix the wrong line. Trace your example aloud, then expect a follow-up such as "now without StringBuilder" or "now handle full stops".
Why candidates were rejected
Few reports are rejections and only one gives a clear reason, so treat these as lessons from candidates' own reflections, not Cognizant's stated reasons.
- Not coding cleanly in your cluster language. One 2025 candidate knew the logic for two easy problems but could not write error-free Java; the interviewer refused C++, and the candidate was rejected.
- Saying No to relocation or flexibility. One 2024 report says a No on the application form meant no shortlist.
- A weak interview for a higher track. One 2024 report says a weak GenC Next interview can drop you to GenC or nothing, and a weak GenC Pro interview means rejection. A 2025 GenC Pro candidate answered most questions and got no final offer, with no reason given.
- Missing a marks cut-off. One 2024 candidate wrote that GenC Pro and Next needed 70 percent throughout and that falling short in 12th limited their track.
- Resume items you cannot explain. In 4 reports the questions followed the resume line by line. A single miss was not fatal: one candidate who could not recall the types of indexing still got a GenC Next offer.
Selected vs. rejected: do this, not that
No selected candidate described a perfect interview; a few habits repeated, and the one clear rejection shows the cost of skipping them.
| Do this | Not that | What the reports show |
|---|---|---|
| Practise in your cluster language: write 20 short programs in Java, C# or Python without an IDE's help | Relying on your contest language: planning to switch to C++ in the interview | One 2025 candidate was refused C++ and rejected after buggy Java. |
| Explain, then code: state your logic and keep talking while you type | Silent coding: typing without saying what you are doing | Four reports say interviewers focused on the logic and thought process. |
| Admit what you do not know: say so politely and move on | Guessing or bluffing: giving false information to fill silence | Two candidates advised this; one who could not recall the types of indexing still got a GenC Next offer. |
| Own every resume line: prepare what, why and one problem solved for each item | Padding the resume: listing tools or certificates you cannot discuss | Questions followed the resume and profile closely in 4 reports. |
| Answer the HR checks plainly: decide on relocation, shifts and tech stack beforehand | Hedging on relocation or shifts: saying No or "it depends" | Relocation came up for 22 of 26 candidates; one report says a No on the form meant no shortlist. |
If you remember only five things
- Screening tests, a cluster test, then one interview. Communication and aptitude tests, a technical assessment in your skill cluster, then a technical interview of usually 25 to 45 minutes that ends with HR checks; some GenC Next candidates get a second interview.
- The assessment is mostly SQL plus two short programs. Usually 2 SQL and 2 coding questions, often with a small web task, in 120 minutes in most reports.
- The interview tests definitions and clean basics. OOP pillars with examples, exceptions, SQL joins and normalization, and easy string and array programs with a variation.
- Code in your cluster language. One candidate was refused C++ and rejected for not writing clean Java.
- Answer the HR checks plainly. Relocation and shifts came up in most interviews.
FAQ
Is there a coding test before the interview?
Yes, in 2024 to 2026 reports: usually 2 SQL and 2 coding questions in your cluster. Two 2023 GenC reports went from the aptitude and English test straight to the interview.
Do I need advanced DSA?
Not for GenC tracks. Interview programs were short, such as reversing a string or a prime check. The 2026 AI-track assessment is the exception, with 3 coding questions, GenAI MCQs, React and RAG tasks.
Which language should I use?
The one in your skill cluster. Three reports say candidates had to code in it; one C#-cluster candidate was allowed C, C++ or C#.
Is system design asked?
No report in the data had a system design round. The deepest content was in two GenC Next second interviews: Spring Boot and REST in one, Java collections in the other.
How long does it take?
Results came 4 to 5 days to about 5 weeks after the interview, and five reports ran about 6 weeks to about 4.5 months end to end. Cognizant says onboarding then happens in batches.
About this guide
The Codinzhub team researched and wrote this guide from 37 Cognizant software engineer interview records, mostly from 2023 to 2026, including experiences and assessment questions shared on Codinzhub. We kept only what candidates described, plus what Cognizant states officially. The questions are our own short summaries, and the practice links are similar problems unless marked as asked as-is. If you interviewed recently, share your experience on Codinzhub and we will update this guide.
Disclaimer. Cognizant's process changes by track, cluster, college and year. Use this guide to build a foundation, and confirm the current format with your placement office.
Search the question bank
The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.
Showing 20 of 108 questions
Maximum team size from start and end arrays (overlapping intervals)
A Cognizant online assessment question shared on Codinzhub (Chandigarh University).
Build a RAG-based airport service chatbot
A Cognizant online assessment question shared on Codinzhub (IIIT Allahabad).
Birthday Records React component
A Cognizant online assessment question shared on Codinzhub (Technical ACE round).
Fewest changes to make a string periodic and a palindrome
A Cognizant online assessment question shared on Codinzhub (IIT Guwahati).
Beautiful Graph
A Cognizant online assessment question shared on Codinzhub (IIT (ISM) Dhanbad).
Meeting Room
A Cognizant online assessment question shared on Codinzhub (IIT (BHU) Varanasi).
Palindrome-based coding plus a prompt-engineering question
A Cognizant online assessment question shared on Codinzhub (DTU Delhi).
10
A Cognizant online assessment question shared on Codinzhub (IIIT Allahabad assessment).
11
A Cognizant online assessment question shared on Codinzhub.
SQL join queries written from a given schema
Level: GenC, GenC Pro, GenC Next.
Build or restyle a small page with HTML, CSS and JavaScript
Level: GenC, GenC Next.
SQL queries using built-in date functions
Level: GenC, GenC Next.
Find the maximum number of consecutive ones
Level: GenC Next.
Sum of numbers that appear consecutively exactly k times
Level: GenC Next.
Print the frequency of each character in a string
Level: GenC Next.
Build a RAG-based airport service chatbot with conversational context
Level: Not reported.
Build a timer application in React
Level: Not reported.
Birthday Records React component that sorts a list of people
Level: Technical ACE.
GenAI MCQs, e.g. which option explains hallucination and bias
Level: Technical ACE.
Minimum Password Changes
Level: Technical ACE.
Keep preparing on Codinzhub
- Cognizant interview questions and experiences — OA questions and interview experiences candidates shared for Cognizant.
- Browse Cognizant online assessment questions — filter the Codinzhub question bank by company.
- Amazon Software Engineer interview guide — the Amazon process, rounds and question patterns.
- Google Software Engineer interview guide — the Google process, rounds and question patterns.
- Adobe Software Engineer interview guide — the Adobe process, rounds and question patterns.
- All company interview guides — every guide on the Codinzhub blog.
Keep track of what you’ve learned.