NetSuite Developer & Product Data Engineer
- Compensation
- Not disclosed
- Location
- Webberville, MI, US
- Work setup
- Not specified
- Seniority
- Not specified
- Employment
- Full time
- Experience
- Not specified
- Category
- Data engineering
- Posted
Skills
Must have
- You build things. Not because someone handed you a ticket, but because you saw the gap, sketched the fix, and had a working version running before anyone scheduled a meeting about it. You are comforta
- You also think in systems. You know a clever one-off script is a liability if nobody can tell where its data came from, and that a schema decision made in a hurry gets paid for by someone three years
- And you ship anyway. You can tell the difference between the version that is right and the version that is right enough for this quarter, and you choose well under pressure. You would rather get a cle
- Most people are strong on one of those and patient with the other two. We are looking for the person who holds all three at once and reads the tension between them as part of the work, not a frustrati
- You can do both halves: NetSuite development (SuiteScript) and product-data engineering (SQL or SuiteQL, plus Python or a comparable language for data work). Deep in one, solid in the other. You would
- You have done this before on large, messy datasets, at real volume and with real stakes.
- You design data structures and integrations that other people can rely on and understand later.
- You are legally authorized to work in the United States. We are not able to sponsor employment visas for this role.
- You can be on-site at our Webberville, Michigan location a few days per week, including quarterly company planning days.
Full description
NetSuite Developer & Product Data Engineer
Webberville, Michigan · Hybrid, a few days per week on-site · Full-time
Every part we sell starts as someone else's spreadsheet. Dozens of vendors, dozens of ideas about what a column called "size" means, and hundreds of thousands of parts listed on Amazon, eBay, Walmart and our own store that all depend on us getting that data right. Today that data lives in too many places. We want it to live in one: NetSuite, as the record for every part we carry, feeding each marketplace from a single clean source.
That is the job. Half of it is NetSuite development, the SuiteScript and SuiteQL you write yourself. The other half is product-data engineering, turning messy vendor catalogs into records a customer can trust when their machine is down and they need the right part the first time. If you have been waiting for a problem that is honestly both, this is it.
What product data means here
Supplier catalogs in every format a vendor can invent, item attributes, fitment and cross-reference data, validation rules, and the feeds that push all of it out to the marketplaces. Not analytics about a software product. The real catalog, and the plumbing that keeps it right.
The split, and what you own
A 50/50 role, by design: about half NetSuite development, about half data engineering. Routine item fixes and listing corrections stay with our listing team. You build and own the system underneath: the pipelines, the records, the validation, the integrations. You build it once, correctly, so it holds.
- NetSuite development: SuiteScript, SuiteQL, saved searches, custom records and fields, and the workflows that make NetSuite the system of record for product data.
- Vendor data ingestion: collecting, aggregating and normalizing supplier catalogs into clean, structured, trustworthy records.
- Marketplace data operations: building and maintaining the feeds and syncs that publish product data to Amazon, eBay, Walmart and our own store, with the validation and compliance checks that keep listings accurate.
- Integrations and APIs: connecting NetSuite, our marketplace channels and the tools around them so data moves reliably and nothing is re-keyed by hand.
A concrete first win: take one priority supplier feed that arrives today as inconsistent, half-trusted input and turn it into validated records publishing cleanly to every channel. Then do it again for the next one.
Who you are
You build things. Not because someone handed you a ticket, but because you saw the gap, sketched the fix, and had a working version running before anyone scheduled a meeting about it. You are comfortable being the person in the room who can actually write the script.