← Notable Interview Insights

Notable·Software Engineer·Onsite - System Design / Architecture·Intermediate

Intermediate
Mar 2026

Summary

System design question at Notable for a software engineer role. Pretty focused, just the one problem about designing a brightness control switch, but there was enough depth to keep it interesting for a while.

Questions Asked (1)

Q1

Design a switch that controls brightness levels for light bulbs. All bulbs share the same 3 brightness levels, but each bulb has a different max wattage, so the actual watt output per level varies by bulb.

System DesignTechnical Trade-offsData Modeling
Author's notes

The abstraction layer is what tripped me up at first.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then model the domain with a clear separation between brightness levels and bulb-specific wattage mappings. Design a flexible system that allows adding new bulbs or brightness levels without major changes, and discuss trade-offs between different data models and control mechanisms.

Pro tip: Demonstrate foresight by discussing how to handle edge cases like invalid brightness levels or bulb failures, and mention the importance of logging and monitoring for debugging and maintenance.

1. Clarify Requirements

Ask questions to understand the scope: number of bulbs, types of bulbs, how brightness levels are set (e.g., via API, UI), and any constraints like power limits or real-time updates.

2. Define Domain Model

Identify core entities: Bulb (with max wattage), BrightnessLevel (e.g., Low, Medium, High), and a mapping from brightness level to wattage per bulb. Consider using a percentage of max wattage for each level.

3. Design Control Interface

Design an interface (e.g., a Switch class) that accepts a brightness level and applies it to all bulbs, computing the actual wattage for each bulb based on its max wattage and the level's percentage.

4. Handle Extensibility and Edge Cases

Ensure the design allows adding new brightness levels or bulb types without modifying existing code. Handle invalid inputs, bulb failures, and concurrency if needed.

5. Discuss Trade-offs and Scalability

Compare different approaches (e.g., storing mappings in code vs. database) and discuss scalability, performance, and maintainability considerations.

Key Points to Mention

  • Use of an enum or constants for brightness levels to ensure consistency across bulbs.
  • Storing bulb-specific wattage mappings as a percentage of max wattage to allow uniform brightness levels.
  • Applying the Strategy or Factory pattern to encapsulate bulb-specific behavior and enable easy addition of new bulb types.
  • Considering a centralized controller that manages all bulbs and applies brightness levels atomically.
  • Discussing trade-offs between hardcoding mappings vs. using a configuration-driven approach for flexibility.
  • Mentioning validation and error handling for invalid brightness levels or bulb communication failures.

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