A well-designed platform acknowledges this by providing:
- Observability escape hatches: Easy access to underlying logs, events, and metrics when the high-level view isn't enough. For example, a
platform logs --rawcommand that surfaces the actual Kubernetes pod logs. - Layered documentation: High-level docs for the happy path, and deeper docs explaining the underlying system for when things go wrong.
- Progressive disclosure: The simple interface is the default, but the underlying complexity is accessible — not hidden behind a locked door.
Interview Tip
Interviewers at platform-focused companies often ask: "How do you handle the tension between hiding infrastructure complexity and giving developers enough visibility to debug their own issues?" The correct framing is the Law of Leaky Abstractions: acknowledge that leaks are inevitable, then describe your strategy for making them graceful — escape hatches, layered observability, and documentation that bridges the abstraction gap. Candidates who say "we hide everything" reveal they haven't operated a platform under real production pressure.