New opportunity

Lead Specialist, AI Scientist

Pearson · Austin, United States

About this role

Pearson seeks a Lead Specialist, AI Scientist to design, deploy and scale production AI/ML capabilities for learner intelligence, knowledge graphs, recommendations and personalized learning. The role spans research, data science, software engineering and product delivery, with an emphasis on measurable learner and business outcomes.

Responsibilities

  • Lead AI capabilities from experimentation and prototyping through deployment, monitoring, evaluation and continuous improvement. Deliver Generative AI, LLM, retrieval-augmented generation and agentic AI solutions integrated into Pearson products.
  • Build reusable AI platform services, APIs and workflows. Establish MLOps and AIOps practices for training, observability, governance, reliability and production operations.
  • Evaluate foundation models and architectures against quality, safety, scalability, latency and cost. Set practices for responsible AI, prompt engineering, model and agent evaluation, and AI governance.
  • Partner with Product, Engineering, Design, Learning Science and Data Science; mentor engineers and data scientists; and communicate technical strategy, decisions, risks and outcomes to stakeholders.

Required qualifications

At least 5 years building and deploying production AI/ML systems, including cloud-native applications and MLOps. Experience with applied machine learning and relevant technologies such as Generative AI, LLMs, RAG, recommendations, knowledge graphs or agentic AI; hands-on foundation-model application development; Python, APIs, testing, CI/CD, version control and production operations. Experience designing scalable services in AWS or similar cloud environments, using containerization, orchestration and infrastructure as code, and evaluating systems for quality, reliability, safety, latency, scalability and cost. Familiarity with technologies such as OpenAI, Anthropic, Bedrock, Azure OpenAI, LangGraph, LangChain, Semantic Kernel or vector databases. A bachelor's degree in a relevant field or equivalent practical experience is required.

Preferred

A relevant master's degree or PhD; educational technology or learning-science experience; familiarity with psychometrics, proficiency modeling, Bayesian methods, item response theory or educational measurement; enterprise-scale AI platform, knowledge graph or agentic-system experience; or research, patent, open-source or industry contributions.

Location information differs within the posting: the job header lists Austin, TX and Hybrid, while the role description says “Remote, United States.” The full-time salary range is $150,000–$190,000, with eligibility for an annual incentive program.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

Machine LearningGenerative AILarge Language ModelsRetrieval-Augmented GenerationAI AgentsRecommendation SystemsKnowledge GraphsMLOpsAIOpsPythonAPI DevelopmentCI/CDAWSContainerizationInfrastructure as CodeModel EvaluationPrompt EngineeringResponsible AIOpenAIAnthropicAmazon BedrockAzure OpenAILangGraphLangChainSemantic KernelVector DatabasesCollaborationTechnical CommunicationMentoring

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Deliver measurable learning outcomes

    Lead production AI for learner intelligence, recommendations, knowledge graphs and personalized learning. The posting names learner engagement, efficacy and business impact as expected results.

  • Own AI from prototype through operation

    Take capabilities from experimentation to deployment, monitoring, evaluation and continuous improvement, rather than stopping at a working prototype.

  • Build reusable production infrastructure

    Develop AI services, APIs and workflows for use across Pearson products, and establish MLOps and AIOps practices for observability, governance and reliability.

  • Evaluate and govern generative AI

    Deliver LLM, RAG and agentic applications while evaluating foundation models for quality, safety, scalability, latency and cost and establishing responsible-AI practices.

  • Lead across disciplines

    Partner with Product, Engineering, Design, Learning Science and Data Science; mentor technical colleagues; and communicate architecture decisions, risks and outcomes to stakeholders.

Likely challenges to think through

  • Demonstrating learning efficacy

    A likely difficulty is distinguishing improved learner engagement from improved learning when assessing personalization or recommendations. Prepare to explain how you would define both measures with Learning Science and evaluate a release against them; the posting does not specify a measurement method.

  • Balancing model performance and operating cost

    Foundation-model choices may trade answer quality and safety against latency, scale and cost. Prepare a comparison approach with evaluation criteria, operational thresholds and a rationale for when a simpler architecture would suffice.

  • Reusing services without constraining products

    Shared AI platform components may speed adoption but need to accommodate different product workflows. Prepare to discuss which APIs, evaluation and monitoring practices you would standardize, and where you would leave room for product-specific design.

