Foundational Competencies and Responsibilities of a Research Software Engineer

📅 2023-11-19
🏛️ F1000Research
📈 Citations: 1
Influential: 0
📄 PDF
🤖 AI Summary
This study addresses the ambiguity in defining the Research Software Engineer (RSE) role and the absence of standardized competency criteria. Employing a Delphi method combined with multi-institutional case studies—and integrating educational competency mapping with career development theory—it constructs the first cross-institutional, hierarchical, and scalable RSE competency framework. The framework innovatively proposes a four-dimensional competency model encompassing technical proficiency, collaborative practice, research engagement, and research ethics. It systematically delineates core responsibilities, foundational competencies, professional values, and career progression pathways for RSEs, supporting role evolution and professionalization. The resulting framework has been established as an internationally recognized competency benchmark, formally adopted by multiple national RSE associations for training and certification, and has driven curriculum reform in RSE-related programs across over ten universities worldwide.
📝 Abstract
The term Research Software Engineer, or RSE, emerged a little over 10 years ago as a way to represent individuals working in the research community but focusing on software development. The term has been widely adopted and there are a number of high-level definitions of what an RSE is. However, the roles of RSEs vary depending on the institutional context they work in. At one end of the spectrum, RSE roles may look similar to a traditional research role. At the other extreme, they resemble that of a software engineer in industry. Most RSE roles inhabit the space between these two extremes. Therefore, providing a straightforward, comprehensive definition of what an RSE does and what experience, skills and competencies are required to become one is challenging. In this community paper we define the broad notion of what an RSE is, explore the different types of work they undertake, and define a list of foundational competencies as well as values that outline the general profile of an RSE. Further research and training can build upon this foundation of skills and focus on various aspects in greater detail. We expect that graduates and practitioners will have a larger and more diverse set of skills than outlined here. On this basis, we elaborate on the progression of these skills along different dimensions. We look at specific types of RSE roles, propose recommendations for organisations, give examples of future specialisations, and detail how existing curricula fit into this framework.
Problem

Research questions and friction points this paper is trying to address.

Defining roles and competencies of Research Software Engineers (RSEs)
Exploring variations in RSE responsibilities across institutions
Proposing skill progression and future specializations for RSEs
Innovation

Methods, ideas, or system contributions that make the work stand out.

Defining RSE roles and competencies
Exploring diverse RSE work types
Proposing skill progression recommendations
🔎 Similar Papers
No similar papers found.
F
Florian Goth
Institute for Theoretical Physics and Astrophysics, University of Würzburg, Germany
R
Renato Alves
European Molecular Biology Laboratory, Heidelberg, Germany
M
Matthias Braun
Cluster of Excellence IntCDC, University of Stuttgart, Germany
L
Leyla Jael Castro
ZB MED Information Centre for Life Sciences, Cologne, Germany
G
G. Chourdakis
School of Computation, Information and Technology, Technical University of Munich, Garching, Germany
S
Simon Christ
Leibniz University Hannover, Department of Cell Biology and Biophysics, Computational Biology, Germany
J
Jeremy Cohen
Imperial College London, London, UK
Stephan Druskat
Stephan Druskat
Software Engineering Researcher; German Aerospace Center (DLR), Berlin, Germany
research software (engineering)empirical/evidence-based SEsoftware intelligence
F
Fredo Erxleben
Helmholtz-Zentrum Dresden-Rossendorf, Germany
J
Jean-Noel Grad
Institute for Computational Physics, University of Stuttgart, Germany
M
Magnus Hagdorn
Geschäftsbereich IT, Charité Universitätsmedizin Berlin, Germany
T
Toby Hodges
The Carpentries, USA
Guido Juckeland
Guido Juckeland
Helmholtz-Zentrum Dresden-Rossendorf, Germany
Dominic Kempf
Dominic Kempf
Heidelberg University, Scientific Software Center, Germany
Anna-Lena Lamprecht
Anna-Lena Lamprecht
Institute of Computer Science, University of Potsdam, Germany
Jan Linxweiler
Jan Linxweiler
Technische Universität Braunschweig
research software engineeringcomputational steeringHPC
Frank Löffler
Frank Löffler
Friedrich Schiller University Jena, Germany
M
Michele Martone
Leibniz Supercomputing Centre, Garching, Germany
M
Moritz Schwarzmeier
Mathematical Modeling and Analysis, TU Darmstadt, Germany
H
Heidi Seibold
IGDORE Munich, Germany
J
Jan Philipp Thiele
Weierstrass Institute, Berlin, Germany
H
H. Waldow
Johann Heinrich von Thünen Institute, Centre for Information Management, Germany
S
Samantha Wittke
CSC – IT Center for Science, Espoo, Finland