AI & Technical question
Glean Model Hub may support multiple LLMs for search, assistant, and agent workflows. Design an evaluation framework you would use to decide whether a new model should be added to the portfolio, including how you would assess answer quality, latency, cost, safety, and enterprise-specific requirements such as permissions, grounding, and consistency.
- Glean
- AI & Technical
- 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
Tests ability to design a rigorous, enterprise aware model evaluation framework covering quality, cost, safety, and Glean specific requirements.
How to approach it
- Define what the evaluation decides: whether a candidate model earns a slot in Model Hub for search, assistant, or agent workflows.
- Build an offline eval suite with a golden set of real enterprise queries, scored on accuracy, groundedness to cited sources, and latency under load.
- Add enterprise checks: does the model respect document level permissions, does it stay consistent in tone and format across repeated queries.
- Layer in safety testing, for example red teaming for prompt injection through retrieved documents and cross workspace data leakage.
- Run a limited live pilot with a design partner workspace comparing the candidate against the current default on real usage, not just offline scores.
What a strong answer includes
- Treats permission compliance as a hard gate, for example the model fails outright if it ever surfaces content a tester lacks access to.
- Separates model quality from system quality, since a great base model can still fail if Glean's retrieval or grounding is weak.
- Proposes concrete thresholds, for example groundedness within two points of the current default and latency under a set ceiling at the ninety fifth percentile.
- Includes a live pilot step, since offline evals on curated queries often overstate real world enterprise search quality.
Common mistakes
- Evaluating raw model quality on public benchmarks without testing it against Glean's actual retrieval and permission system.
- Skipping adversarial or safety testing because the model scores well on accuracy alone.
Likely follow-up questions
- How would you weight cost against quality if the best model is also the most expensive?
- What would you do if the model passes offline evals but underperforms in the live pilot?
More ai & technical questions
- How would you measure whether Glean's AI answers are accurate and well-cited?Glean · AI & Technical · Medium
- How would you design a governance model that behaves consistently across Glean's UI, public APIs, and heterogeneous enterprise connectors, for example, a shared policy layer for permissions, action scopes, audit logging, and redaction, even when source systems expose different authentication models and data granularity?Glean · AI & Technical · Hard
- A Fortune 500 customer asks for an audit trail for every AI-agent answer: which data sources were accessed, which permissions were applied, why the response was generated, and whether sensitive content was filtered or redacted. Design the admin and end-user experience, and the core APIs/data model needed to support this without overwhelming either audience.Glean · AI & Technical · Hard
- Several enterprise customers report that the ServiceNow and GitHub connectors are ingesting data successfully, but search results and assistant answers still feel incomplete or low quality. How would you diagnose where the breakdown is across crawl freshness, permissions sync, metadata extraction, entity mapping, ranking, and UX, and how would you decide which fixes to ship first?Glean · AI & Technical · Hard
- Design the next version of Glean’s Indexing API and custom connector platform for large enterprises that need to bring proprietary data sources online quickly. What core capabilities would you prioritize, such as schema/modeling, auth and permissions, incremental sync, observability, and governance, and what principles would you use to keep the platform flexible without creating an inconsistent product experience?Glean · AI & Technical · Hard
- Glean Model Hub lets enterprise customers choose among LLMs for search, assistant, and agent workflows. How would you build a model-provider evaluation framework to decide which new providers to add, including the gating criteria, offline/online evals, and the tradeoffs you would make across answer quality, latency, security, cost, and enterprise-specific requirements?Glean · AI & Technical · Hard
More questions from Glean
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 1: Foundations: the model and the decisions it forces on you
- Chapter 8: Evals: define good and make the number defensible
- Chapter 6: Agents and agentic architecture