03

Practice your answers

Technical practice

How would you design and evaluate a recommendation system for personalized learning?

What to coverThe role calls for production recommendations and improved learner engagement and efficacy. Suggested preparation: explain how you would establish a baseline, measure recommendation quality and learner outcomes, and check whether improvements persist after deployment.

How would you use a knowledge graph to support learner intelligence?

What to coverKnowledge graphs and learner intelligence are stated areas of work. Suggested preparation: discuss how you would model relationships, keep graph data current, and evaluate whether the graph improves a learning capability.

How would you build and troubleshoot a retrieval-augmented generation application?

What to coverThe posting explicitly includes RAG and production LLM applications. Suggested preparation: cover retrieval quality, answer grounding, evaluation examples, and how you would isolate retrieval failures from generation failures.

When would you choose an agentic workflow over a simpler LLM application?

What to coverThe role includes agentic AI solutions and agent evaluation. Suggested preparation: compare the added capability with orchestration complexity, reliability, safety, latency and cost, including how you would test a workflow before release.

How would you select a foundation model for a Pearson product capability?

What to coverThe posting calls for evaluating models and architectures against quality, safety, scalability, latency and cost. Suggested preparation: describe a representative evaluation set, decision criteria and how you would revisit the choice as requirements or models change.

How would you establish evaluation and governance practices for an LLM application?

What to coverResponsible AI, prompt engineering, model evaluation and AI governance are stated responsibilities. Suggested preparation: distinguish prompt-level tests from system-level evaluation, and explain how you would identify risks and monitor them in production.

How would you design reusable AI services and APIs for multiple products?

What to coverThe role calls for reusable platform capabilities, services, APIs and workflows. Suggested preparation: discuss interface design, testing, versioning and the trade-off between shared components and product-specific needs.

How would you deploy a scalable AI service in a cloud environment?

What to coverThe posting names cloud-native architectures, containerization, orchestration, infrastructure as code and CI/CD. Suggested preparation: walk through a deployment design and explain how you would address reliability, security, scaling and operational cost.

How would you diagnose a production AI system whose quality or latency has deteriorated?

What to coverThe role owns monitoring, observability, evaluation and continuous improvement. Suggested preparation: explain what evidence you would inspect, how you would distinguish model or data issues from service issues, and how you would verify a fix.

How would you decide whether an AI prototype should become a product capability?

What to coverThe expected results include moving research and prototypes into measurable learner and business outcomes. Suggested preparation: propose baseline comparisons, evaluation criteria and a staged decision that accounts for production readiness as well as product impact.

Behavioural practice

Tell me about a time you aligned several disciplines on an AI product decision.

What to coverThe role involves Product, Engineering, Design, Learning Science and Data Science partners. Suggested preparation: use a real situation, your actions to resolve differing priorities, and the resulting decision or outcome.

Describe a time you mentored engineers or data scientists through a technical challenge.

What to coverMentoring and elevating AI engineering capabilities are stated responsibilities. Suggested preparation: explain the situation, what guidance you gave without taking over, and what changed as a result.

Tell me about a time you communicated a difficult architecture trade-off to stakeholders.

What to coverThe posting calls for communicating strategy, decisions, risks and outcomes across the business. Suggested preparation: describe the competing considerations, how you made the decision understandable, and its result.

Describe a time you moved an experiment toward production.

What to coverThe role spans prototyping, deployment and continuous improvement. Suggested preparation: give a real situation, the actions you took to address delivery or evaluation gaps, and the measurable result if one was available.

Tell me about a time you handled a reliability or quality issue in a deployed system.

What to coverReliable, observable production AI systems are an expected result. Suggested preparation: outline the situation, your diagnosis and coordination, and the outcome or follow-up changes.

02

Sharpen your knowledge

Topics to prepare

  • RAG and agentic AI architecture

    The posting calls for LLM, retrieval-augmented generation (RAG), and agentic AI solutions. Sketch when a learning-product feature would use retrieval, an agentic workflow, or neither; explain the quality, latency, cost, and safety trade-offs. This is a suggested revision exercise, not a specified interview task.

  • Recommendations and knowledge graphs for personalization

    Pearson names learner intelligence, recommendations, knowledge graphs, and personalized learning as target capabilities. On a hypothetical learning scenario, map how learner signals and content relationships could inform a recommendation, then identify what would need evaluation before deployment.

  • Production AI lifecycle and platform design

    The role owns experimentation through deployment, monitoring, and improvement, and calls for reusable services plus MLOps and AIOps. Draw a conceptual architecture showing those stages and where observability, reliability, and governance belong.

  • Model evaluation and responsible AI

    The posting explicitly calls for evaluating models and agents against quality, safety, scalability, latency, and cost. Draft a comparison rubric for two hypothetical foundation-model approaches, including failure cases and a decision rule; the rubric is a preparation suggestion, not a stated Pearson process.

  • Educational measurement concepts

    Learning science, psychometrics, proficiency modeling, Bayesian methods, and item response theory appear under preferred qualifications. If relevant to your preparation, outline how proficiency estimates might differ from engagement metrics and what evidence would support a personalized-learning outcome; these methods are not listed as required.

Skills to revise

  • Build a small Python AI API

    Python, APIs, testing, and foundation-model application development are explicit qualifications. As practice, implement a small API around a hypothetical learning-content task, add tests for normal and failure responses, and explain how you would version its interface.

  • Prototype and assess a retrieval workflow

    RAG, prompt engineering, and vector databases are named in the posting. As a suggested exercise, prototype retrieval over sample content and compare responses with and without retrieval for grounding, incorrect claims, latency, and cost. No particular provider is required by this exercise.

  • Create an evaluation and monitoring plan

    Pearson expects deployed AI systems to be evaluated, monitored, and improved. Prepare a compact test set and scorecard for a hypothetical recommendation or LLM feature, then specify what production signals would trigger investigation and how you would assess a change.

  • Design a deployable service workflow

    The qualifications name cloud services such as AWS, containerization, orchestration, infrastructure as code, CI/CD, and production operations. Practice diagramming a containerized service's build, test, deployment, rollback, and observability path, explaining reliability and cost trade-offs without assuming Pearson's specific stack.

  • Present an architecture decision

    The role requires collaboration across Product, Engineering, Design, Learning Science, and Data Science, as well as mentoring and stakeholder communication. Rehearse a brief decision memo for a hypothetical personalized-learning feature: state the outcome sought, alternatives, risks, evaluation plan, and what each partner would need to resolve.

04

Your preparation checklist

  • Select a production AI project walkthrough

    The role owns AI capabilities from prototype through deployment and improvement. Prepare one project you can substantiate, covering your decisions, production responsibilities, monitoring, and measured outcomes; distinguish your contribution from the team’s.

  • Sketch a reusable learning-AI service

    The posting calls for reusable services and APIs supporting personalization, recommendations, or knowledge graphs. As a practice exercise, draw an architecture showing data flow, a model or retrieval component, API boundaries, and integration points; explain the trade-offs.

  • Prepare a foundation-model evaluation plan

    Pearson emphasizes quality, safety, scalability, latency, and cost. Draft a comparison of plausible model or RAG approaches, with evaluation criteria, test cases, failure modes, and a decision rule; label proposed metrics as your suggestions.

  • Gather production engineering evidence

    The qualifications name Python, APIs, testing, CI/CD, cloud deployment, containers, orchestration, infrastructure as code, and MLOps. Assemble specific examples you can verify, showing what you built or operated and how reliability and observability were handled.

  • Connect technical choices to learner outcomes

    Expected results include learner engagement and efficacy as well as business impact. Prepare a concise explanation of how you would evaluate a personalization or recommendation capability; treat learning-science and educational-measurement methods as preferred, not required.

  • Rehearse a leadership decision story

    The role involves cross-functional work, mentoring, and communicating risks and trade-offs. Prepare one verifiable example that shows stakeholder input, your technical recommendation, how you supported others, and the outcome.

  • Write targeted questions for Pearson

    Ask which AI capabilities are priorities, how learner outcomes and production quality are measured, and what platform components already exist. Clarify the posting’s conflicting location information: Austin, TX and Hybrid in the header versus Remote, United States in the role description.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…