Forward Deployed Engineer (all genders)
PARTSCLOUD GmbH
Use the employer link to read the full source listing and submit your application.
Listing data may include public employer ATS feeds and Jobs by Adzuna.
Before you apply
The decision-making details job seekers want first
We pulled the strongest signals from the listing so you can quickly judge fit, compensation, and what the company expects before opening the full source post.
Compensation
Salary & market context
Salary not listed
Requirements
Top requirements
- 3–8 years in a hands-on, customer-facing technical role like solutions engineering, implementation, forward-deployed, or data engineering where you delivered working outcomes, not just specs.
- Strong with data: SQL and Python for transformation; you can trace a planning output back to a raw ERP export.
- You reason about any industrial ERP's data model rather than knowing one system's screens.
- You solve in the room with customers and own the result; your energy comes from fixing the real problem, not from working a ticket queue.
Perks & setup
Benefits candidates care about
- On-site in Stuttgart, 4 days/week , with flexible hours.
Why candidates care
Benefits & perks
- On-site in Stuttgart, 4 days/week , with flexible hours.
Start here
Requirements
- 3–8 years in a hands-on, customer-facing technical role like solutions engineering, implementation, forward-deployed, or data engineering where you delivered working outcomes, not just specs.
- Strong with data: SQL and Python for transformation; you can trace a planning output back to a raw ERP export.
- You reason about any industrial ERP's data model rather than knowing one system's screens.
- You solve in the room with customers and own the result; your energy comes from fixing the real problem, not from working a ticket queue.
- Fluent in German and English.
- Nice-to-have
- Direct SAP exposure (ECC / S/4HANA, PM or MM) is useful, but not the point: we are not hiring an SAP consultant.
- Microsoft Business Central, proALPHA, or other Mittelstand ERPs.
Responsibilities
What you'll do
- The moment a contract is signed, you own the path from raw, undocumented ERP data to the first trustworthy PartsOS planning result.
- You are the technical half of a two-person team: the Customer Success Manager owns the relationship and the business case; you own the system and the speed.
- Build robust transforms that handle 150+ columns, wrong currencies, duplicates, and hidden sheets, flagging every assumption and validating with the customer's system owner instead of guessing.
- Reason about any industrial ERP's data model where demand, stock, lead times, and BOMs live whether it's SAP, Business Central, proALPHA, or a homegrown system.
- Configuration That Reflects Reality Translate customer-specific planning requirements such as service levels, lead times, criticality hierarchies and reorder logic into PartsOS configuration.
- The CSM owns the relationship, stakeholders, business case, and conversion; you own the data, the system, and Time-to-Value.
Role snapshot
About the role
Your mission
You make customer value technically real. The moment a contract is signed, you own the path from raw, undocumented ERP data to the first trustworthy PartsOS planning result. And you get there fast: first real value within five working days of getting access to a customer's data.
You sit with maintenance, spare-parts, and supply-chain teams in real factories, open the SAP export nobody documented, and turn it into a plan they can run. You are the technical half of a two-person team: the Customer Success Manager owns the relationship and the business case; you own the system and the speed. Time-to-Value is your number.
What You’ll Be Working On
Source text