A research software engineer is someone involved in research, but more focused on the computational skills than publications. Nordic-RSE is the network of these people in the Nordics. We currently focus on building a network of RSEs and highlighting their importance in the academic system. For RSEs or people who might want to be one, we offer opportunities for professional development and career advancement.
A growing number of people in academia combine expertise in programming with an intricate understanding of research. Although this combination of skills is extremely valuable, RSEs often lack a formal place in the academic system: they may produce fewer first-author papers than a researcher, and they may contribute to many papers and not appear as a author beyond a minor acknowledgement, if that! Their code is less formal than a software developers’, and career recognition is correspondingly low. The term “Research Software Engineer” is an attempt to recognize and promote these people, and the advantages to being a RSE are similar to being a researcher. RSEs will almost always closely work with researchers.
There are two typical types of RSEs:
You can read more about RSEs demographics in the Nordics in our 2018 survey.
We are still just beginning - if you have ideas for activities we should organize, get in touch.
Most research software engineers don’t have that as their job title. If you answer yes to many of the following questions, you are doing the work of a research software engineer:
Content of this page is derived from text originally provided courtesy of the UK Research Software Engineer Association.