Cognizant interview experience posts are interesting to read because there isn’t one standard format — what you get depends heavily on which role you applied for, and sometimes on what you said in your intro. After going through 33+ experiences across Gen C, CIS, Digital Nurture, and Engineer Trainee roles, the patterns are clear but the surprises are real.
Preparing for Cognizant or other fresher placements? Join our Telegram channel for daily job alerts and placement updates.
Job Summary
Cognizant interview experience — which role changes everything
Cognizant recruits freshers into several tracks. Gen C is the most common fresher role. CIS (IT Service Desk) is a separate track with completely different interview questions. Digital Nurture and Engineer Trainee roles fall in between. Knowing which role you’re interviewing for matters because the questions are genuinely different.
One thing common to all roles: ID verification happens first. College ID, government ID, or all semester mark memos (including 10th standard in some cases). Have all documents ready. You’re not getting into the interview without them.
Duration varies — Experience 4 noted 31 minutes, Experience 6 ran 41 minutes for a Gen C role. Generally expect 25-45 minutes.
Gen C technical round — what they ask
Cognizant has something unusual: aptitude questions get asked during the interview itself, not just in the written test. Three to four questions on speed/distance/time, percentages, profit/loss, or puzzles show up in at least half of the Gen C experiences. Don’t assume aptitude prep stops after you clear the written round.
Your project is the other constant. Experience 22 had ML questions specifically because the student’s project was on ML. Experience 11 got deep cybersecurity questions because the student was in a cybersecurity program. Cognizant follows wherever your resume points — this is a pattern you’ll see across several companies, but Cognizant does it particularly consistently. Whatever domain you’ve worked in, expect follow-up questions in that space.
OOPs was asked in roughly half the experiences, most commonly overloading vs overriding. Experience 5 asked for definitions plus working code with output explanation — so it wasn’t just “define method overriding” but “write it, run it in your head, and explain what happens.” Be ready to write, not just explain.
Python came up frequently in recent (2024) experiences: list vs tuple, pickling (what it is and why), monkey patching, deep copy vs shallow copy, OOPs in Python, local vs global variables. Experience 6 had a specific question: “Can an empty class be created in Python?” — the answer is yes, and they wanted to know if you’d actually tried this, not just read about it.
C language questions: pointers, arrays, structures, static variables, format specifiers, scanf/printf purpose, null character behavior, how negative integers are stored. Experience 23 gave a C++ program and asked for the output — so read carefully and trace the execution.
SQL and databases: database definition, DML commands, CREATE/DELETE/UPDATE/RENAME syntax, array and dictionary syntax in the context of databases, primary key vs unique key. Experience 21 asked for a query to create an employee table and then update it with salary records.
Networking (mostly for CIS role, but some Gen C too): OSI model, protocols, LAN vs WAN, VPN definition, firewall basics.
Recent trends in IT — asked in almost every Gen C experience. Pick one trend you actually know something about and explain it properly. Saying “AI and ML are trending” and stopping there is not enough.
CIS role — completely different territory
If you applied for the CIS (IT Service Desk) role, the interview is essentially a customer support aptitude test. Technical depth doesn’t matter. Communication and problem-solving mindset do.
Scenario questions were the core: “What will you do if your PC slows down?”, “What measures will you take if your printer and system are not working?”, “If the system has been slow, what will you do?” (Experience 9). These test your troubleshooting thought process out loud.
Experience 10 had the most memorable question from this batch: “How would you explain Instagram to an 80-year-old person who doesn’t have any knowledge about it?” This is a classic support-role question about simplifying technical concepts for non-technical users. The answer isn’t about Instagram — it’s about whether you can communicate across knowledge gaps.
VPN comes up repeatedly for CIS: “Why do businesses need VPN?” and “What is VPN?” (Experience 17, Experience 9). Basic network understanding is expected. OS definition, server basics, LAN/WAN. Nothing deep.
Rotational shifts and location flexibility are emphasized even more in CIS than in other roles. This is a 24/7 support function. They want explicit confirmation you’re okay with shift work.
HR questions — and the ones that caught people off guard
Standard Cognizant HR: Why IT? (for non-IT backgrounds), Why Cognizant?, relocation, shift preferences, certifications, recent workshops. All consistent across experiences.
But Cognizant’s HR has a reputation for going wherever your resume or intro takes them. Experience 26 mentioned learning Japanese in their intro — the interviewer asked them to say something in Japanese. The same experience had: “If you had a billion dollars, what would you do?”, “What new thing did you recently learn in electronics?”, “How to save our environment?”, and “Memorable day in my life.” These are all from a single interview that ran 15 questions long.
Experience 15 (CIS role) asked: “Tell about the movie you saw recently.” Not a trick. They want to see how you construct a narrative and whether you have genuine interests.
Experience 31 had a direct challenge: “Why should I hire you instead of CSE and IT students?” — directed at a non-IT student. Have a concrete answer to this. “I’m a quick learner” won’t cut it. What specific thing about your background makes you useful?
Experience 14 included a Group Discussion format before individual interviews, where students took turns presenting points and then defending them in a Q&A. Not every venue does this, but some do.
ECE and non-CS students
Cognizant asks non-IT students “Why IT instead of core?” consistently. But they also sometimes ask branch-specific questions — Experience 4 (EEE student) got asked about Bluetooth, microprocessors, generators, alternators, and wire colors in electrical systems. Experience 27 (ECE) got accumulator, repeater, microprocessor questions. Experience 24 had flip flop, diode, forward/reverse bias, and Op Amp questions.
The message here is: don’t completely abandon your core subject knowledge. A few hours of reviewing basics before the interview is worth it.
One thing students don’t prepare enough for
The “tell me about recent trends in IT and explain one” question comes up in Cognizant more than in other companies. Most students name something (Generative AI, cloud, blockchain) and then can’t go deeper than the name. Pick one trend, read enough to explain how it works at a basic level, and know one real-world application. That’s all they need. But students who just say “AI is trending these days” without anything else to add tend to get follow-up questions they can’t answer.
📖 Want 80+ Real Cognizant Interview Experiences?
Get the complete PDF with actual questions asked across Gen C, CIS, and Digital roles — from freshers who cleared Cognizant interviews.
Note: freshershunt.in compiles these interview experiences from student contributions. We are not affiliated with Cognizant. Details may vary by batch, location, and interviewer. Always verify with the official Cognizant careers page.