These are LLD questions of the kind Cognizant actually asks — the patterns that keep coming back in Cognizant's AI project interviews, where what matters is applying LLD 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 LLD concept questions
A common Cognizant LLD question, reflecting their healthcare/insurance client base: design a claims processing system where claim approval rules differ by insurance plan type.
Asked in
Every claim status change needs to be logged to an audit trail, and possibly also trigger a compliance-team alert for high-value claims. What pattern fits, and why is a direct call from Claim.setStatus() to an audit-logging function the weaker design?
Asked in
A Claim class validates the claim, calculates the payout, notifies the claimant, and saves itself to the database — all inside one class. Diagnose this using this course's SRP question.
Asked in
How to use this page: Cognizant rarely asks something you've never seen — they ask a standard LLD concept and then push one level deeper ("why?", "what would you do if..."). Master the concept in the LLD course lessons, and the follow-up stops being scary.
Keep practising: SOLID Principles, Strategy Pattern, Design a Parking Lot and UML Diagrams cover what most Cognizant LLD rounds test — and the Cognizant questions section covers the rest of their selection process.