These are Prompt Engineering questions of the kind Infosys actually asks — the patterns that keep coming back in Infosys'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.
Infosys Prompt Engineering concept questions
Explain zero-shot, one-shot and few-shot prompting with examples, and say when you would use each.
Asked in
An LLM keeps returning JSON wrapped in explanatory text so your code cannot parse it. How do you fix this?
Asked in
Infosys Prompt Engineering applied & hands-on questions
This prompt classifies support tickets and is wrong far more often than expected — especially on delivery complaints. Find three problems with the examples and fix them.
Asked in
Classify each ticket: billing, technical or logistics.
"Charged twice for one order" -> billing
"Refund not received" -> billing
"Wrong amount debited" -> Billing
"App keeps crashing" -> technical
Ticket: "Package marked delivered but never arrived" ->How to use this page: Infosys 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 Infosys Prompt Engineering rounds test — and the Infosys exam guide covers the rest of their selection process.