Job search
80,000 Hours Job Board Review: Filter Engineering Jobs Without Confusing Fellowships and Grants
Separate software engineering jobs, career development, fellowships and funding on the 80,000 Hours job board before choosing an application route.
The 80,000 Hours job board can help software engineers find work connected to its chosen global problems, but its opportunities include employment, fellowships and funding. Start with Software engineering under Skill set, then select your intended Role type. Decide separately whether to exclude career-development opportunities, then read the original source before preparing an application.
Our public checks found useful narrowing and consequential differences between cards and original sources. One engineering card carried a Junior label while the employer sought senior and principal engineers. A visiting fellowship marked rolling on the board had closed its Fall 2026 cohort. A salary-information filter also left three Funding entries visible.
LandOffer.ai publishes this review. Compare retained employment leads with recent LandOffer.ai jobs using the same source and eligibility checks. We inspected public pages on October 13–14, 2026, without creating a matching profile, subscribing to alerts, requesting advice or submitting an application. Counts below describe that session.

Decide whether the board's priorities fit your search
The board's FAQ describes a curated selection of public opportunities that could contribute to its chosen problems or develop skills and connections for future work on them. The FAQ distinguishes endorsement of a listed role from endorsement of the organisation or its other roles. The FAQ also acknowledges limits to its review capacity.
That scope makes the board useful when you want to investigate those priorities. It is a narrower starting point than a general software-job directory. A relevant technical role may sit among research, operations, policy, fellowships and project funding because the site serves several routes into the same problem areas.
Choose the work arrangement you need before choosing an appealing mission. If you need an employee position now, a supported research visit or project grant belongs in a separate list. They may be worthwhile opportunities, but they ask different questions about your existing work, finances, availability and materials.
You can also keep using a broad board that already supplies relevant engineering leads. This review does not establish that 80,000 Hours has exclusive opportunities, better hiring odds or comprehensive coverage. Its value here is a focused discovery route you can combine with employer research.
A completed software-engineering filter sequence
We tested the public board without an account. The Skill set menu had separate entries for Software engineering and Engineering. At the time, those facets displayed 241 and 18 respectively. We selected Software engineering; we did not test the Engineering category or assume the two were interchangeable.
Here is the actual narrowing sequence:
| Setting applied in order | Displayed result | What that step established |
|---|---|---|
| No filters | 932 roles | The starting public opportunity list in this session |
| Skill set: Software engineering | 241 roles | Results carrying the selected skill category |
| Add Role type: Full-time | 221 roles | The intersection with the selected full-time classification |
| Add Exclude career development | 208 roles | A further reduction using that separate setting |
The three selected settings remained visible together. We did not measure classification accuracy across the list, and these counts are not a promise of how many jobs will be available when you search. Facet counts can overlap, so adding them does not produce a reliable total of distinct opportunities.
The distinction between role type and career development matters. Full-time describes one classification; career development is another reason a role may be included. Excluding the latter reduced an already full-time list in our session. It is therefore a different choice from excluding fellowships or selecting a skill.
Even the final list contained an Expression of Interest, Core Technology Team card from the UK Government's AI Security Institute. We inspected its card, not its original recruitment terms. Treat that result as a reason to open the destination and identify what is being requested, rather than counting every full-time result as a currently open employee vacancy.
The FAQ says Ranked sorting combines publication date with the site's rating; it also documents other sorting choices. A high position on the list does not tell you whether your background, work authorization or preferred arrangement fits. The board's order can guide reading, while the original description decides what you prepare.
Salary information cannot identify an employment offer
The Annual salary panel explains that hourly, weekly and monthly amounts are annualised, and non-US salaries are converted to a USD equivalent. It also says excluding entries without salary information excludes one-off payments such as grants and awards. These are the board's displayed explanations, not conversions or payments we independently verified.
To see what that control did to funding, we cleared the earlier filters, selected Funding, and then enabled Exclude roles without salary info. The list went from 26 to three. The remaining cards were MATS Research's Residency Program, Omidyar Network's Tech Journalism Fund and Global Rice Research Foundation's Global Rice Leadership Awards. Each still displayed Funding.
This observation is narrow but useful: the switch did not turn the remaining opportunities into employee jobs. We did not determine how each amount was entered or converted, or investigate each fund's detailed terms. Do not use the presence of salary data as a substitute for reading the opportunity type.
For employment, find the employer's compensation, location and arrangement. For a fellowship, establish whether support means a stipend, expenses, accommodation or something else. For a grant, identify the project and permitted use of funds. An annualised number can support a search comparison while leaving those practical questions unresolved.
If you are deliberately looking for project support, a salary-information requirement can also remove opportunities you wanted to inspect. Run that search separately from your employment search. Keep its criteria appropriate to a proposal, rather than asking a funding record to behave like a salaried vacancy.
Three original sources changed the next action
We opened the engineering employer, fellowship programme and funder pages linked from three board records. Save the original source with each lead so its requirements remain available when you prepare materials.
| Opportunity | Original-source finding | Resulting action |
|---|---|---|
| Meridian Labs: Member of Technical Staff, Engineering | Hiring senior and principal engineers; owns shipped Python and TypeScript/React tools. Compensation depends on experience and level. | Evaluate the original engineering requirements before preparing its employment materials; the board's Junior tag is insufficient. |
| Constellation: Visiting Fellowship | Fall 2026 applications closed; three-to-six-month Berkeley visit, no stipend, with housing, travel and meals covered. | Save future-cohort interest separately from a current employee application. Resolve existing research work and funding before considering attendance. |
| Transformative AI Fund | Early-stage project grants for individuals and organisations; applications open on the inspected funder page. | Investigate project fit and the funding application route. Do not file it as an employee vacancy or annual salary. |
Meridian Labs: engineering work, with an original seniority requirement
The Meridian Labs employer page describes engineers building Python evaluation libraries and TypeScript/React applications used to inspect results. Responsibilities include implementation, tests, documentation, releases, code review and fixing user-reported problems. This is concrete software ownership, even though the surrounding mission concerns AI research.
Its minimum qualifications call for strong Python or strong TypeScript and React, with willingness to work in the other. It also asks for a record of shipping and maintaining software, judgment about scope, and clear writing in reviews, documentation and issues. Those details give you something more useful to compare with your work than a broad engineering label.
The important discrepancy was seniority. The board card displayed Junior, with one to four years of experience, while the original page said it was hiring at senior and principal levels. Use the employer's requirement to judge the application. We did not establish why the label differed or whether the employer would consider an individual applicant outside those levels.
The original page displayed $175,000–325,000 with benefits, depending on level and experience. It preferred in-person or hybrid work in Boston, the San Francisco Bay Area or London, while allowing remote work for the right person. That conditional wording does not promise unrestricted remote eligibility.
Its employment packet asks for a resume, LinkedIn and GitHub links if available, and a brief explanation of interest by email. We read that instruction and sent nothing. A retained lead now has a specific engineering scope, seniority condition, attendance discussion and requested packet.
Constellation: a supported visit, with a closed current cohort
The Constellation Visiting Fellowship page described a three-to-six-month programme for AI safety researchers working from its Berkeley centre. Applicants should already be working full-time in its focus areas or closely related work. The programme provides a place to continue research and collaborate, rather than presenting a generic entry-level engineering vacancy.
The original page said Fall 2026 applications were closed and offered an expression-of-interest route for future opportunities. This differed from the board's rolling-applications text. At our check, the correct action was to record the closed cohort and future-interest option; we did not open or submit that form.
The terms also ruled out a remote visit. Fellows were generally expected at the workspace at least three days per week on average. Housing, travel and meals were covered, but the FAQ said there was no stipend. It mentioned possible help with funding or a paid residency when funding is a barrier; that possibility is not an assured arrangement.
An employed researcher with supported ongoing work may evaluate this as a future collaboration opportunity. Someone seeking an immediate paid software position should not put it in the same application queue merely because it appears on a job board. For an immediate employment search, remove this closed research visit; for a future visit, keep its attendance and funding conditions with the cohort note.
Transformative AI Fund: a project, not a job packet
The Transformative AI Fund described early-stage grants to individuals, new organisations and existing organisations starting projects. Its main focus was reducing catastrophic risks from advanced AI, alongside some other implications of transformative AI. Its published typical grant range was $10,000–150,000, rarely exceeding $300,000.
The inspected page said applications were always open. That establishes an available funding route in the source we read, not approval for any applicant. The listed amounts are project grants; they do not establish an annual employment salary, recurring income or an offer to join the funder's team.
A software developer with a concrete, relevant project may investigate whether that proposal fits. A developer seeking employee work can remove it from the employment queue and retain it only if a separate project-funding search is intended. We did not open a funding form, donate or contact the funder.

