These are HLD questions of the kind Infosys actually asks — the patterns that keep coming back in Infosys's AI project interviews, where what matters is applying HLD 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 HLD concept questions
An Infosys interviewer asks you to explain leader-follower (primary-replica) database replication in plain terms, and why it helps read-heavy applications.
Asked in
An Infosys interviewer asks for a simple, real-world example that shows the difference between latency and throughput.
Asked in
Infosys HLD applied & hands-on questions
Infosys-style: your cache can hold 1,000 items, but your application accesses tens of thousands of distinct items over the day, with a small set of 'popular' items being accessed repeatedly. Which eviction policy — LRU or a simple FIFO (evict oldest inserted) — would you recommend, and why?
Asked in
How to use this page: Infosys rarely asks something you've never seen — they ask a standard HLD concept and then push one level deeper ("why?", "what would you do if..."). Master the concept in the HLD course lessons, and the follow-up stops being scary.
Keep practising: Caching Explained, Databases at Scale, Design a URL Shortener and Interview Framework cover what most Infosys HLD rounds test — and the Infosys exam guide covers the rest of their selection process.

