Skip to content

Company interview guide

Cognizant interview process and practice questions

Cognizant hires most freshers in India through GenC (Generation Cognizant), which it describes as its hiring and development programme for emerging talent, via campus and off-campus drives. It says its assessments evaluate communication skills, aptitude and/or technical skills depending on the role, and candidates commonly report a technical and an HR interview after them, centred on fundamentals, SQL and their own projects.

As candidates commonly report it; it varies by team, level and year. Last reviewed 18 October 2026.

The interview process

  1. 1Online assessment (aptitude and coding)
  2. 2Technical interview
  3. 3HR interview

Outside India

Candidates elsewhere more often report:

  1. Recruiter screen
  2. Technical interview with the team
  3. Manager or client interview (some roles)
  4. HR interview

What interviewers listen for

  • Fundamentals: OOP, DBMS, SQL, a language
  • Your projects
  • Communication
  • Willingness to learn and relocate
  • Work as one
  • Raise the bar
  • Dare to innovate
  • Do the right thing
  • Own it

Behavioral questions

  1. Tell me about a time your team succeeded because people relied on each other's strengths.

    A good answer covers

    • Who did what, and why the split suited each person
    • How you helped someone or asked for help yourself
    • What the team achieved that one person couldn't have
  2. Tell me about a time you took ownership of a problem that wasn't strictly yours.

    A good answer covers

    • The problem and why nobody had picked it up
    • What you did and who you kept informed
    • The outcome, and whether you'd step in the same way again
  3. Tell me about a time you tried a new approach instead of the usual one. Did it work?

    A good answer covers

    • The usual way and what was wrong with it
    • The new approach and how you tested it safely
    • The result, including what didn't work
  4. What's a piece of feedback that changed how you work?

    A good answer covers

    • The feedback, who gave it and why it stung or surprised you
    • What you changed in practice
    • How you know the change is working

Role and technical questions

  1. Write a SQL query to find the second-highest salary.

    A good answer covers

    • A subquery: the highest salary that is below MAX(salary)
    • Or DENSE_RANK in a window function, which also handles ties and the Nth highest
    • What happens with duplicate salaries, nulls, or fewer than two rows
  2. Explain your project's architecture.

    A good answer covers

    • The layers: front end, back end, database and any outside services
    • How one request flows through them, using a single feature as the example
    • Why you chose that design and what you'd change now
  3. Explain the difference between DELETE, TRUNCATE and DROP in SQL.

    A good answer covers

    • DELETE removes chosen rows and can be filtered with WHERE
    • TRUNCATE empties the whole table quickly but keeps its structure
    • DROP removes the table itself; how rollback and triggers differ between them
  4. What is the difference between method overloading and method overriding? Give an example.

    A good answer covers

    • Overloading: same name, different parameters, chosen at compile time
    • Overriding: a subclass replaces a parent method, chosen at run time
    • A short example, such as area() for shapes or a payment's process() method
  5. A page in your project takes ten seconds to load. How would you find out why?

    A good answer covers

    • Measuring first: browser network tools, server logs, query times
    • Common causes: slow database queries, large images or scripts, too many calls
    • One fix, and how you'd check it actually helped
  6. For experienced candidates: how have you handled a client who changed requirements late in a release?

    A good answer covers

    • Understanding why the change mattered to the client
    • Showing the impact on scope, dates and risk clearly
    • The agreement reached and how the team delivered it

Why Cognizant? Fit and HR questions

  1. Tell me about yourself.

    A good answer covers

    • Your degree and the technologies you know best
    • One project and your part in it, with a result
    • Why you're applying for this role, in under two minutes
  2. Are you comfortable relocating?

    A good answer covers

    • A clear, honest answer, with any real constraint stated politely
    • Why you're open to it, such as the projects and learning it brings
    • Anything that shows you've adapted before, like studying away from home
  3. Why Cognizant, and what kind of work would you like to do here?

    A good answer covers

    • Something specific: the GenC training path, a practice area, or recent work you read about
    • The kind of projects or technologies you'd like to start with
    • How that fits your longer-term plan
  4. Do you have any questions for us?

    A good answer covers

    • One or two thoughtful questions about training, the first project or the team
    • Nothing already answered on the careers site
    • A brief thank-you

Tips

  • Revise SQL joins and simple queries.
  • Be ready to explain every technology on your resume.
  • Read the GenC page for the track you're applying to; the role decides whether assessments lean on aptitude, coding or communication.
  • Practise explaining a SQL query out loud: what each clause does and the order it runs in.
  • Keep a short story ready for a few of Cognizant's values, such as owning a problem or trying a new approach.
  • Keep your resume and academic certificates ready; Cognizant asks for them during hiring.

Practise it out loud

A mock interview asks the way Cognizant's interviewers are known to, follows up on your answers and gives you a report. The warm-up is free, needs no account and checks five of these questions as you answer.

About this guide

Written by Orbit from Cognizant's own public pages and what candidates commonly report. Orbit isn't affiliated with Cognizant. The questions are practice questions in the style of its interviews, not questions taken from them. Processes change, so check the job post and what your recruiter tells you.

Sources