Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Analytics Engineer Source-Aware Guide
Defines source-aware analytics engineering and governed data transformation, evidence handling, and action boundaries.
Read the fileOverview
Analytics Engineer overview
Use this bundle to prepare source-aware analytics engineering and governed data transformation analysis and a reviewable analytics engineering delivery brief.
Read the fileWorkflow
Analytics Engineer source-aware triage
1. State the requested decision or artifact. 2. Inventory evidence: business question, stakeholder, decision, and acceptance criteria, warehouse, platform, environment, repository, and tool.
Read the fileTemplate
analytics engineering delivery brief
Review-ready artifact for analytics engineering and governed data transformation, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Analytics Engineer work, plus teams reviewing its decisions and outputs
- Teams working in Data and analytics, Software, Financial services
When to use it
- An Analytics Engineer task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Prepare an analytics engineering delivery brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready recommendation with explicit verification and approval boundaries.
What it helps produce
- analytics engineering delivery brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Analytics Engineer work by producing analytics engineering delivery brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1243.01, then confirm that the reference is current and applicable. Inspect Analytics Engineer Source-Aware Guide before drafting.
Context path: bundles/roles/analytics-engineer
What the bundle includes
Frameworks
- source-evidence matrix
- analytics engineering and governed data transformation review matrix
- qualified-review gate
Evaluations
- Analytics Engineer source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Use the cited official, originator, standards, or professional sources for general analytics engineering and governed data transformation context; local facts, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for business question, stakeholder, decision, and acceptance criteria, warehouse, platform, environment, repository, and tool versions, source data contracts, freshness, quality, ownership, and sensitivity, models, grain, keys, joins, transformations, tests, and lineage, metric and semantic definitions, dimensions, filters, and reconciliation, and review, CI, deployment, access, documentation, monitoring, and incident evidence.
- Do not infer source-data meaning, model grain, join behavior, metric definition, test result, and production state.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, and other sensitive data.
- Require explicit confirmation before querying or exposing sensitive data, changing production models or metrics, deploying transformations, changing access, or certifying data products without review.
- Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to accountable reviewers.