Senior Data Engineer

Fusion Worldwide

About The Position

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 "done" for a pipeline, notes on past mistakes, and approved project plans. We'd expect you to follow them and add to them. What We Build Has to Be Explainable A trader who disagrees with a number can see where it came from. Parameters and thresholds are stored as versioned data, and every output records which version it used. None are hard-coded in a transform. Anything an LLM generates comes with a plain-English reason and a link to the source field. Lineage is kept end to end, so you can trace a wrong number back to the row that caused it. Taking a Feature End to End We have a product manager, and you'd work with them on direction and priorities. They don't have to sit in the middle of every decision. Once you pick up a problem, you'll do most of the scoping, building the POC, iterating, and deciding when it ships. You'll do some of the product work yourself. That includes talking to the trader who raised the problem, deciding what the first version leaves out, and choosing when a rough version is ready to show them. Everything you work on gets a Jira ticket. You'll work in a light Agile process, with story point estimates. The product manager or business analyst writes most tickets, and you'll write your own for improvements, fixes, and iterations, using AI to draft them.

Requirements

Production data platform experience on platforms such as Databricks, Snowflake, Spark, or dbt.
8+ years building software, weighted toward backend and data engineering.
Expert SQL and deep experience with relational databases such as SQL Server, PostgreSQL, Oracle, or MySQL (specifically SQL Server).
Ability to read an execution plan, design indexes that hold up under load, and determine when a normalized model is inappropriate.
Experience writing back into a system of record, including transactional integrity, idempotency, and reconciliation.
API design experience, including designing APIs for applications not controlled by the designer, changing them without breaking them, and shaping them around UI needs.
End-to-end delivery experience, able to demonstrate features driven from idea through POC, build, iteration, and release.
Caching and performance engineering experience, including making slow things fast and explaining changes.
Proficiency with Git, code review processes, and CI/CD pipelines.
Understanding of data governance and security, including access controls, handling sensitive data, and meeting audit requirements.
Experience with production LLM systems, including post-shipping aspects like evaluation, guardrails, cost, and latency.
Day-to-day work with AI agents on production systems, with specifics on their benefits and failures.
Experience building auditable systems, including lineage, versioned parameters, and outputs that non-engineers can challenge.
Clear written communication skills, with experience writing many documents.

Nice To Haves

3+ years hands-on experience with a production data platform, including object modeling, building and shipping pipelines, and shipping an application that people use.
Python and PySpark experience, including identifying and correcting agent errors in transforms, window functions, or downstream contract breaks.
Dimensional modeling and schema design judgment.
Experience with entity resolution, master data, taxonomies, or knowledge graphs.
React experience.
Process mining experience.
Jira experience, including connecting to it with AI tools.
ERP integration experience.
Streaming and event-driven ingestion (Kafka, CDC) experience.
Experience in electronics distribution, supply chain, or industrial B2B data.

Responsibilities

Work with the object model covering companies, parts, offers, and demand signals, including adding object types, properties, and relationships.
Build and maintain ingestion from RMS, Azure SQL, HubSpot, and vendor APIs, along with the transforms, pipelines, and automations.
Build and maintain quality gates, including data expectations, freshness checks, and tests.
Tune performance across query plans, index design, materialization strategy, and caching.
Assist with incident response for pipeline or write-back failures, which may include on-call duties.
Work on the write-back path into RMS for scores, enrichment, resolved entities, and operational flags.
Handle idempotency, conflict handling, and reconciliation for system of record write-backs.
Design APIs for UIs in Web RMS, focusing on contracts, versioning, and performance.
Build custom applications.
Build agent workflows for tasks like triaging RFQs, picking pricing signals, and flagging offer anomalies.
Build and maintain agent setups, including instructions, tool connections, and output checks.
Build and maintain AI agents, including their instructions, data access, and error checking mechanisms.
Review and fix code produced by AI agents.
Follow and contribute to written standards, including runbooks and notes on past mistakes.
Ensure that built systems are explainable, with traceable lineage and versioned parameters.
Collaborate with a product manager on direction and priorities.
Take ownership of features from idea through POC, build, iteration, and release.
Communicate with stakeholders, including traders, to define requirements and gather feedback.
Create and manage Jira tickets for all work, using AI to draft tickets for improvements and fixes.
Participate in a light Agile process with story point estimates.