Product design question

Design a permissions model so Glean never surfaces documents a user shouldn't see.

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

  1. State the non-negotiable requirement: a permissions model must mirror the exact access rules of every connected source system, with zero tolerance for leakage.
  2. 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.
  3. 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.
  4. Add a fail-safe default: if a permission check cannot be verified confidently, exclude the document rather than showing it, erring toward under-inclusion.
  5. Add auditability: log every access decision so security teams can verify and investigate the permissions system's behavior.
  6. Define success as zero permission-leak incidents in testing and production, verified through regular red-team style access audits.

What a strong answer includes

Common mistakes

Likely follow-up questions

More product design questions

More questions from Glean

Learn the skill behind it

Chapters of the AI PM course that teach what this question tests.

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank