New opportunity

Product Manager- AI Education

Basis AI · New York, United States

About this role

Basis AI is hiring a Product Manager for AI Education to help an already AI-native organization use emerging models and agents more effectively. Working with its internal Atlas team, the role focuses on changing how people work—not delivering introductory AI training. Basis develops agents that perform end-to-end work for accounting firms, while Atlas builds AI-enabled workflows within Basis.

Responsibilities

  • Test newly released models, build and run agent-based workflows, assess what has meaningfully changed, and distinguish durable capabilities from demonstrations.
  • Develop the organization’s approach to AI learning through company-wide programs, role-specific playbooks, hands-on workshops, individual support, and potentially skills or agents that teach people within their workflows.
  • Explain differences among models, tools, and workflows to engineers and non-engineers without oversimplifying them.
  • Identify capability gaps, choose interventions that change behavior, encourage participation across teams, and measure adoption by whether people work differently and agents take on more valuable work—not by attendance.
  • Turn frontier techniques into secure, reliable, repeatable approaches suitable for a growing company serving large customers and handling sensitive data.

Requirements and working arrangement:

  • Firsthand, ongoing practice with AI models, multiple agents, and self-built workflows; enthusiasm for coding agents and applying agents to real-economy problems.
  • Ability to work independently, exercise organizational judgment, and teach complex concepts effectively.
  • In person in Flatiron, NYC, five days a week. No specific degree or years of experience are stated.

Compensation and benefits: The stated salary range is $100K–$300K, with equity eligibility. Benefits include medical, dental, vision and life insurance; six coaching and six therapy sessions; a company-paid Wellhub Gold membership; unlimited PTO and 12 paid holidays; daily meal stipends and $300 for a desk setup; pre-tax commuter benefits, a 401(k), and parental leave.

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

Skills for this role

AI agentsCoding agentsAI educationAI model evaluationWorkflow designTraining program designWorkshop facilitationChange managementAdoption measurementTechnical communicationData security

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

  • Evaluate frontier models through firsthand work

    The role calls for testing major model releases, running multiple agents and building workflows to distinguish durable capabilities from compelling demos.

  • Build learning into real workflows

    Basis describes an already AI-native workforce, not an introductory training audience. The role may use company-wide programs, role-specific playbooks, workshops, individual support or agents that teach in the flow of work.

  • Own behavioral adoption

    The posting defines success by whether people work differently and agents take on more valuable work, rather than by attendance. The PM identifies capability gaps, chooses interventions and measures the resulting change.

  • Make frontier techniques usable across the company

    The role must turn promising individual setups into secure, reliable and repeatable approaches for a growing organization serving large customers and handling sensitive data.

  • Explain technical distinctions without flattening them

    The PM must make differences among models, tools and workflows intuitive to both engineers and non-engineers while retaining the nuances needed to redesign work.

Likely challenges to think through

  • Speed versus evidence

    Likely preparation challenge, not a confirmed employer problem: weekly model changes create pressure to recommend tools before their value is durable. Prepare a way to test new capabilities against repeatable tasks and explain when evidence is still limited.

  • Education versus changed behavior

    Likely preparation challenge: experienced AI users may not benefit from broad instruction, even when a workshop is well attended. Prepare an approach to finding role-specific friction, embedding help in existing work and checking whether workflows actually change.

  • Experimentation versus organizational trust

    Likely preparation challenge: a fast solo-agent workflow may be hard to repeat safely across teams handling sensitive data. Prepare to discuss how to preserve useful experimentation while assessing reliability, data exposure and repeatability before wider adoption.

03

Practice your answers

Technical practice

How would you test a newly released model before recommending it for internal workflows?

What to coverSuggested preparation: Describe representative tasks, comparisons with current models, repeated trials and the evidence you would collect about quality and reliability. Explain how you would distinguish a durable improvement from an impressive demonstration.

How would you design an agent-based workflow for work that currently spans several human steps?

What to coverSuggested preparation: Map the task, agent responsibilities, handoffs and points where human judgment remains valuable. Discuss how you would test whether the workflow completes useful work end to end rather than merely accelerating one step.

How would you diagnose an agent workflow that succeeds in a demo but fails on longer-running work?

What to coverSuggested preparation: Walk through how you would locate failure points across steps, inspect outputs and test whether fixes hold across varied cases. Address the trade-off between greater autonomy and reliable completion.

How would you assess a coding agent’s readiness to contribute to a production workflow?

What to coverSuggested preparation: Explain how you would evaluate its work beyond code generation, including reviewability, testing and what happens when it makes a mistake. The posting says Atlas has shipped agents that push code to production; do not assume a particular approval or deployment process.

How would you turn a new AI capability into a role-specific playbook for experienced users?

What to coverSuggested preparation: Start with the role’s existing work and identify the decisions or tasks the capability could change. Explain what examples, boundaries and hands-on practice would help experienced users apply it rather than revisit introductory material.

When would you use a workshop, individual support or an in-workflow teaching agent?

What to coverSuggested preparation: Compare the interventions by the capability gap, frequency of use and need for feedback in context. Describe how you would check whether the chosen intervention changes work after the session or interaction.

How would you explain a subtle difference between two models, tools or workflows to both engineers and non-engineers?

What to coverSuggested preparation: Ground the distinction in a concrete work decision while retaining important limitations and trade-offs. Show how you would adjust the level of detail without giving either audience a misleading simplification.

How would you measure whether AI education changed adoption rather than just attendance?

What to coverSuggested preparation: Define observable changes in workflows and the value of work agents take on, then compare them with a baseline over time. Discuss how you would check that the change is useful and sustained, not just increased tool usage.

