Supply Chain Systems Analyst

Most weeks tend to involve system analysis, configuration work, reporting development, and the steady cadence of cross-functional engagement — pulling system data for analyses, supporting configuration changes, sitting with IT and functional teams on system issues, building reports for supply-chain functions. You're often the bridge between supply-chain functional needs and the technology that runs them. System reliability and reporting quality anchor the operating view.

Friction tends to come from the configuration-and-business-process interaction — system changes affect business process, and the analyst navigates both vocabularies. Variance across employers is sharp: at major companies systems-analyst roles run in structured project methodology; at smaller firms the analyst may be the de facto systems-and-process owner.

The role tends to suit people who are systems-fluent, business-process literate, and patient with cross-functional implementation work. APICS CSCP and vendor-specific (SAP, Oracle, Manhattan) credentials anchor advancement. The trade-off is the technical-functional translation work — both sides expect fluency, and the analyst earns standing by speaking both languages credibly.