These are Prompt Engineering questions of the kind Cognizant actually asks — the patterns that keep coming back in Cognizant's AI project interviews, where what matters is applying Prompt Engineering sensibly for clients rather than research depth. Treat this page as a mock interview: say every answer out loud before revealing it. If one surprises you, the lesson behind it is linked at the bottom.
Cognizant Prompt Engineering concept questions
What is prompt injection? Can it be prevented the way SQL injection can?
Asked in
Which model settings would you use for a data-extraction prompt versus a marketing-copy prompt, and why?
Asked in
Cognizant Prompt Engineering applied & hands-on questions
This internal tool summarises support tickets and has tools available: read_ticket, update_ticket_status, send_email. Ticket text is written by customers. Identify the risk and give the two changes you would make first.
Asked in
System: You are a support assistant. Summarise the ticket and
update its status. Email the customer if the issue is resolved.
Ticket #4821: {{ticket_text}}How to use this page: Cognizant rarely asks something you've never seen — they ask a standard Prompt Engineering concept and then push one level deeper ("why?", "what would you do if..."). Master the concept in the Prompt Engineering course lessons, and the follow-up stops being scary.
Keep practising: Anatomy of a Prompt, Zero-shot & Few-shot, Chain-of-Thought and Prompt Injection & Safety cover what most Cognizant Prompt Engineering rounds test — and the Cognizant questions section covers the rest of their selection process.