Obtenez une réponse de cet employeur
Votre CV et votre lettre de motivation, adaptés exactement à ce que l’employeur recherche.
Atomic builds data integrations for supply chain customers. This role owns the data ingestion layer across multiple deployments, wiring ERP, WMS, and partner systems to produce clean, trustworthy data in real time.
You’ll work directly with customers on technical conversations, manage several pipelines in parallel, and apply playbooks to accelerate delivery while maintaining high quality. Based in NYC area, hybrid work may apply.
Most companies still plan their supply chains, meaning quantities, mix, allocations, and timing, in spreadsheets or legacy software. The spreadsheets break as soon as the business moves quickly. The legacy suites take a year to implement and frequently lose to the spreadsheets anyway.
Atomic is rebuilding the brain behind the American supply chain. By tackling operations optimization from first principles with an AI-native stack, they deliver unprecedented results at breakneck speed for their customers. Customers include DoorDash, HelloFresh, Archer Meat Snacks, Starface World, LMNT, OOFOS, Cora, and Chomps.
The founders lived this problem before they built the solution. Michael Rossiter and Neal Suidan built Tesla’s end-to-end supply chain orchestration system from scratch during the Model 3 ramp, after watching a company that size run on spreadsheets that could not keep up with how fast the business moved. Revenue has grown roughly 10x this year.
Every Atomic deployment starts with a customer’s data, and that data arrives however it happens to exist: an ERP export, a WMS feed, a partner API, an emailed spreadsheet, a file someone has been maintaining by hand for six years. Nothing moves until it’s wired in, normalized, and trustworthy.
This role owns that layer across the customer base. Where the standard Forward Deployed Engineer goes deep on one complex engagement at a time, you’d go broad — running integrations and pipelines for several customers in parallel, applying playbooks where they exist and improving them where they don’t.
It’s still a customer-facing job. You’d be on calls with the customer’s technical teams working out what their systems actually contain, explaining what’s feasible, and telling them directly when something is broken on their end or when a timeline is slipping. The engineering team builds and maintains the platform foundation; you connect each customer to it and make the data underneath it reliable.
The hard part isn’t the code. Customers hand you data in every format and state of cleanliness, tell you what they think they need, and some of it will be wrong. Figuring out what to actually build, and building it fast, is what you'll be doing.