Exploring CoCo Challenges in ML Engineering Teams: Insights From the Semiconductor Industry
Not on the map. Why?
Abstract (arXiv)
The integration of machine learning (ML) into complex software systems has increased challenges in collaboration and communication (CoCo) of the teams building these systems. ML engineering (MLE) teams often involve diverse roles, ML engineers, data scientists, software engineers, and domain experts, each bringing unique goals, experiences, and jargon. These interdisciplinary dynamics can make it challenging to deploy, reproduce, and maintain ML-enabled systems over the long term. Previous studies have uncovered several CoCo challenges and practices, but most have focused on software-centric companies, leaving limited empirical understanding of how these dynamics unfold in hardware-centric contexts. In hardware-centric environments, CoCo challenges are shaped by additional constraints such as strict data governance, long development cycles, and tight coupling with physical processes, which amplify coordination complexity and reduce flexibility. To strengthen empirical understanding in such settings, we present a qualitative investigation of MLE teams within a global semiconductor company, where ML-enabled systems and manufacturing processes introduce additional complexity. We interviewed 12 practitioners regarding CoCo practices, tools, challenges, and approaches. Through analysis, we identified 16 recurring challenges, with unclear roles and responsibilities emerging as the most critical, and common practices and recommendations practitioners considered effective in mitigating CoCo problems. While grounded in a single organizational context, our findings align with known issues in interdisciplinary ML-enabled systems development, but also demonstrate how these challenges manifest differently under hardware-driven constraints. Our results highlight directions for future research and tool support to strengthen CoCo in MLE projects and ensure the success of ML-enabled systems.
Key facts. No citing papers in the map yet (data through 13 Oct 2026). Builds on 12 of its 41 references that are in the map. First posted on arXiv 8 May 2026.
Builds on
12 of 41 references.
References · 12
- 2018Datasheets for Datasetscited by 1,377
- 2018Model Cards for Model Reportingcited by 1,076
- 2020Improving Reproducibility in Machine Learning Research (A Report from the NeurIPS 2019 Reproducibility Program)cited by 319
- 2021Beyond Expertise and Roles: A Framework to Characterize the Stakeholders of Interpretable Machine Learning and their Needscited by 64
- 2021Collaboration Challenges in Building ML-Enabled Systems: Communication, Documentation, Engineering, and Processcited by 56
- 2021How AI Developers Overcome Communication Challenges in a Multidisciplinary Team: A Case Studycited by 29
- 2021Characterizing and Detecting Mismatch in Machine-Learning-Enabled Systemscited by 19
- 2020Machine Learning Explainability for External Stakeholderscited by 17
- 2021Reinforcement Learning for Process Control with Application in Semiconductor Manufacturingcited by 4
- 2024Naming the Pain in Machine Learning-Enabled Systems Engineeringcited by 3
- 2024Towards Effective Collaboration between Software Engineers and Data Scientists developing Machine Learning-Enabled Systemscited by 3
- 2023An Exploratory Study of V-Model in Building ML-Enabled Software: A Systems Engineering Perspectivecited by 2
Built on by
Not cited yet.