Data Architect at Niron Magnetics
Minneapolis, MN
$165,000–$190,000from the description
Jul 14, 2026
Minneapolis, MN
Jul 21, 2026
What this job asks for AI summary
A senior, hands-on technical leadership role responsible for designing and evolving the end-to-end enterprise data architecture at a growing magnet manufacturing company. The position owns the expansion of an existing Microsoft Fabric-based data lakehouse, covering ingestion, modeling, governance, and integration with systems such as ERP and manufacturing tools, while enabling analytics, reporting, and AI/ML workloads. It suits an experienced data architect comfortable driving architectural strategy in a compliance-sensitive, early-stage industrial environment.
Senior level · 10+ years · Minneapolis-St. Paul-Bloomington, MN-WI · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 10 people in the Minneapolis-St. Paul-Bloomington, MN-WI area plausibly meet what this posting asks for (database architects). range 4–15
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $136,957 (middle half $115,209–$161,832). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The role is titled 'Sr. Enterprise Data Architect' and is squarely focused on designing and owning the end-to-end data estate (lakehouse, modeling, governance, pipelines) — 15-1243 Database Architects is the closest SOC, though the breadth of platform and AI/ML enablement work makes 15-1299 a reasonable runner-up.
Databricks is listed in the requirements section but with the qualifier 'strongly desired' rather than firm gating language, so it is treated as preferred rather than a hard gate.
D365 F&O integration experience is listed as 'preferred' in the requirements section, so it is treated as preferred.
R and Spark appear in the requirements section explicitly flagged as 'a plus', so they are treated as preferred.
The 'Nice to Have' section lists manufacturing/industrial experience, regulated-environment experience, an advanced degree, time-series/OT/sensor data experience, AI/ML and RAG workload experience, and clean-tech passion — all treated as preferred. The advanced degree is only listed under Nice to Have, so the degree requirement is set to None.
Message queues and webhooks are named alongside REST/GraphQL as integration mechanisms; they are captured under the REST skill entry as part of the same integration-pattern requirement rather than as separate skills, since they name no specific product.
The role does not appear to be remote; the posting is headquartered in Minneapolis, MN with no remote language.
Ignored 2 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): data governance, D365 Finance & Operations.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.