System Design with ER Diagram | Dataford Interview Questions

Your question is System Design with ER Diagram. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

Problem

Design a small system with OOP (name the classes and their relationships) and a database schema (ER diagram) to support it

Asked in the Onsite round 1 stage.

Define a small but coherent system, identify its core entities, and explain how the object model maps to persistent storage. Be prepared to discuss assumptions, relationships, ownership, validation, and basic data access boundaries.

Deliverables

State assumptions and identify the main use cases.
Name the classes, responsibilities, attributes, and relationships.
Provide an ER diagram or equivalent relational schema.
Explain primary keys, foreign keys, cardinality, and important constraints.
Describe how a representative workflow moves through the object and persistence layers.

Your question is System Design with ER Diagram. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

Design a small system with OOP (name the classes and their relationships) and a database schema (ER diagram) to support it

Asked in the Onsite round 1 stage.

Deliverables

State assumptions and identify the main use cases.
Name the classes, responsibilities, attributes, and relationships.
Provide an ER diagram or equivalent relational schema.
Explain primary keys, foreign keys, cardinality, and important constraints.
Describe how a representative workflow moves through the object and persistence layers.