Preserve the original request before preparing materials
The three records now lead to different preparation. Meridian asks for employment materials and software experience. Constellation's current page directs future-cohort interest for a research visit. The fund requires investigating a project-funding route. Reading the request first avoids preparing a job packet for a research visit or project-funding opportunity.
The board's FAQ says it uses language models to help produce bullet-point summaries. Those summaries can help you decide which original pages to read, but keep original qualifications and dates in your record. A short card cannot replace the source when seniority or a closed cohort changes your action.
For each retained lead, save its original URL, opportunity type, current opening or interest status, work location, decisive qualification and requested materials. For Meridian, keep conditional remote work as a question; for Constellation, record the next cohort window as unknown. Do not mark a lead applied because you opened a card, found an email address or saw a programme's interest button.
Start an employment search with Software engineering and your intended Role type; make the career-development setting a deliberate choice. Keep fellowship and funding searches separate when you want those routes. Compare retained employment leads with recent LandOffer.ai jobs, confirm their current original terms and opening status, then prepare the materials that destination requests.
Sources and Further Reading
- 80,000 Hours job board — native filter sequences, opportunity cards and salary explanation inspected October 13–14, 2026.
- 80,000 Hours job-board FAQ — curation, endorsement boundaries, sorting and summary production.
- Meridian Labs engineering position — original responsibilities, seniority, compensation, location and employment materials.
- Constellation Visiting Fellowship — original closed Fall 2026 cohort, attendance and support terms.
- Transformative AI Fund — original project scope, grant range and funding route.


