Data Modeling for Product Features | Dataford Interview Questions

How do you approach data modeling for new product features?

Use the provided feature, status history, and project relationship data to produce a concise feature-level view. Include features even when they have no status history or project assignments.

Output

One row per feature with feature_id, feature_name, current_status, project_count, and lifecycle_stage.
Order by feature_id ascending.

Schema

product_features

Column	Type	Description
feature_idPK	INT	Unique product feature identifier
feature_name	VARCHAR(150)	Product feature name
owner_team	VARCHAR(100)	Team responsible for the feature
created_at	DATE	Date the feature was created

feature_status_history

Column	Type	Description
status_history_idPK	INT	Unique status history record identifier
feature_id	INT	Referenced product feature
status	VARCHAR(30)	Recorded feature status
status_date	DATE	Date the status became effective

feature_projects

Column	Type	Description
assignment_idPK	INT	Unique feature-project assignment
feature_id	INT	Referenced product feature
project_name	VARCHAR(150)	Project using or implementing the feature

Your question is Data Modeling for Product Features. Start with the requirements and the three tables in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

Problem