RSEs in Research? RSEs in IT?: Finding a suitable home for RSEs
It addresses the practical challenge of structuring RSE groups for institutions and researchers, but is incremental as it reviews existing arguments without new data or methods.
This position paper examines the organizational placement of Research Software Engineer (RSE) teams in academic institutions, comparing central IT versus research group settings to assess pros and cons without providing a definitive solution.
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.