Bringing AI in at Speak

Decide when AI can say a tenant boundary is tested

Published Nov 6, 2026

You’re a forward deployed engineer working with Speak’s engineering team. The team is in the room.

The setting

offers , a platform where companies buy, set up and manage language-learning programs for their employees and get reports on how those programs are used.

Passing reporting tests and proving tenant boundaries are different claims.

Reviewers need visibility across reporting dependencies without treating generated tests as independent proof.

Who you’d be doing this for

“Finance asked why two department totals changed after the export. I spent my morning checking the employee lists again.”

Daniela Petrovic · Learning and Development Administrator · a character in this brief

Uses cohort reports to explain participation to department heads and finance.

What is at stake

Engineers reviewing enterprise reports disagree about what passing tests prove. You must decide when an AI check can mark a tenant boundary as tested, and when that claim still needs an engineer.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • tenant enforcement vs cross-layer coverage
  • representative fixtures vs learner privacy
  • cohort semantics vs executable assertions
  • broad dependency tracing vs bounded execution

Why Speak

Enterprise reporting joins Node.js handlers and Postgres queries before administrators use the figures to evaluate workplace learning.

Written with these in mind

Forward deployed engineersSolutions engineers with developer-workflow experienceEngineers focused on evaluation and verification

Not your kind of problem? 41 more at Speak, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Speak. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Full-stack Engineer (opens in a new tab)
    • You’ll work primarily in TypeScript across Next.js/React, Node.js, and Postgres, partnering with engineers in adjacent pods where the experience crosses team boundaries.
  • Full-Stack Engineer - Enterprise (opens in a new tab)
    • Designing and implementing backend services, APIs, and data models that support multi-tenant enterprise use cases
    • You’ll work across the B2B product surface — partner portals, reporting, B2B subscription mechanics, admin experiences, and learner features that require an enterprise touch.
  • Engineering Manager, Enterprise (opens in a new tab)
    • A strong technical background with hands-on experience in full-stack development and familiarity in our stack (TypeScript, React, Node.js, Postgres, BigQuery).
    • You will manage a team of engineers, guide the technical strategy for a variety of platforms—including our mobile app, L&D web portal, and custom integrations—and help shape a product used by millions of learners worldwide.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

The same setting, from another role

Each is set around Speak’s Speak for Business, written for a different role. They’re separate briefs, not the same scenario.