Job search
Where to Find Research Software Engineer Jobs: US-RSE, Labs, and University Teams
A source map and completed role triage for finding research software work without treating every research title or lab appointment as the same career route.
Start with the US-RSE job board, then follow promising listings to the hiring institution. Add national-laboratory careers pages and university research-computing teams to your search. Research software work can appear under several titles, and an RSE title alone does not tell you whether the appointment emphasizes maintainable software or independent research, or whether it is a time-limited training position.
Choose sources around the work you want to own. This guide, published by LandOffer, reviews public institutional pages checked October 12, 2026; it is not an application or hiring-outcomes test. You can also browse recent roles on LandOffer, but verify research appointments with their actual employers. The completed teaching cases below are fictional and keep unknown employment terms visible.

Build a source map around the hiring institution
The US-RSE posting policy accepts roles with substantial research-software responsibilities and sufficiently adjacent work, regardless of title. It welcomes academic, industry, national-lab and nonprofit submissions. Its review concerns relevance to the community; inclusion does not establish your qualifications, a current vacancy, or an employer's funding commitment. The policy expects postings to be open to people based in the United States, with qualifying international opportunities also considered.
That makes it a useful discovery source when an exact-title query misses scientific developer or computational software positions. The board inspected for this guide linked university RSE positions, a Berkeley Lab postdoctoral fellowship, scientific developer work and a contractor's computer-scientist opening. These are different employment routes. Follow the institution or named employer, rather than treating every laboratory-related result as a federal civil-service position.
Here is a completed source map using actual public destinations. Its final column identifies what each source leaves unresolved.
| Starting source | Concrete lead or context reviewed | Next verification step |
|---|---|---|
| US-RSE jobs | Johns Hopkins RSE, Robotics & Simulation; university and laboratory-related titles | Open the employer detail and record its requisition identifier |
| Berkeley Lab careers | 2027 Alvarez and Hopper postdoctoral fellowships, requisition 107450 | Read degree timing, research proposal requirements and appointment conditions |
| Princeton RSE team | A central research-computing group working with academic partners | Use team context to understand the work; find a separate current employment posting |
| Named contractor careers | A contractor can advertise work supporting a research institution | Establish the employing entity and contract assignment before interpreting benefits or status |
The map produces three different outputs: an application lead, a specific fellowship route, and an organization to monitor. Only the first two reviewed sources contain a particular recruitment opportunity. A team directory belongs on an employer list; it should not become an invented open position.
Search for software responsibilities as well as titles
Try “research software engineer,” “scientific software developer,” “computational software,” and domain terms such as simulation, geospatial analysis or scientific data. Run a few separate searches and record which wording found each position, so you can repeat a useful query when new roles appear. A long string requiring every concept can hide a good role whose employer uses different language.
Read the verbs that describe ownership. Designing a reusable library, maintaining tests, improving performance and supporting research users indicate a different working week from running an existing analysis script. Neither is automatically better. The question is whether the responsibility matches the engineering work you want to keep doing.
A research-computing job can also emphasize cluster administration, user support or infrastructure reliability. Those responsibilities may suit an engineer who enjoys systems work, but an HPC label does not establish application development. Look for who writes the scientific code, who operates its environment, and who handles researchers' requests.
Similarly, “research engineer” may describe building experimental apparatus, developing models, or owning a software platform. Identify the output before inferring the career path. Keep an unfamiliar title in the search long enough to read its duties, then remove it if the work falls outside your chosen direction.
Read one university RSE posting in full
The public Johns Hopkins RSE, Robotics & Simulation posting, requisition 121856, offers a useful example of mixed research and engineering responsibilities. Its Data Science and AI Institute role describes both shorter consulting or service projects and longer AI research collaborations.
The posting calls for robust, reusable, portable and documented software, alongside collaboration with researchers. It also includes guidance and service to the university community. Its technical expectations cover Python or C++, relevant scientific or AI libraries, containers, Linux, Git, testing and development practices. A candidate should therefore examine both engineering depth and willingness to work with changing research questions.
Its minimum requirements name a quantitative master's degree and specified software and AI/ML or data-science experience, while allowing education/experience equivalencies under its stated formula. A PhD is highly preferred. Those categories are not interchangeable: “preferred” is different from a minimum requirement, and an equivalency provision requires the institution's evaluation.
Location also changes the decision. The inspected detail describes hybrid Baltimore work with approximately three to four on-site days in a five-day week. Someone seeking fully remote work should not keep it solely because research-software development can be performed on a laptop.
The reviewed JHU detail did not establish a funding end date. Record that field as unknown and ask about the individual appointment; the omission does not establish permanent funding. Likewise, a possible contribution to publications does not turn every responsibility into a paper-producing research appointment. This example supports reading the complete role rather than assuming that “university,” “RSE,” or “hybrid” resolves the practical questions.
Separate software staff work, research ownership and fellowships
A staff RSE often helps research succeed through dependable software. A research-scientist appointment may place more weight on defining questions and producing original findings. A postdoctoral fellowship can combine research and software while imposing degree timing and a specific application process. These are reading categories, not universal definitions.
The actual 2027 Berkeley Lab Alvarez and Hopper fellowship requires a PhD by October 1, 2027 and limits prior postdoctoral experience as described in the announcement. It seeks independent research contributions in computing-related fields. Its application deadline is October 30, 2026, and the materials include a research statement and references.
That opportunity belongs in a research shortlist for the appropriate candidate. It does not establish that every software role at the laboratory requires a doctorate. Its Berkeley work arrangements and program conditions also need separate review; a lab's name is not a substitute for reading the appointment.
Use the following fictional exercise to see how three similar-looking discoveries can produce different decisions.
Tessa has a quantitative master's degree and five years developing Python simulation tools, including three years supporting ML experiments. She wants to maintain shared software and collaborate with scientists. She has no PhD, can commute to Baltimore, and needs clarity about any fixed employment end date.
| Fictional appointment | Responsibility and stated requirement | Tessa's completed decision |
|---|---|---|
| University simulation RSE | Shared libraries, tests and research-user collaboration; master's plus relevant experience; doctorate preferred | Keep for detailed application review; check equivalency, exact experience and funding terms |
| Institute research scientist | Lead an independent research agenda; completed doctorate is a minimum | Remove from this shortlist because Tessa lacks the stated minimum |
| Laboratory postdoctoral fellowship | Original research proposal and doctoral timing requirement | Remove from this route; search the lab's staff engineering openings separately |
The university row is informed by the kind of distinctions visible in the JHU posting; the other rows are invented appointments. No employer has assessed Tessa. Her result is a narrower search, not a finding that she qualifies or would be selected.

