Product design question
Design a permissions model so Glean never surfaces documents a user shouldn't see.
- Glean
- Product design
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Trust and safety product design for the single highest-stakes requirement in enterprise search: never leaking unauthorized content.
How to approach it
- State the non-negotiable requirement: a permissions model must mirror the exact access rules of every connected source system, with zero tolerance for leakage.
- Design real-time permission checks: at query time, filter results against the live access-control list from the source system rather than relying on a cached snapshot that could be stale.
- Handle permission changes promptly: when access is revoked in a source system, that change must propagate to Glean's index quickly, not on a slow batch schedule.
- Add a fail-safe default: if a permission check cannot be verified confidently, exclude the document rather than showing it, erring toward under-inclusion.
- Add auditability: log every access decision so security teams can verify and investigate the permissions system's behavior.
- Define success as zero permission-leak incidents in testing and production, verified through regular red-team style access audits.
What a strong answer includes
- Treats this as a zero-tolerance safety requirement, not a normal feature trade-off between coverage and precision.
- Proposes real-time or near-real-time permission checks instead of relying on a potentially stale cached index.
- Specifies a fail-safe default (exclude when uncertain) which is the correct posture for a security-critical system.
- Adds auditability as a distinct requirement, since enterprise security teams will demand it before approving the product.
- Proposes an ongoing red-team audit process rather than treating this as a one-time design decision.
Common mistakes
- Treating stale permission caches as an acceptable trade-off for search speed.
- Not proposing an audit or verification mechanism for a security-critical system.
Likely follow-up questions
- How would you handle a source system with no real-time permission API?
- How would you test this system before trusting it in production?
- What would you do if a leak was discovered after launch?
More product design questions
- How would you improve Glean's enterprise search relevance across 100+ connectors?Glean · Product design · Hard
- Design an onboarding flow that gets a new employee productive with Glean on day one.Glean · Product design · Medium
- How would you let non-technical employees build their own Glean agents?Glean · Product design · Medium
- A Fortune 500 admin wants employees to use Glean agents with GitHub, ServiceNow, and Zendesk, but their security team will only approve launch if they can prevent data leakage, over-permissioning, and unsafe write actions. Design the minimum viable governance controls and the admin/end-user experience you would ship for v1, and explain what you would defer to keep adoption high.Glean · Product design · Hard
- Design Glean’s end-to-end first-run developer experience for a team integrating with its APIs, SDKs, and MCP-based interoperability. Start from sign-up and auth, then walk through sandbox or test data, first successful call, SDK setup, error handling, rate-limit behavior, and documentation. What would you optimize for, and what tradeoffs would you make?Glean · Product design · Hard
- Partner developers integrating Glean with tools like ServiceNow, Zendesk, GitHub, and Microsoft Teams keep filing tickets about webhook reliability and confusing API behavior. How would you isolate whether the main problem is API design, SDK abstractions, documentation, operational reliability, or partner-specific complexity, and how would you prioritize what to fix first?Glean · Product design · Hard
More questions from Glean
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop