Job search
CRA Career Center Review: Separate Research Staff, Postdocs, and Faculty Career Tracks
Use actual appointment descriptions to distinguish research software staff, academic research scientists, postdocs and faculty on CRA Career Center.
CRA Career Center can help you discover computing roles in universities and research organizations, but a search for “research” does not isolate research staff jobs. A software engineer, a postdoctoral scholar and a professor may all work on AI while joining different appointment systems and carrying different obligations.
This review checks public pages on October 22, 2026. We searched the board and followed employer references without signing in, saving jobs or starting applications. The examples below separate observed listings from fictional candidate decisions. You can also explore LandOffer.ai while comparing research employment with a broader technology search.

What the CRA search actually showed
The CRA Career Center job search displayed 122 listings during our check. Its public controls included keyword and location search, position type and other filters. Entering “research” returned 102 results; the first visible page remained heavily populated by faculty roles, alongside a postdoctoral listing. Those are dated observations, not estimates of the whole academic technology market.
We inspected the initial results page, not every listing. We also opened the Job Title filter, whose visible choices did not establish a comprehensive staff-only category. The search is useful for discovery, but a computing keyword and a full-time label are weak evidence of the career track you would enter.
Describe the work you want before searching: maintaining research software, operating computing infrastructure, developing a research program, or teaching and advising. Then inspect the appointment language in each result. A relevant subject area can coexist with an unsuitable employment arrangement.
Save the exact title, employer, requisition and check date in your own record. Keep both links so you can return to the employer record when the board description changes or disappears. Registration and saved-job controls were visible, but we did not test account features, alerts or application handling. This review does not make a price or placement claim about them.
Classify the appointment before comparing technologies
Ask what the employee is hired to own and how that work will be evaluated. Software staff may build and maintain tools for other researchers. A postdoctoral appointment may center on a bounded research assignment and professional development. Faculty appointments may combine research leadership, teaching and service. These are reading categories, not universal definitions that override a posting.
| Track to investigate | Evidence to find in the actual appointment | Assumption to avoid |
|---|---|---|
| Research software or engineering staff | Organizational unit, software ownership, support obligations, required qualifications and employment terms | Every university software role requires a doctorate |
| Academic research scientist | Appointment series, independent research expectations, grant responsibilities and funding conditions | “Scientist” automatically means ordinary staff engineering |
| Postdoctoral research | Degree timing, research duties, appointment duration, renewal conditions and location | Full-time means an indefinite role |
| Faculty | Rank, tenure description, teaching, advising, research and service | Every computing faculty role has the same tenure arrangement |
A staff-oriented search should therefore examine duties as well as titles. Look for who defines the research questions, who writes funding proposals, who maintains shared infrastructure and how success is assessed. A role can include coding while evaluating the employee mainly on scholarly leadership.
Read the appointment terms separately from the duties. A strong technical match does not resolve the employment arrangement. Full-time describes workload, not guaranteed duration. An initial term, a maximum term, possible renewal and continuing funding are separate facts. When a posting leaves one unspecified, keep it unresolved rather than converting silence into permanence.
Three CRA-linked appointments illustrate the difference
The ASU Postdoctoral Research Scholar listing led to an employer posting on Interfolio. That page described AI project development with interdisciplinary researchers, including support for competitive funding proposals. It required a relevant PhD by appointment, anticipated a January 2027 start, and described up to two years contingent on funding, performance and project needs.
The employer required physical presence in Tempe; another location needed additional approval that was not guaranteed. Its December 1, 2026 application deadline was followed by a separately described reserve-pool process. Neither a reserve pool nor an anticipated start is an appointment offer. A developer interested in durable platform ownership should inspect this research-and-proposal remit before treating the AI terminology as a conventional engineering match.
The William & Mary Professor of Data Science advertisement referenced its faculty recruitment portal. The exact employer role, JR102152, described a tenured Professor appointment beginning August 10, 2027. It required a relevant PhD, teaching and mentoring experience, and an established research record. Duties included teaching one course each semester and sustaining an externally funded research program. November 13, 2026 was the initial review date, with later applications considered if needed.
The employer's generic job-family label said tenure track, while the role description specifically said tenured Professor. Read both fields rather than silently replacing the detailed description with a broad category. The specific appointment also stated it was continuing and not term-limited; that statement belongs to this role, not every faculty listing.
A third case complicates the staff/faculty split. CRA's UC San Diego Research Scientist page said the job was unavailable. The UCSD employer record, JPF04498, still displayed a December 31, 2026 final date, with consideration after its September review conditional on the position remaining unfilled. Its non-tenured academic research series expected independent research and principal-investigator responsibilities, required a relevant PhD at application, and tied appointment duration to projects and funding. That is not evidence of an ordinary continuing software staff position—or confirmation that a vacancy remains.
A software staff comparison outside the board
To make the distinction concrete, we separately read NYU's Senior Research Software Engineer posting, 2026-15732. We did not establish that CRA carried this job. The employer's public HTML described building and maintaining solutions for researchers and instructors, including research computing infrastructure.
The role listed a relevant master's degree or equivalent work experience as required education, with a doctorate preferred, plus five or more years of software engineering experience. It identified NYU IT's Research Technology Services and a hybrid arrangement requiring 60–80% onsite in New York. Those are role-specific conditions, not a general alternative-qualification policy for universities.
Our browser showed the NYU careers shell with a blank job frame; the detailed text was available through an ordinary public page retrieval. We therefore treat it as a documented employer comparison, not a completed native application test. We did not verify appointment duration or infer permanence from its full-time label.

