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.
Tonight's separation puts live reporting and a clean data boundary in direct conflict.
The operations sponsor protects reporting continuity, while the security sponsor requires shared records to leave the subsidiary's environment.
Who you’d be doing this for
“I checked three reports this morning and found parent-company records. Tonight I'm supposed to tell operations they're ready.”
Mazen Ahmadi · Subsidiary Data Engineering Lead · a character in this brief
Responsible for keeping the subsidiary's reporting usable after access to the parent's Oracle environment ends.
What is at stake
A subsidiary loses shared Oracle access tonight with three of 12 reporting workloads still crossing the separation boundary. You must weigh reporting continuity and renewal value against a data boundary the customer's security sponsor will not relax.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- live reporting vs complete data separation
- renewal scope vs validated customer value
- historical completeness vs permitted retention
- last extraction opportunity vs costly verification
Why Fivetran
Managed ingestion into Snowflake and transformations in dbt underpin the reporting workloads attached to the customer's upcoming renewal.
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)
- Own Mutual Success Plans and shape Mutual Account Plans with the AE, mapping whitespace across business units, subsidiaries, and use cases
- Lead technical validation of the most complex new workloads, including workshops and, where necessary, proofs of concept (POCs)
- 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 an irreversible change forced by a fixed date.
The customer has 21 days to retire its existing feed, and product and finance already report different retention results.
You must weigh reporting continuity against a definition that remains trustworthy after the cutover.
Approval workflows across 240 customer projects are paused after owners changed roles.
You must weigh immediate delivery continuity against an access decision the customer cannot casually undo.
The customer cannot link enough workload credential issuances to named reviewers before an audit deadline.
You must weigh a defensible evidence plan against a competing path that promises faster consolidation.
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 make a hard-to-reverse product decision feel clear and defensible before customers are bound by its consequences.
Deleted records now eat 31% of retention cost, and recovery is slowing in large bases before a fixed storage migration.
You have to cut the cost without removing data that customers expect to get back.
Routing differs by region, so time to the right owner varies threefold, and the slowest paths enter the next filing peak unchanged.
You decide what must be true before launch, since the new path is hard to undo.
A migration review found 14,600 old invoices the new service calculates differently, 430 with conflicting exemption evidence.
You decide what counts as correct before a switch you cannot undo.
