Senior Data Engineer

Role Summary Fusion Worldwide is a global open market distributor of electronic components. When a supply chain breaks because of an allocation, a shortage, or a part going end-of-life, we're who the world's largest manufacturers call. That business runs on knowing things: which companies are real and active, which parts substitute for which, who is likely to need what. Our traders make those calls in hours, using what the platform shows them. We run a production data and intelligence platform. RMS is our system of record, a custom internal ERP we build and maintain. Every order, quote, and transaction lives there. Our platform sits on top. It reads from RMS, enriches and models that data, and writes operational results back. Tech Stack Data: Microsoft SQL Server, Azure SQL Languages: Python, PySpark, SQL, TypeScript AI: Claude connected directly to our platform for agentic development Applications: Custom applications in React, APIs consumed by Web RMS Integration: RMS, HubSpot, vendor APIs Cloud: Microsoft Azure Work management: Atlassian (Jira, Confluence) Platform & Data Work with the object model covering companies, parts, offers, and demand signals. That includes adding object types, properties, and relationships as the data needs them. Build and maintain ingestion from RMS, Azure SQL, HubSpot, and vendor APIs, along with the transforms, pipelines, and automations behind it. Build and maintain the quality gates, including data expectations that fail the build, freshness checks against declared SLAs, and tests that catch problems nobody would otherwise notice. Tune performance across query plans, index design, materialization strategy, and caching. Help with incident response when pipelines or write-backs break, which may include on-call. System of Record Write-backs Work on the write-back path into RMS. Scores, enrichment, resolved entities, and operational flags get written back to the system of record. Handle idempotency, conflict handling, and reconciling the two sides when they disagree. APIs, Applications & AI Design the APIs that UIs in Web RMS use to pull platform data. You work on the contracts and the versioning, and you make sure the APIs are fast enough for a UI. Build custom applications. Build agent workflows that read the object model and act on it, such as triaging inbound RFQs, picking out pricing signals, and flagging anomalies in offers. Build and maintain the agent setup the team develops with, including instructions, tool connections, and the checks on agent output. How We Work Our team built this platform with AI agents, and you'd keep working that way. We're rolling out a federated team model, and this role sits on the core data platform team. Claude connects directly to our platform and writes transforms, queries our data, runs audits, and reads the object model as it goes. You'll have a budget for AI tooling and compute, and we won't make you fight for model access. Agents write most of the code. You build and maintain the agents, including their instructions, the tools and data they can reach, and the checks that catch their mistakes. You review what they produce and fix it when it's wrong. A few things that have gone wrong here: a scoring pass quietly stopped running. An LLM we used to check output lost part of its prompt and started approving everything. A library upgrade changed a default setting and turned off a live feature, and no test caught it. We want someone who has used agents heavily on production systems, had them fail, and changed how they work because of it. Leave your ego at the door. Everyone on the team does hands-on work, including the tedious parts. We're not interested in self-promotion. If most of your AI experience is posting about it on LinkedIn, this role isn't a fit. We'll ask what you built, what broke, and what you'd do differently. People who do well here give credit freely and say so when they're wrong. You'll inherit written standards, including runbooks that define…

View the full posting and apply