Asked me to explain the architecture of one of the projects from my resume.

Explained using class diagrams.

Designed a WhatsApp-like service.

Given the high-level design first, then dived deeper, explaining load balancing, splitting into microservices and communication between them, notification service, message queuing, database sharding, etc.

Asked me how to maintain the sequencing of messages, since clients' timestamps would be unreliable.

Created a class diagram for a standalone Chess board game.

Discussed my design choices, such as why a particular class/relationship was needed, or why a method was placed in one class rather than another. Convinced the interviewer for some choices, giving proper reasons, and made changes in the design for others.

Provided pseudocode for all possible moves of any piece.

Asked me to explain the architecture of one of the projects from my resume.

Explained using class diagrams.

Designed a WhatsApp-like service.

Given the high-level design first, then dived deeper, explaining load balancing, splitting into microservices and communication between them, notification service, message queuing, database sharding, etc.

Asked me how to maintain the sequencing of messages, since the client's timestamp would be unreliable.

Created a class diagram for a standalone Chess board game.

Discussed my design, like why a specific class/relationship was needed, why a method was in one class rather than another, etc. Convinced him for some of these points with proper reasons and made changes in the design for others.

Provided pseudocode for all possible moves of any piece.