Engenheiro Avançado Implantado (todos os gêneros)

<h2>Your mission</h2>
<p>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.<br>
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.</p>
<h2>What You’ll Be Working On</h2>
<h2>Time-to-Value</h2>
<ul>
<li>First meaningful planning result within five working days of data access. This metric belongs to you.</li>
<li>You never hand extraction back to the customer as homework: you drive it together, on the call, in one session.</li>
</ul>
<h2>The Data Path, End to End</h2>
<ul>
<li>Drive extraction from the customer's ERP, then clean, map, validate, and load it reliably and repeatably.</li>
<li>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.</li>
<li>Write connectors and idempotent data pipelines in SQL and Python; ship reproducible imports, not throwaway spreadsheets.</li>
</ul>
<h2>Integration Architecture &#x26; IT Concept</h2>
<ul>
<li>Define the export path and cadence, clarify interface ownership, and answer SAP indirect-use, licensing, and security questions before they stall a trial.</li>
<li>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.</li>
</ul>
<h2>Configuration That Reflects Reality</h2>
<ul>
<li>Translate customer-specific planning requirements such as service levels, lead times, criticality hierarchies and reorder logic into PartsOS configuration.</li>
<li>The customer's manual judgment stays in charge; the AI augments, it doesn't overrule.</li>
</ul>
<h2>Trust Through Traceability</h2>
<ul>
<li>Every recommendation traces back to a raw ERP field and coexists cleanly with the customer's existing MRP/disposition logic.</li>
<li>Nothing unvalidated reaches the customer. You test in staging and catch the data defect before they do.</li>
</ul>
<h2>The Playbook</h2>
<ul>
<li>Turn one-off integrations into reusable templates that make the next onboarding faster.</li>
<li>Identify and hand reproducible product gaps to Engineering, clearly separated from implementation issues.</li>
</ul>
<h2>Working With Your CSM</h2>
<ul>
<li>Every account is a two-person team. The CSM owns the relationship, stakeholders, business case, and conversion; you own the data, the system, and Time-to-Value.</li>
<li>When the CSM brings the business goal, you translate it into configuration; when you