The setting
's lets data teams build, transform, govern and validate their data workflows, either in a web browser or with command-line tools.
Friday's adoption review depends on reporting workloads that still point to development.
Customer-led configuration protects analyst independence, while specialist configuration protects the reporting deadline.
Who you’d be doing this for
“I told our controller the reports were ready, then spent Monday asking three analysts to run them manually.”
Yamini Patel · Finance Analytics Lead · a character in this brief
Coordinates the four departmental reporting owners and presents adoption progress to the customer sponsor.
What is at stake
Three finance departments still run reports manually after completing dbt training. You weigh customer ownership through a workshop against specialist configuration in the only available session.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- analyst independence vs. predictable completion
- workshop time vs. reporting obligations
- specialist capacity vs. customer effort
- training completion vs. demonstrated adoption
Why Fivetran
Expansion across finance departments depends on turning completed dbt training into accepted, scheduled reporting in Snowflake.
Written with these in mind
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.
- Sr. Customer Solutions Architect (opens in a new tab)
- Lead technical validation of the most complex new workloads, including workshops and, where necessary, proofs of concept (POCs)
- Shape the account plan and own the technical side of the expansion pipeline, translating executive-level customer initiatives into scalable data workloads and solutions
- Customer Solutions Architect (Denver) (opens in a new tab)
- Senior Technical Instructor (US East) (opens in a new tab)
- It’s an exciting time to join us: we’re creating a company with the scale, talent, and technology to help more organizations put their data to work with greater speed, confidence, and impact.
- Deliver live, world-class instruction to train and onboard dbt - Fivetran customers, partners, and GSIs in small (~10), large groups (up to ~30) and webinar audiences (50 - 200)
- Customer Solutions Architect (Austin) (opens in a new tab)
- Customer Solutions Architect (NYC) (opens in a new tab)
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about people starting something and never quite finishing it.
Four of six researchers still need a developer to finish their first task.
You must weigh tailored guidance for Friday against a reusable walkthrough that reaches future users.
Eight of twelve consulting analysts rebuild their generated briefings despite acceptable content.
You must weigh a tailored skill against teaching flexible inputs in the only working session available.
Only six of eighteen designer-developer pairs finished an asset handoff independently.
You must weigh keeping the intended workflow against giving everyone enough time to practice a narrower one.
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.
Generated dbt changes can pass a quick diff review while missing a downstream contract or lineage dependency.
You must weigh faster review flow against the evidence reviewers need to trust a promotion.
Plausible AISQL answers are reaching warehouses without a dependable link to approved metric definitions.
You must weigh fast containment against preserving useful answers for ambiguous analyst questions.
Changed metric definitions are reaching the catalog while AISQL answers from stale context.
You must weigh faster refreshes against query latency and needless rebuilds.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn observed user friction into a fast, confident decision that visibly restores a better experience.
Managers export disconnected monitoring and publishing data 2.4 times more often when using both surfaces.
You have to weigh a focused first view against broader reporting expectations.
Marketing specialists are rebuilding near-identical campaigns location by location for multi-unit groups.
You must weigh brand consistency against the local flexibility restaurant managers need.
Search-led product-detail views are stuck at 18% despite rising search volume.
You have to weigh a sharper discovery configuration against the customer engineers’ need to validate it safely.