Worked example: a software maintainer sorts the shortlist
This is a fictional decision record, not an application assessment or a claim about actual search recommendations. Beatrice has a computing master's and six years maintaining data-processing services. She wants reusable software, user support and a defined team; she does not want to lead an independent scholarly program.
| Record item | Beatrice's completed comparison | Decision consequence |
|---|---|---|
| Preferred output | Tested data tools, release notes and maintained interfaces | Prioritize software ownership |
| NYU example | Relevant software duties; master's-or-equivalent wording; New York onsite requirement | Keep for a full requirements review |
| ASU example | PhD required by appointment; bounded postdoctoral remit | Exclude from this staff shortlist |
| William & Mary example | Tenured Professor duties include teaching and research leadership | Exclude from this staff shortlist |
| UCSD example | Academic PI expectations; board/employer availability discrepancy | Exclude as a staff match; retain the status note |
| Unresolved employment fact | NYU comparison does not establish appointment duration | Hold any conclusion about continuing employment |
Her finished experience summary reads: “I maintained a shared ingestion service used by three internal research groups. I owned schema migrations, automated regression checks and documented releases; the investigators owned the scientific questions. My strongest evidence is a reproducible migration test and a runbook explaining failure recovery.” These are fictional facts, not suggested claims for readers to copy unchanged.
Her decision is keep for further review. She has identified a relevant work pattern without completing a qualification assessment. She still needs to compare every required skill, actual location feasibility and current availability. She records infrastructure experience she lacks rather than treating the degree wording as approval. The other three roles leave this shortlist because their appointment goals differ from hers, not because their computing work is less substantial.
Worked example: research credentials do not settle the contract
A second fictional candidate, Darius, has a relevant doctorate and enjoys collaborative research. He wants to work with multiple labs but can commit to only an 18-month relocation. His doctorate alone does not tell him whether a postdoc, academic scientist or software staff appointment fits.
He completes an appointment memo using an invented project offer description, not an actual employer offer:
| Question | Stated scenario fact | Remaining issue |
|---|---|---|
| Work ownership | Develop a shared evaluation package with two labs | Who approves releases when lab priorities conflict? |
| Initial term | Twelve months | Extension is discussed but not committed |
| Funding | Initial year is budgeted | No evidence for the following six months |
| Research responsibility | Collaborate on experiments and a methods paper | Independent grant leadership is not stated |
| Maintenance | Package will serve another cohort | No successor or support allocation identified |
| Location | Campus presence throughout the initial term | Later flexibility is unspecified |
His complete, unsent clarification note reads: “I understand the initial appointment described here is twelve months. My planning horizon is eighteen months, so I am treating any additional period as unresolved. Please clarify the appointment category, the process and conditions for renewal, and whether funding is committed beyond the initial term. For the evaluation package, who decides release priorities, and who maintains it after the appointment? I would also like the location expectation stated for the full initial period. I am not assuming these points from the job title.”
Darius records hold rather than treating the proposed extension as committed employment. Twelve stated months leave six months of his planning horizon unsupported; an extension conversation does not fill that gap. Even if the technical work fits, he has not resolved the term or handoff. This example demonstrates a comparison method, not advice that relocation or leaving another job is safe.
Use CRA as a lead, then verify the owning institution
CRA is useful when you want computing research employers and are willing to classify appointments carefully. It is less efficient as a staff-only feed if you assume that a broad keyword will remove faculty and postdoctoral results. Our limited public search did not establish comprehensive staff coverage, listing freshness across the board or hiring outcomes.
For each retained lead, compare the actual requisition and employer description with your intended work. Preserve required versus preferred qualifications, appointment duration, funding conditions, location and review dates. If the board and employer disagree, retain both observations and check the institution's current record before investing in application materials. A detailed advertisement still cannot establish an individual's selection or future renewal.
For a parallel search beyond academic appointments, browse recently posted technology roles on LandOffer.ai. For each CRA lead, finish the appointment comparison before adapting your resume. Select evidence for the work the institution actually describes: maintaining software, conducting a bounded research assignment, or leading a faculty research and teaching program.
Sources and Further Reading
- CRA Career Center job search
- CRA ASU postdoctoral advertisement and ASU employer description
- CRA William & Mary advertisement and employer faculty portal, exact role JR102152
- CRA UCSD research scientist page, unavailable at check and UCSD employer record JPF04498
- Independent NYU software staff comparison


