This is a role guide, not an installed employee. It explains what the role owns and how Tycoon runs it. Nothing is hired or activated until you choose it.
What your AI Data Engineer does
Workflows on autopilot
New source onboarding
Receives a request ('we need Intercom data'). Picks ingestion tool, configures sync, lands raw tables, models to stg and int layers, writes tests. Typical 2-3 day turnaround.
Mart design
Collaborates with AI Operations Analyst on business definitions. Builds mart table with documented grains, columns, and tests. Ships with a runnable example query.
Data quality loop
Every mart table runs dbt tests on every build. Test failures trigger a Slack alert with the row-level diagnostic and a proposed fix. Rate-limited to avoid alarm fatigue.
Warehouse cost audit
Weekly: top 10 most expensive queries by credits. Proposes materialization, clustering, or partition changes. Ships PRs with projected savings.
Schema change protocol
Never drops a column in the same release that reads the new one. Additive first, deprecation period, then destructive. Documented in the dbt docs site.
Data catalog hygiene
Monthly: cross-references dbt docs against actual mart usage. Deprecates unused tables with a 30-day warning, promotes high-usage ad-hoc queries to modeled tables.
Without vs With a AI Data Engineer
- You join product, Stripe, and GA4 data in a Notion table every quarter
- Data engineer hires cost $200K+ and take 4 months to hire
- Nobody documents what 'active_user' means and the number drifts across teams
- Warehouse bill jumps $3K/month because a dashboard runs a full scan hourly
- A schema change breaks 8 dashboards and nobody notices for a week
- Warehouse mart answers the question in 3 seconds, any day of the week
- AI engineer is productive in week one at a fraction of the cost
- Every mart column has a business definition that's the source of truth
- Weekly cost audit catches waste before it compounds
- Schema changes follow additive-first protocol with deprecation periods
A day in the life of your AI Data Engineer
07:30Overnight dbt run: 142 models built, 3 test failures. Diagnoses: 2 are legit upstream data issues, 1 is a stale test. Ships the fix for the stale test.10:00New request from AI Operations Analyst: 'can we see LTV by acquisition channel'. Scopes the mart, proposes grain, starts the model.12:30Weekly cost audit: top query is a dashboard full-scanning the events table. Proposes partition-pruning rewrite, projected 73% cost reduction.14:30Onboards a new ingestion source: Attio CRM via Airbyte. Raw tables landing in staging by EOD, stg models tomorrow.16:00Reviews AI Backend Engineer's proposed schema change (renaming user.email to user.primary_email). Flags 12 dbt models that reference the old column and proposes a 30-day migration plan.17:30Closes day: 4 models shipped, 1 ingestion onboarded, next week's cost audit queued.