Data Warehouse Engineer

Data Engineer/Architect

Southeast Wisconsin (Hybrid, 3 days onsite)

We are hiring a Data Architect for a growing company in southeast Wisconsin.

This is a build, not a maintenance job. The company has grown through acquisition, each business runs its own ERP, and they are standing up a single data platform to bring all of it together. You would be the technical owner of that build.

What you will do

Design and build the data lake and the pipelines feeding it, pulling Sales, Purchase, GL, Inventory, AR and AP data from multiple ERP systems.

Build the curated and semantic layers on a medallion architecture, creating one standardized data model and data dictionary across every entity.

Write custom connectors for legacy source systems that have no native integration.

Build predictive and analytical models on top of the curated data for cost savings, supplier pricing comparison, and cross-sell analysis.

Partner with Finance and Operations on how the data gets defined and mapped.

Build the reporting and dashboards leadership will actually run the business on.

What we are looking for

10+ years building enterprise data platforms with hands-on data modeling and ETL/ELT across many different source systems.

Real depth in Databricks, Snowflake, BigQuery or a comparable cloud platform. This is the part we will dig into.

Experience designing semantic layers and curated models on a layered or medallion architecture.

Comfort with financial and operational data. Chart of accounts, journal entries, invoices, sales orders, purchase orders. You do not need an accounting background, but you should have built reporting on this kind of data before.

Strong SQL and Python.

Nice to have

AI or machine learning applied to curated data for forecasting, anomaly detection or spend analysis.

Multi-entity or M&A data integration experience.

Microsoft Dynamics AX or D365 Finance & Operations.

Power BI, including DAX and Power Query.

Distribution or manufacturing industry data.

Why this one is worth a look

Greenfield. There is no legacy platform to inherit or defend, and the budget is already approved.

You own the architecture. This is not a role where you implement someone else's design.

The office sits far enough north that if you are anywhere between Milwaukee and the north suburbs, you are looking at a short commute instead of a haul into the city.