First-time day at Fivetran

Refresh metric context while AISQL still serves old logic

Published Oct 22, 2026

You’re the ai / ml engineer. Your team is in the room.

The setting

's lets data teams build, transform, govern and validate their data workflows, either in a web browser or with command-line tools.

The catalog reflects a new metric definition while AISQL still reasons from the old one.

Fast context refresh protects governed answers, while unnecessary rebuilds add latency and compute cost.

Who you’d be doing this for

“I changed the definition this morning, and the next answer still used last week's logic.”

Petr Markovic · Analytics Engineer · a character in this brief

Maintains governed dbt metrics used by analysts and downstream AI workflows.

What is at stake

Changed metric definitions are reaching the catalog while AISQL answers from stale context. You must weigh faster refreshes against query latency and needless rebuilds.

Why it isn’t already fixed

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

  • fresh metric grounding vs query latency
  • targeted invalidation vs operational simplicity
  • fast release vs verified evaluation evidence
  • catalog updates vs retrieval consistency

Why Fivetran

AISQL depends on dbt metric definitions to produce warehouse-native SQL that analytics engineers can trust.

Written with these in mind

LLM systems engineerML platform engineerretrieval and evaluation specialist

Not your kind of problem? 54 more at Fivetran, 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 Fivetran. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Staff R&D Software Engineer, Fivetran AI · no longer posted
    • Drive the AISQL capability forward: natural language to SQL grounded in dbt metric definitions, executed natively against the warehouse
    • Research emerging techniques in retrieval, reasoning, and agentic AI, and decide what’s actually worth pursuing for Fivetran AI’s roadmap — then convince others
  • Sr. Principal AI Systems Architect (opens in a new tab)
    • This role owns the architecture behind the analyst AI system, including metadata contracts, tool interfaces, context assembly, prompt and skill orchestration, evaluation loops, and the operational patterns that make agents useful in real workflows instead of isolated demos.
    • Design retrieval and context strategies that give the model the right information at the right time with strong cost, latency, and quality tradeoffs.
  • Senior R&D Software Engineer, Fivetran AI · no longer posted

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.

Similar problems at other organizations

Like this one, each of these turns on fixing one thing without breaking another.

The same setting, from another role

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

Other problems with a similar purpose

In each of these, as in this one, the aim is to build machine-learning systems that earn trust by staying explainable where their errors carry real consequences.