CompilerJobs is a curated map of who hires compiler engineers

The unit of the list is a team, not a company

The project describes itself as a listing of compiler, language and runtime teams for people looking for jobs in this area, and the listing is structured that way. Each entry is a company with a link to its careers page and then one or more bullet points naming the specific groups, the projects and the toolchains. AdaCore lists Ada runtimes and front ends including GNAT and libadalang, back ends to those front ends including GCC, LLVM, Infer and Why3, and various custom languages. Arm lists GCC, LLVM work to support Arm32 and the Scalable Vector Extension, an LLVM-based downstream GPU compiler for Mali GPUs, and an ML compiler. AMD lists AOCC, ROCm, and two LLVM teams working on the AMDGPU backend. The value of that granularity is that a candidate can see that a company has a specific group doing a specific thing, which is exactly the information a careers page hides behind a generic engineering requisition.

The scope is deliberately wider than compilers

The scope section is where the author states the inclusion rule, and it is broader than the title suggests. The list covers teams that work on language implementations, compilers for languages, language runtimes, static analysis and similar work, and it explicitly includes things like database query compilers and HDL and synthesis compilers. The author says he wants to err on the side of openness because the field is broad and he does not want to be too close-minded. There is a second, sharper criterion. He generally wants evidence that a company has hired at some point in the past or will in the future, and that is what excludes some boutique firms and early stage startups. So the list is not a directory of everyone who touches compilers, it is a directory of employers who plausibly employ someone whose job is compilers, and that distinction is what makes the list short enough to be usable.

Three annotations carry the metadata

Each entry can carry three markers and a location line, and the author is careful about what the markers mean. The remote icon means the company offered remote work at the time the icon was added, which is a deliberately narrow claim and one that goes stale. The internship icon means the company is known to have offered internships or co-ops in compilers, languages and runtimes, which is a claim about history rather than a current opening. The location marker is derived from job postings or other knowledge, and the author says outright that it is definitely not comprehensive, with a request that readers help update it. That candour is the point of the section, because a curated list that does not say where its data comes from is a list you cannot calibrate. The location data is in fact the weakest field in the file, and the author says so.

Careers pages are linked on purpose, and descriptions are stubs

Two conventions explain the shape of the entries. First, the author generally links to a company's careers or jobs page rather than to a specific job, and gives the reason: those links have a longer lifespan than a direct link to a posting. A listing made of individual job URLs rots within weeks, while a careers page survives for years, so the list stays useful even when every role it once pointed at has been filled. Second, the descriptions are frequently short. The contribution section asks people to feel free to spruce up the description of the work for teams they know about, and notes that many of these are simply stubs. So the quality of an entry tracks how much someone who works there has cared to write about it, which is an honest property of a crowd-maintained list and also the reason the file is worth reading rather than scraping.

A static site with a live count, built with Jekyll

The repository is tiny, with a Gemfile, a README.md, a _config.yml, an _includes/ directory and an index.md, and the site is published at mgaudet.github.io/CompilerJobs/. The one piece of machinery worth pointing out is in the README itself, where the Companies heading carries a count placeholder written as an inline id element.

# Companies (<i id="count"></i>)

That is a hook for a script to fill in the number of entries at build time, so the page never shows a stale hardcoded total. The licence field is empty and the repository listing does not include a licence file, so there is no explicit grant to reuse the content, which is worth knowing before you mirror it. The primary language is listed as HTML, which is consistent with a Jekyll site whose content is Markdown with a generated front page. The maintenance signal is the last push on 2026-09-28 with no releases, which for a list like this is the right shape, since the value is in the entries being current rather than in versioned releases.

Where a curated list runs out

The limitation is that a list of employers is a different thing from a set of openings, and the two are easy to confuse. Nothing in this repository tells you that a team is hiring this month, and the deliberate choice to link to careers pages means you will be checking a company page rather than a role. It also cannot tell you whether a team is growing, shrinking or keeping a legacy compiler maintained, which is the question a candidate actually cares about, and a one-line entry like LLVM and more is exactly the entry you would want expanded. The remote and internship markers are the same problem in a smaller form, because both record a historical state and neither carries a date in the rendered page, so a reader cannot tell a marker added last month from one added in 2019. The author's own framing, that many entries are stubs and that the location data is not comprehensive, is the honest summary. What the list does well is narrow: it tells you which employers have the kind of team you would be looking for, and that is a question a search engine answers badly.

Editorial conclusion

CompilerJobs suits a person deciding where to apply in a field where the team names are not obvious from the company names, since it lists the specific groups, for example two LLVM teams at AMD and the Bifrost JIT at Autodesk, rather than asking you to guess. It is the wrong tool for a hiring pipeline, because a list of employers is not a stream of openings and the links deliberately point at careers pages rather than at live postings, and it is the wrong tool if you need a complete picture, because the author says the location data is not comprehensive. Before using it, check the annotation date on the remote and internship markers, since the remote flag records the state at the time the icon was added rather than today, and treat every entry as a starting point for your own research. The last push was on 2026-09-28 and the repository publishes no releases.

Frequently asked questions

Official sources

1. Issues
2. mgaudet/CompilerJobs on GitHub
3. Project website
4. README