Analytics Engineer

Havenparkcommunities; Orem (UT); On-site; USD 110,000 - 150,000; Full time

Job summary

Havenpark Communities in Utah is building a modern analytics platform from the ground up. As an Analytics Engineer, you own the transformation layer, turning data from multiple systems into canonical facts and dashboards that business users can trust.

You will design the core data model with dbt, migrate legacy reports, and ensure data quality with tests. We value hands-on code ownership and a thoughtful approach to governance and AI-assisted development.

Qualifications

• Strong SQL with window functions, deduplication, and incremental logic.
• Ability to work with AI-assisted tooling and review outputs critically.
• Hands-on dbt experience, core/warehouse modeling, and CI practices.
• Experience with a cloud data warehouse, ideally Snowflake.
• Comfort with Git/GitHub and a PR-based workflow.
• Dimensional modeling fundamentals and data quality focus.

Responsibilities

• Own the transformation layer and turn source data into canonical facts and dimensions.
• Migrate legacy reports onto the new core model with reconciliation.
• Build the core data model in dbt and design defensible grain and SCDs.
• Ensure data quality with dbt tests and CI checks as release blockers.
• Collaborate across teams to integrate diverse data sources and govern semantics.

Skills

SQL

DBT

Snowflake

Git/GitHub

Dimensional modeling

Data testing

Tools

dbt

GitHub

Fivetran

Airflow

Job description

We're building a modern analytics platform from the ground up: a layered, well-tested data model in Snowflake that becomes the single source of truth for the business, and a governed semantic layer that lets stakeholders, not just analysts, ask questions and get trustworthy answers.

As an Analytics Engineer, you own the transformation layer. You'll turn messy source data from a dozen operational systems into canonical facts and dimensions, migrate legacy reports onto that clean foundation, and make the whole thing reliable enough that people stake real decisions on it.

How we work matters as much as what we build. We leverage AI heavily across our development workflow, authoring and refactoring SQL, building dbt models, writing tests, and moving work through our GitHub PR process. AI is a force multiplier here, not a crutch and not a black box.You own everything that ships under your name. That means you read every line, understand why it's correct, catch what the model got wrong, and stand behind the result in review. We don't write everything by hand anymore, but you can't own what you don't understand, so strong fundamentals are non-negotiable.

• Build the Core data model. Design and implement facts and dimensions in dbt following a disciplined staging → intermediate → core → mart architecture. Model slowly changing dimensions, handle mixed-grain snapshot sources, and make defensible grain and materialization decisions.
• Migrate legacy reporting onto Core.Reconstruct existing business-critical views and reports on top of the new model, reconciling outputs line-for-line so stakeholders can trust the cutover.
• Work fluently with AI in the loop. Use AI coding tools to accelerate model development, test writing, and the dbt/GitHub workflow, while critically reviewing every output, correcting it, and taking full ownership of correctness, performance, and style.
• Own data quality. Write dbt tests (generic, singular, and unit), establish contracts on data-out models, and treat a failing CI check as a release blocker, not a suggestion.
• Integrate diverse sources. Work across data from a myriad of sources, each with its own quirks, grains, and coverage gaps you'll need to understand and document.
• Build the semantic / AI-ready layer.Curate mart models and metric definitions with the metadata (certification, PII level, known issues) that powers governed self-service and agentic AI, so non-analysts can safely ask their own questions.
• Raise the bar on engineering practice.Small, reviewable PRs; a shared style guide; version control as the source of truth; documentation that the next engineer — or AI agent — can actually use.

Must-haves

• Strong SQL — you can read, write, andjudgeit. Window functions, deduplication, incremental logic, and grain are second nature, whether the first draft came from you or from an AI assistant.
• The judgment to workwithAI tooling, not be replaced by it: you can tell when generated SQL is subtly wrong, and you take ownership of fixing it.
• Hands-ondbtexperience (Core or Cloud): models, tests, macros, refs/sources, and a feel for layered project structure.
• Experience with a cloud warehouse, ideallySnowflake.
• Comfortable withGit/GitHuband a PR-based, review-driven workflow.
• Dimensional modeling fundamentals (facts, dimensions, SCDs) and the judgment to avoid over-engineering.
• A documentation and testing habit: you make your work legible and verifiable.

Nice-to-haves

• Experience using AI coding assistants (e.g., Claude Code, Copilot, Cursor) in a professional, review-gated workflow.
• ELT tooling (Fivetran, CData) and experience taming third-party source schemas.
• Semantic layer/metrics layer work, or experience preparing data for AI/LLM consumers.
• BI tooling (e.g., Power BI, Sigma) and partnering directly with report consumers.
• Domain exposure to real estate, property management, finance/GL, or operations.
• Python for ancillary tooling and automation.

• Greenfield with guardrails.You're building the platform, not babysitting legacy — but with real standards, code review, and CI from day one.
• AI-accelerated, human-owned.We give you the best modern tooling to move fast, and we trust you to own the outcome. Less time on boilerplate, more time on judgment.
• Your work ships decisions.The models you build directly drive how communities are run and capital is deployed.
• Craft is valued.Small diffs, clean models, and good tests are how we measure quality here — not heroics.