Data Architect

UtiliSave LLC•New York, NY

9h•Remote

About The Position

The pioneer in forensic utility bill auditing. Since 1991 we've recovered $700M+ for 16,000+ commercial buildings, on pure contingency. No recovery, no fee. We're growing, and our in-house software and 35 years of audit data are the engine behind that recovery. Right now we're moving the whole company to a modern, AI-enabled workplace. That means a new CRM built in-house on, client and utility portals, Microsoft 365 and SharePoint across every department, and AI tools that help our auditors find and recover more. Every one of those projects runs on data, and we need someone to own it. This is a hands-on role. You'll design the data model for the new platform, clean up and migrate decades of data out of SQL Server, and build the integrations that connect our systems. You'll also keep our existing applications healthy while we get there, because the legacy systems run the business today. You get to work on new technology and carry a working business through the change at the same time. What you'll be part of A real rebuild. We're replacing a legacy platform with a modern Microsoft stack, and the data model you design is the one the company will run on for years. AI is part of how we work. Our developers use Claude Code and similar tools every day, and our AI team is building tools that depend on clean, well-governed data. You'll be the person who makes that data ready. Real ownership on a small team. You'll work directly with the development, AI and IT teams. Decisions don't sit in a queue, and your work shows up in the business quickly. Modern and legacy, side by side. You'll learn and support the systems that run the business today while building what replaces them, so nothing gets lost along the way.

Requirements

5+ years in data engineering, data architecture or database development.
Strong hands-on SQL Server: T-SQL, schema design and performance tuning.
Experience with Dataverse or the Dynamics 365 data model: tables, relationships, keys and security roles.
Built and supported production integrations using REST APIs, Azure Data Factory, Azure Functions, Power Automate or similar.
Data modeling and data quality in practice: you've migrated a legacy database, written matching and dedupe rules, and set up a single source of truth.
Data security experience: role-based access and permissions across databases, Microsoft 365, SharePoint and Entra ID.
Power BI data modeling (semantic models, DAX), beyond building visuals.
Working knowledge of Microsoft 365 and SharePoint: libraries, metadata, permissions and the Graph API.
Demonstrated, hands-on use of AI-assisted development tools in real projects, not just familiarity. Claude Code preferred; Copilot, Cursor or similar accepted.
Able to plan data flows and explain them clearly, in writing and out loud, to developers and non-technical colleagues.
Comfortable working independently in a small, fully remote team.

Nice To Haves

C#/.NET experience, including working inside legacy applications.
Python for data work.
Utility, energy or billing data experience, including large time-series or meter data.
Integrations with QuickBooks Online or other finance systems.
Microsoft certifications such as PL-600 or DP-600.

Responsibilities

Own the company's data model across SQL Server and Dataverse, and define the target model for our Dynamics 365 CRM before data is migrated into it.
Plan and run data cleanup and migration: one trusted ID for each account, property, utility and contact, clear matching and dedupe rules, and intake checks that stop bad data from coming back.
Plan, design and build data flows and integrations between SQL Server, Dataverse, SharePoint, finance systems and our AI platform, using APIs, Azure services and Power Automate.
Protect the data: design and maintain permissions for staff, clients, auditors and AI tools across SQL Server, Dataverse, SharePoint and Entra ID.
Own the reporting data layer, including Power BI semantic models and the history tracking we need to measure cycle times and outcomes.
Support and maintain our existing applications and databases during the transition, so the business keeps running while the new platform comes online.
Bring production integrations under standard controls: source control, code review, test environments and documentation.
Use AI-assisted tools (Claude Code, GitHub Copilot, Cursor or similar) as a normal part of your work for SQL, pipelines, testing and documentation.
Track all work in JIRA, with estimation and task breakdown before development begins, and write documentation as part of delivery.