Investigate the team behind the posting
A research-software team page can reveal a role's organizational home. Princeton's RSE service description explains collaboration across research groups and disciplines. It is useful context for searching beyond one department, but a description of the team does not establish an opening today.
Princeton's August 2026 partnership guide distinguishes central co-funding from full partner funding. In its co-funded model, partners commit funding for a finite period, typically one to three years. That partner commitment is not itself a statement that every individual employee has the same fixed appointment length.
The guide also describes engineering collaboration, professional development and discussion of publication credit. These institution-specific details suggest useful questions elsewhere: Who manages the engineer? Who sets priorities? How are contributions recognized? What happens when a particular project ends? They should not become assumptions about another university's policy.
For a department-funded position, ask whether you would work mainly with one principal investigator or across several groups. A single-project role may offer substantial domain depth; a central team may offer broader peer support. The posting, reporting structure and actual conversations should establish which arrangement applies.
Turn uncertainty into a precise appointment question
Avoid a broad message asking whether a job is “stable.” It invites an answer that may mean something different to each reader. Name the missing condition and explain the decision it affects.
For Tessa's fictional university lead, her prepared question is: “Is this staff appointment subject to a fixed end date or continued project funding? If the initial simulation project ends, does the appointment end, or can the engineer be assigned to another project within the team?”
She would send that only through the employer's designated contact when appropriate; this guide has sent nothing. A response about a currently funded project would still need to be distinguished from an individual employment guarantee. Written offer terms and institutional policies matter later in the process.
A second useful question concerns the work allocation: “How much of the initial assignment involves developing and maintaining shared simulation software, compared with running experiments, writing proposals or providing user support?” The answer helps Tessa compare the actual allocation of work with her preference for maintaining shared simulation software.
For Tessa's university lead, record the funding answer, its date and the source beside requisition 121856 rather than in a general university note. If different pages describe different arrangements, preserve the discrepancy and ask which governs the position. Do not silently choose the more attractive wording.
Run a focused search you can maintain
Create a small employer list from the source map: university research-computing groups, labs in your relevant scientific domain, and any named contractors whose employment model interests you. Record the actual employer separately from the research institution it supports.
Once a week, review the community board and those employer destinations. Deduplicate by employer, requisition and appointment. A community posting date can differ from the employer's creation date, and the same opportunity can appear in more than one board section. Neither duplication nor a recent board entry establishes a newly created vacancy.
For each promising result, save the domain, software output, minimum requirements, location, appointment type and unresolved funding condition. This is a research-employment shortlist, not a tally of every role containing “Python.” Remove clearly unsuitable routes early so you can read a smaller number of plausible positions carefully.
Before preparing materials, follow the current employer instructions. A fellowship research statement and a staff software application serve different purposes. Select examples of testing, maintainability, performance or research collaboration that match the duties you actually performed; do not claim independent scientific ownership merely because you supported a successful project.
Begin with one source and finish with one documented lead. As you browse recent roles on LandOffer, choose one research institution, open a specific employer posting, and record the software responsibility, minimum requirements and unresolved appointment condition before preparing materials.



