PageSourceSearch

https://nordic-rse.org/about/rse/

html nordic-rse.org collected 2026-10-01 15:06:09 UTC 10,650 bytes, 228 lines download raw bytes

1<!doctype html>
2<html lang="en">
3  <head>
4    <meta charset="utf-8">
5    <meta http-equiv="X-UA-Compatible" content="IE=edge">
6    <meta name="viewport" content="width=device-width, initial-scale=1">
7    <meta name="description" content="We bring together the community of people writing and contributing to
8research software from Nordic universities, research institutes, companies and
9other organizations to share knowledge, to organize meetings, and raise
10awareness for the scientific recognition of research software.
11">
12    <meta name="author" content="">
13    <link rel="shortcut icon" href="/img/favicon.ico">
14
15    <title>Nordic-RSE</title>
16
17    <link rel="stylesheet"
18      href="https://stackpath.bootstrapcdn.com/bootstrap/4.5.0/css/bootstrap.min.css"
19      integrity="sha384-9aIt2nRpC12Uk9gS9baDl411NQApFmC26EwAOH8WgZl5MYYxFfc+NcPb1dKGj7Sk"
20      crossorigin="anonymous">
21
22    
22<script src="https://kit.fontawesome.com/f030d443fe.js" crossorigin="anonymous"></script>
22
23
24    <!-- twitter card description -->
25    <meta name="twitter:card" content="summary_large_image">
26    <meta name="twitter:title" content="Nordic-RSE">
27    <meta name="twitter:description" content="We bring together the community of people writing and contributing to
28research software from Nordic universities, research institutes, companies and
29other organizations to share knowledge, to organize meetings, and raise
30awareness for the scientific recognition of research software.
31">
32    <meta name="twitter:site" content="@nordic_rse" />
33    <meta name="twitter:creator" content="@nordic_rse" />
34    <meta property="og:locale" content="en_US" />
35    <meta property="og:type" content="website" />
36    <meta property="og:title" content="Nordic-RSE" />
37    <meta property="og:description" content="We bring together the community of people writing and contributing to
38research software from Nordic universities, research institutes, companies and
39other organizations to share knowledge, to organize meetings, and raise
40awareness for the scientific recognition of research software.
41" />
42    <meta property="og:url" content="https://nordic-rse.org/" />
43    <meta property="og:site_name" content="Nordic-RSE" />
44
45    <!-- social media image -->
46    
47      <meta name="twitter:image" content="https://raw.githubusercontent.com/nordic-rse/nordic-rse-materials/main/graphics/www/NRSE_some.png">
48      <meta property="og:image" content="https://raw.githubusercontent.com/nordic-rse/nordic-rse-materials/main/graphics/www/NRSE_some.png" />
49      <meta property="og:image:width" content="876" />
50      <meta property="og:image:height" content="458" />
51    
52
53    <!-- font -->
54    <link href="https://fonts.googleapis.com/css?family=Roboto" rel="stylesheet">
55
56    <link href="https://nordic-rse.org/css/style.css" rel="stylesheet">
57
58    
59    
60  </head>
61
62  <body>
63
64    <div class="container">
65
66      <!-- navigation -->
67      <nav class="navbar navbar-expand-lg navbar-light fixed-top bg-light">
68        <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarNavDropdown" aria-controls="navbarNavDropdown" aria-expanded="false" aria-label="Toggle navigation">
69          <span class="navbar-toggler-icon"></span>
70        </button>
71        <div class="collapse navbar-collapse" id="navbarNavDropdown">
72          <ul class="navbar-nav">
73            <li class="nav-item">
74              <a class="navbar-brand" href="https://nordic-rse.org/">
75                
76                <img src="https:&#x2F;&#x2F;nordic-rse.org&#x2F;processed_images&#x2F;NRSE_neighboring_oneline.5a84b6f72eafe84e.png" style="display: inline-block;">
77                <!-- <span style="display: inline-block;">Nordic-RSE</span> -->
78              </a>
79            </li>
80          </ul>
81          <ul class="nav navbar-nav navbar-right">
82
83            <!-- about us-->
84            <li class="nav-item dropdown">
85              <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownMenuLink"
86             data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
87                About
88              </a>
89              <div class="dropdown-menu" aria-labelledby="navbarDropdownMenuLink">
90                <a class="dropdown-item" href="https://nordic-rse.org/about/rse/">What is RSE?</a>
91                <a class="dropdown-item" href="https://nordic-rse.org/about/governance/">Governance</a>
92                <a class="dropdown-item" href="https://nordic-rse.org/about/code-of-conduct/">Code of Conduct</a>
93              </div>
94            </li>
95
96
97            <!-- Events -->
98            <li class="nav-item dropdown">
99              <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownMenuLink"
100             data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
101                Events
102              </a>
103              <div class="dropdown-menu" aria-labelledby="navbarDropdownMenuLink">
104              <!--  <a class="dropdown-item" href="https://researchsoftwarehour.github.io/">Research Software Hours</a>-->
105                <a class="dropdown-item" href="https://nordic-rse.org/events/">Events overview</a>
106                <a class="dropdown-item" href="https://nordic-rse.org/events/seminar-series">Seminar series</a>
107                <a class="dropdown-item" href="https://nordic-rse.org/nrse2026
107/">Conference</a>
108                <a class="dropdown-item" href="https://nordic-rse.org/events/past ">Past events</a>
109                <a class="dropdown-item" href="https://nordic-rse.org/events/#calendar">Calendar</a>
110              </div>
111            </li>
112
113            <!-- Community -->
114            <li class="nav-item">
115              <a class="nav-link" href="https://nordic-rse.org/communities/">Community</a>
116            </li>
117            
118
119            <!-- Blog -->
120            <li class="nav-item">
121              <a class="nav-link" href="https://nordic-rse.org/blog/">Blog</a>
122            </li>
123
124            <!-- Resources -->
125            <li class="nav-item">
126              <a class="nav-link" href="https://nordic-rse.org/resources/">Resources</a>
127            </li>
128            
129
130            <!-- Get involved -->
131            <li class="nav-item">
132              <a class="nav-link" href="https://nordic-rse.org/join/">Get involved</a>
133            </li>
134          </ul>
135        </div>
136      </nav>
137      <!-- end navigation -->
138
139      <div class="row top-buffer">
140        
141  <div class="col-md-12">
142    <h1 id="research-software-engineers">Research Software Engineers</h1>
143<h3 id="what-is-a-research-software-engineer">What is a research software engineer?</h3>
144<p>A growing number of people in academia <strong>combine expertise in programming with an
145intricate understanding of research</strong>. Although this combination of skills is
146extremely valuable, RSEs often lack a formal place in the academic
147system: they may produce fewer first-author papers than a researcher,
148and they may contribute to many papers and not appear as a
149author beyond a minor acknowledgement, if that!
150Their code is less
151formal than a software developers', and career recognition is
152correspondingly low.  The term &quot;Research Software Engineer&quot; is an attempt
153to recognize and promote these people, and the <a href="https://www.software.ac.uk/blog/2013-08-23-ten-reasons-be-research-software-engineer">advantages to being a
154RSE are similar to being a
155researcher</a>.
156RSEs will almost always closely work with researchers.</p>
157<p>You can read more about RSEs demographics in the Nordics in <a href="https://github.com/nordic-rse/RSE_intro_survey">our 2018
158survey</a>.</p>
159<h3 id="are-you-a-research-software-engineer">Are you a research software engineer?</h3>
160<p>Most research software engineers don't have that as their job title.  If you answer yes to many of the following
161questions, you are doing the work of a research software engineer:</p>
162<ul>
163<li>Are you employed to develop software for research?</li>
164<li>Are you spending more time developing software than conducting research?</li>
165<li>Are you employed as a postdoctoral researcher, even though you predominantly work on software development?</li>
166<li>Are you the person who write research software in your research group?</li>
167<li>Are you sometimes not named on research papers despite playing a fundamental part in developing the software used to create them?</li>
168<li>Do you lack the metrics needed to progress your academic career, like papers
169and conference presentations, despite having made a significant contribution
170through software?</li>
171</ul>
172<p>Content of this page is derived from text originally provided courtesy of the
173<a href="https://society-rse.org/">Society Research Software Engineering in UK</a>.</p>
174
175  </div>
176
177      </div>
178
179      <footer>
180        <div class="row top-buffer">
181        </div>
182        <hr>
183        <div class="row">
184          <div class="col-md-4">
185          </div>
186          <div class="col-md-4">
187            <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">
188              <img alt="Creative Commons Licence" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/80x15.png" />
189            </a>
190            <br/>This work is licensed under a
191            <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">
192              Creative Commons Attribution 4.0 International License
193            </a>.
194	    <a href="/about/governance/privacy/">Privacy Policy
195	    </a>.
196          </div>
197        </div>
198      </footer>
199    </div>
200
201    
202    
203
204    
204<script src="https://code.jquery.com/jquery-3.5.1.slim.min.js"
205            integrity="sha384-DfXdz2htPH0lsSSs5nCTpuj/zy4C+OGpamoFVy38MVBnE+IbbVYUew+OrCXaRkfj"
206            crossorigin="anonymous"></script>
206
207    
207<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/umd/popper.min.js"
208            integrity="sha384-Q6E9RHvbIyZFJoft+2mJbHaEWldlvI9IOYy5n3zV9zzTtmI3UksdQRVvoxMfooAo"
209            crossorigin="anonymous"></script>
209
210    
210<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.5.0/js/bootstrap.min.js"
211            integrity="sha384-OgVRvuATP1z7JjHLkuOU7Xw704+h835Lr+6QL9UvYjZE3Ipu6Tp75j7Bh/kR0JKI"
212            crossorigin="anonymous"></script>
212
213
214    
214<script src="https://cdn.jsdelivr.net/npm/[email protected]/anchor.min.js"
215            integrity="sha256-E4RlfxwyJVmkkk0szw7LYJxuPlp6evtPSBDlWHsYYL8="
216            crossorigin="anonymous"></script>
216
217
218    
218<script>
219      anchors.add();
220
221      // https://github.com/twbs/bootstrap/issues/1768#issuecomment-6531466
222      var shiftWindow = function() { scrollBy(0, -100) };
223      if (location.hash) shiftWindow();
224      window.addEventListener("hashchange", shiftWindow);
225    </script>
225
226
227  </body>
228</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.