← Attentive Interview Insights

Attentive·Software Engineer·Onsite - System Design / Architecture·Senior

Senior
Apr 2026

Summary

System design round at Attentive for a software engineer role. The problem was a catalog service with some genuinely tricky constraints around admin overrides and multi-partner ingestion. More moving parts than I expected going in.

Questions Asked (1)

Q1

Design a catalog service that ingests product data from multiple partner sites (each with different formats and update schedules), stores and exposes that data via an API, and allows admins to override any partner-supplied attribute such that those overrides survive re-ingestion.

System DesignData ModelingAPI & Integrations
Author's notes

I spent the first few minutes just trying to untangle the override requirement because it's the part that actually makes this hard.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale, then propose a layered architecture with an ingestion layer (adapters per partner), a canonical data model with attribute-level provenance, and an API layer. Emphasize how admin overrides are stored separately and applied during reads or merges, ensuring they survive re-ingestion.

Pro tip: Design the system so that partner data and admin overrides are stored in separate tables/collections, and the final product view is a materialized merge. This avoids complex conflict resolution during ingestion and makes overrides durable and auditable.

1. Clarify Requirements and Scale

Ask about data volume, update frequency, partner count, API latency needs, and consistency requirements. This shapes the architecture and data model.

2. Design Ingestion Pipeline

Propose a pluggable adapter per partner to normalize data into a canonical schema. Use a queue or scheduler to handle different update schedules and ensure idempotent writes.

3. Model Data with Overrides

Store partner-supplied attributes and admin overrides separately, keyed by product ID and attribute name. Overrides include metadata like who/when. The effective attribute is computed by merging, with overrides taking precedence.

4. Expose API and Handle Reads

Design REST/GraphQL endpoints that return the merged view. Consider caching or materialized views for performance. Ensure overrides are applied at read time or via a merge service.

5. Address Consistency and Failure

Discuss how to handle partial failures, retries, and eventual consistency. Ensure that re-ingestion doesn't overwrite overrides and that the system is resilient to partner format changes.

Key Points to Mention

  • Canonical data model with attribute-level provenance
  • Separate storage for partner data and admin overrides
  • Idempotent ingestion and handling of different update schedules
  • Merge logic for effective attributes (override wins)
  • API design for reading merged data with caching
  • Audit trail and versioning for overrides

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.