add English version

en/positions.md

@@ -31,6 +31,16 @@ When members of de-RSE e.V. represent the Society in public, they take the accep
 - **Full text:** [F1000Research](https://doi.org/10.12688/f1000research.23224.2); [arXiv:2005.01469 \[cs.GL\]](https://arxiv.org/abs/2005.01469)
 - **Cite:** Anzt H, Bach F, Druskat S et al. An environment for sustainable research software in Germany and beyond: current state, open challenges, and call for action [version 2; peer review: 2 approved]. F1000Research 2021, 9:295 (https://doi.org/10.12688/f1000research.23224.2). [[BibTeX]({{ "/assets/bib/deRSEPosition001.bib" | prepend: site.baseurl }})]
 
+### **Position 002** - Foundational Competencies and Responsibilities of a Research Software Engineer
+
+| ![First page of the position 002 PDF.]({{ "/assets/img/positions/position-002-cover.png" | prepend: site.baseurl }}) | **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, and give examples of future specialisations. An appendix details how existing curricula fit into this framework.
+
+- **Authors:** Florian Goth, Renato Alves, Matthias Braun, Leyla Jael Castro, Gerasimos Chourdakis, Simon Christ, Jeremy Cohen, Stephan Druskat, Fredo Erxleben, Jean-Noël Grad, Magnus Hagdorn, Toby Hodges, Guido Juckeland, Dominic Kempf, Anna-Lena Lamprecht, Jan Linxweiler, Frank Löffler, Michele Martone, Moritz Schwarzmeier, Heidi Seibold, Jan Philipp Thiele, Harald von Waldow, Samantha Wittke
+
+- **Community reviews:** 25. Juli 2024 - 09. August 2024
+- **Accepted as official position:** 19. September 2024
+- **Full text:** (submitted); [[arXiv:2311.11457 \[cs.SE\]](https://doi.org/10.48550/arXiv.2311.11457)
+- **Cite:** Goth et al. Foundational Competencies and Responsibilities of a Research Software Engineer. arXiv: 2311.11457
 
 ## Work in progress