How would you adapt a power user’s agent setup for company-wide use with sensitive data?

What to coverSuggested preparation: Identify risks to data handling, reliability and repeatability, and describe safeguards you would consider before broader use. Explain how you would preserve room to experiment while making the approach trustworthy at scale.

How would you decide which AI capability gap to address first across teams?

What to coverSuggested preparation: Compare gaps by their effect on valuable work, the readiness of a practical intervention and the effort required to change behavior. Explain what evidence would prompt you to revise the priority after an initial test.

Behavioural practice

Tell me about a time hands-on testing changed your view of an AI tool or technique.

What to coverSuggested preparation: Use a real situation, describe what you built or tested and explain what evidence changed your judgment. Finish with the resulting decision and what you learned about separating demonstrations from durable capability.

Tell me about a time you helped experienced colleagues change an established workflow.

What to coverSuggested preparation: Describe the situation, the behavior you wanted to change and how you earned participation without relying on a generic training session. Give the result in terms of changed work, including any limits to adoption.

Tell me about a time you taught a complex technical distinction to people with different backgrounds.

What to coverSuggested preparation: Explain the audiences and the decision they needed to make, then describe how you adjusted your explanation without losing an important nuance. Share evidence that they understood and could use it.

Tell me about a time you had to balance a promising automation with organizational risk.

What to coverSuggested preparation: Set out the opportunity and the reliability, repeatability or data concerns you faced. Describe your decision, whom you involved and what happened as a result.

Tell me about a time you independently prioritized an ambiguous, cross-team problem.

What to coverSuggested preparation: Describe the competing needs, how you identified the most consequential gap and the intervention you chose. Explain how you assessed the outcome and what you changed in response.

02

Sharpen your knowledge

Topics to prepare

  • Durable model capability versus demos

    Suggested exercise: Define criteria for deciding whether a newly released model improves a recurring task, including repeatability and failure cases. The posting explicitly asks for firsthand testing and judgment about what meaningfully changed.

  • Agent-driven redesign of work

    Suggested exercise: Map a multi-step knowledge-work process and identify which steps agents could take end to end, where people would still exercise judgment, and how responsibilities would change. Atlas aims to move beyond individual productivity gains toward agents doing larger portions of work.

  • Adoption as behavior change

    Suggested exercise: Contrast workshop attendance with evidence that a team changed its workflow and assigned agents more valuable work. The role explicitly owns adoption, not attendance, and must choose interventions that change behavior.

  • Organizational trust in AI workflows

    Suggested exercise: Compare a solo user's agent setup with one intended for repeated use across teams; identify security, reliability, and repeatability concerns. The posting highlights sensitive data, large customers, and the limits of power-user setups.

  • Models, tools, and workflows

    Suggested exercise: Explain how a change in model capability could alter a tool choice or an entire workflow, without treating those as interchangeable. The role calls for explaining subtle distinctions to engineers and non-engineers.

Skills to revise

  • Run comparative model tests

    Suggested exercise: Give two models the same realistic, non-sensitive task; record outputs, failures, and whether any improvement holds across repeated runs. This rehearses the posting's requirement to test new models and separate durable capability from demonstrations.

  • Build and assess a multi-agent workflow

    Suggested exercise: Construct a small workflow using multiple agents, including a coding agent where appropriate, and inspect handoffs and completed work. The posting calls for firsthand practice running agents, building workflows, and enthusiasm for coding agents.

  • Create a role-specific learning intervention

    Suggested exercise: Draft a one-page playbook and a hands-on workshop for an already AI-using team, centered on one changed workflow rather than introductory prompting. Both formats are named in the posting.

  • Diagnose capability gaps and measure adoption

    Suggested exercise: For a hypothetical team, identify one gap, select a targeted intervention, and specify before-and-after evidence of changed work and agent responsibility. The role is self-directed and explicitly measures adoption through behavior.

  • Explain a workflow to different audiences

    Suggested exercise: Present the same agent workflow to an engineer and a non-engineer, adapting the explanation while retaining its limitations and tradeoffs. The posting explicitly requires clear teaching without oversimplification.

04

Your preparation checklist

  • Prepare an agent-workflow walkthrough

    The role calls for firsthand work with multiple agents, coding agents, and self-built workflows. If available, choose a project you can explain end to end: the task, agent responsibilities, your decisions, failure modes, and what the agents accomplished.

  • Draft a model-evaluation example

    The posting emphasizes testing new models and separating durable capabilities from compelling demos. Prepare a comparison using a real task, repeatable tests, observed limitations, and a decision about whether to change a workflow.

  • Design an AI-learning intervention

    Basis describes an already AI-native workforce, not introductory training. As a practice exercise, sketch how you would identify one capability gap and address it through a role-specific playbook, hands-on workshop, or in-workflow aid.

  • Practice explaining a technical trade-off

    The role requires explaining distinctions among models, tools, and workflows to engineers and non-engineers. Prepare two short explanations of the same trade-off, preserving the important limitations in both.

  • Define evidence of changed behavior

    The posting says success is adoption, not attendance. Propose a before-and-after measure showing whether a team works differently and agents take on more valuable work; explain what evidence would challenge your conclusion.

  • Review a workflow for organizational use

    Basis highlights security, reliability, repeatability, and sensitive data. For your walkthrough or design exercise, identify what you would validate before extending a solo workflow across teams; frame safeguards as proposals, not existing Basis policy.

  • Prepare questions for Atlas and confirm logistics

    Ask how Atlas identifies capability gaps, embeds with teams, and evaluates whether its agents change work. Also be ready to discuss the posting’s five-days-a-week, in-person Flatiron arrangement.

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…