RSEs in Research? RSEs in IT?: Finding a suitable home for RSEs

TL;DR

This paper explores the optimal organizational placement of Research Software Engineers within academic and research institutions, analyzing various models and their advantages and disadvantages.

Contribution

It provides a comparative analysis of different institutional placements for RSE teams, offering insights into their benefits and challenges.

Findings

Central IT placement offers technical support advantages.

Embedding RSEs in research groups fosters close collaboration.

Ad hoc setups vary widely in effectiveness.

Abstract

The term Research Software Engineer (RSE) was first used in the UK research community in 2012 to refer to individuals based in research environments who focus on the development of software to support and undertake research. Since then, the term has gained wide adoption and many RSE groups and teams have been set up at institutions within the UK and around the world. There is no "manual" for establishing an RSE group! These groups are often set up in an ad hoc manner based on what is practical within the context of each institution. Some of these groups are based in a central IT environment, others are based in research groups in academic departments. Is one option better than another? What are the pros and cons of different options? In this position paper we look at some arguments for where RSE teams fit best within academic institutions and research organisations and consider whether there is an ideal "home" for RSEs.