Make the right thing easy: auto-generate service dashboards, provide libraries that instrument code automatically, and include observability in your definition of done for new features.
Strong answers cover: making observability tools developer-friendly, embedding dashboards and alerts into the development workflow, "you build it, you run it" ownership, providing training and runbooks, celebrating good observability practices, and gradually increasing developer on-call responsibility. Best candidates discuss overcoming resistance and making observability a natural part of the development process.
Tests cultural leadership alongside technical skills. The best observability tools are useless if developers do not use them. Candidates who can bridge the gap between SRE practices and development teams are invaluable.