Cognizant Interview Experience for PAT Role
Question Details
Round 1:Aptitude Test (Take From Home )For Round 1-Basic Questions from all chapters of Aptitude will do.(Preferred Book-R.S Agarwal) .For Logical Reasoning and English AM...
Full Details
Round 1:Aptitude Test (Take From Home ) For Round 1 -Basic Questions from all chapters of Aptitude will do.(Preferred Book-R.S Agarwal) .For Logical Reasoning and English AMCAT Practice Papers are enough .Questions are repeated mostly from the model papers of AMCAT. Round 2:Technical Interview For Round 2 -One needs to have a good grasp on whatever he/she is writing on resume .If you have written about Java as Technical Skill then Core Java should be very clear . I have been given two programming questions to write 1.Count the numbers of vowels in a string. 2.Palindromic Numbers and Stuff like that . OOPs Concept should be very clear. Features of OOPs with Examples. For Java -You can refer to Geeks for Geeks & JavaTpoint .Very Good Explanations are given.Go through some Java Interview Questions on Google and YouTube .You will get a good bunch of questions and that is enough. I have written SQL.So one query was asked related to LIKE Query. Be clear about the detail explanation of your Final Year Project of College. Round 3:HR Why should I hire you? Why Cognizant? Who motivates you the most? What was the last book you have read and what have read about that?If you written in resume. Do you know about all the policies of Cognizant & Signature in one Document? Are you willing to relocate? Verdict-Selected
About This Question
This is a reported interview question from a cognizant interview for a swe role during the phone screen round reported in 2019.
It covers the following topics: Strings, Sql .
Difficulty rating: Easy
More Cognizant Interview Questions
About Cognizant Interview Reports
This question was reported by a candidate who interviewed at Cognizant. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Cognizant are the higher-signal extractions to take from this report.
For broader preparation context, the Cognizant interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Cognizant reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Cognizant Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Cognizant reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.