AI Engineer - Data and Evals
Summary
Builds the datasets, benchmarks, agentic LLM-judge verifiers, and eval platform/infrastructure that measure and improve the quality of Glean's enterprise AI assistant and agents. Core stack is Go and/or Python backend engineering with LLM/RAG evals, traces, and simulation environments; hybrid role (4 days/week) in Mountain View or San Francisco.
About the Role:
The bottleneck in building reliable, useful AI is no longer writing code. It's defining what good looks like and measuring how well our products deliver it. That takes high-quality data and evals that teams can trust.
Our team owns data and evaluation science for Glean's AI products. We build evalsets, agentic LLM-judges, and benchmarks that capture what good looks like, along with the platform and infrastructure that run evals reliably at scale, and enterprise simulation environments where we test how our assistants and agents actually perform. Starting from real production usage, you'll turn what we learn into evals that guide improvements across the entire stack, from agent harnesses to tool use, skill iteration, model routing, and post-training of task specific models.
You'll bring new research into production and partner with R&D, product, and GTM to turn findings from evals into better products and customer outcomes. If you care about quality and want to build the systems that measure it, this role is for you.
You will:
- Build evalsets and benchmarks from expert-curated examples, production data, synthetic data, and past failures, covering edge cases and key user slices.
- Build and scale the eval platform and agent observability: experiment pipelines, trace capture and replay, and dashboards, with reproducible, affordable runs.
- Build agentic LLM verifiers for correctness, groundedness, citation quality, and task success, and calibrate them against human labels using clear rubrics.
- Run evals at every stage, from CI and pre-release suites to sampled production traffic, and report results with confidence intervals.
- Build enterprise simulation environments with simulated users and realistic company data to test multi-step agent tasks.
- Diagnose failures by slice and trace, and turn eval results into concrete fixes, weighing quality against latency and cost.
About you:
- 5+ years of software engineering experience with strong Go and/or Python and backend fundamentals: APIs, data modeling, testing, and distributed pipelines. TypeScript is a plus.
- Experience building datasets and benchmarks for LLM use-cases, RAG, or agents, including evalset curation and synthetic data generation.
- Familiarity with eval methodologies and their tradeoffs: deterministic metrics, LLM-as-a-judge, pointwise vs pairwise grading, human labeling, and judge calibration.
- Experience building eval or experiment infrastructure that runs reliably at scale, including CI/CD integrations and observability tooling like OpenTelemetry.
- Strong analytical skills: you dig into traces and failure cases, write SQL, and use data and metrics to explain why quality moved.
- Nice to have: experience with simulation environments and/or model post-training techniques.
- This role is hybrid (4 days a week in our Mountain View or San Francisco office)
By clicking “Submit Application,” I confirm that I have read the Global Data Privacy Notice and the Applicant Arbitration Agreement, and I agree to the terms.
Skills
As published by greenhouse · 8 questions · 2 written answers
Basics
First Name, Last Name, Email, Phone, Resume/CV, Cover Letter
Short answers (3)
- LinkedIn Profile
- Do you know anyone currently at Glean?
- Please input the total years of experience you have that are relevant for this role.
Pick from a list (3)
- How did you hear about Glean?
- Are you willing and able to commit to the hybrid policy if hired?
- Do you require sponsorship? optional
Written answers (2)
- What AI tools are you currently using today and how are you using them?
- Describe one production ML system relevant to this role that you personally shipped. What did you own, what baseline or metric did you use, what tradeoff or failure did you encounter, and what changed after launch?




