The setting
's extracts data from source systems and loads it into a customer's data warehouse, ready to query. Fivetran engineers write the connectors that link each source.
Six working workloads have only two accepted reporting handoffs.
Departmental ownership protects continuity, while centralized reporting protects scarce time before the data engineer's leave.
Who you’d be doing this for
“I've sent the same four extracts again this morning, and I'm supposed to be on leave tomorrow.”
Zhen Kobayashi · Central Data Engineer · a character in this brief
Maintains the customer's six reporting workloads and still supplies extracts to four departments.
What is at stake
Four departments still request manual extracts despite having working reports. You must weigh departmental ownership against a centralized service that needs less customer preparation.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- departmental independence vs centralized continuity
- specific practice vs limited session time
- deployed workloads vs accepted business outcomes
Why Fivetran
Healthy ingestion into Snowflake and working dbt outputs have not yet translated into accepted departmental use.
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)
- Shape the account plan and own the technical side of the expansion pipeline, translating executive-level customer initiatives into scalable data workloads and solutions
- Design enablement programs and workshops for large, distributed customer teams, and turn the best ones into reusable programs for the CSA team
- Customer Solutions Architect (Denver) (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.
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.
Forty portfolio leads are bypassing Project Overview and asking for Slack summaries instead.
You must weigh a fast familiar path against rebuilding the shared review habit.
The same setting, from another role
Each is set around Fivetran’s Fivetran data pipeline platform (managed ELT), written for a different role. They’re separate briefs, not the same scenario.
Completed connector runs are leaving some warehouse tables behind when morning reporting begins.
You decide where the system's reading of a failed run stops and the on-call engineer's own check across traces, run history, and pull requests begins.
Large reloads can consume the same warehouse window that scheduled reporting depends on.
You have to weigh a useful estimate against the risk of overstating what past runs can predict.
Duplicate completed runs are loading the same batch twice into customer warehouses.
You must weigh retry recovery against a permanent definition of a completed run.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn confusing, fragmented technical systems into something the people relying on them can understand and trust.
Growth sellers are revisiting call records because key qualification details are thin or unsupported in Salesforce.
You decide where the draft stops and the seller starts: who fills a qualification field from a call record, who confirms its source link, and who writes the proposed next step.
Health-system opportunities stall after first meetings, even when the discovery notes are complete.
You must decide where the AI's work on those notes ends and where the seller takes over what a care-management leader reads in the proposal.
Eleven producers appear complete in the dashboard, but only seven pass migration checks.
You must weigh a timely wave against publishing a readiness view people cannot trust.
