Answers are grounded in this paper and cite their sources.
Practice review reveals workflow and usability barriers in national computational infrastructure, highlighting the essential role of research software engineers as technical translators.
Research software engineering increasingly involves more than writing code. RSEs are often responsible for translating between domain researchers, infrastructure teams, and usable software systems that support reproducible research. At DAFNI, my role spans both front-end software engineering and researcher engagement. Working across these areas has highlighted how usability, accessibility, onboarding, and communication directly influence the success and reproducibility of computational research workflows. This talk reflects on lessons learned from supporting researchers using a national-scale research platform. I will discuss common barriers researchers face when interacting with research infrastructure, including workflow complexity, discoverability, inconsistent user experiences, and challenges in operationalising reproducible software practices. I will also explore how user feedback, support interactions, and iterative interface design can improve both software quality and researcher confidence. The presentation will argue that modern RSE work increasingly depends on hybrid technical and community-facing roles, and that these contributions should be recognised as core components of the research journey rather than secondary support activities.
No takes yet. Share an insight, caveat, or question.
Elizabeth Mamtsits (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: