Core and required roles are separated from contextual and optional mentions so the headline does not overstate job intent.
Explore Bun by location
Select up to five markets; results and hiring evidence update together.
This reference guide is available while the observed market sample grows. Counts describe listings in our catalog; employer breadth and source-date coverage are still limited.
0core + required roles2context + optional mentions2remote-friendly▼ -1 this week
Employer concentration
Kiss My Apps accounts for 1 of 2 mentions (50%). The remaining 1 mentions span other employers.
Bun combines a JavaScript runtime with tools for packages, tests and builds. A vacancy may name it as the execution runtime or only as part of developer tooling. Compatibility and application behavior should be verified for the components actually used.
2 live roles2 hiring companies100% remote-friendly
Vacancy evidence map
Where Bun carries hiring weight
Each segment represents roles where Bun was parsed at that evidence tier. This keeps a required production skill separate from contextual stack language.
0 Core0 Required1 Supporting1 Optional
0core + required0% of mentions
1roles per company2 employers
Market interpretation
What Bun demand means in practice
Bun combines a JavaScript runtime with tools for packages, tests and builds. A vacancy may name it as the execution runtime or only as part of developer tooling. Compatibility and application behavior should be verified for the components actually used.
State which Bun tools you adopted and the dependency compatibility you tested. Show an application or pipeline measurement under the same workload as its baseline. Explain deployment, error diagnosis and rollback, and distinguish a faster local command from an improvement to the production system.
Bun combines a JavaScript runtime with tools for packages, tests and builds. A vacancy may name it as the execution runtime or only as part of developer tooling. Compatibility and application behavior should be verified for the components actually used.
What evidence should I provide for a Bun role?
State which Bun tools you adopted and the dependency compatibility you tested. Show an application or pipeline measurement under the same workload as its baseline. Explain deployment, error diagnosis and rollback, and distinguish a faster local command from an improvement to the production system.
How Bun appears in job requirements
Inferred from the title and requirement wording in 2 active roles; each role is counted once. Read the methodology.
Posting evidence, not a company-wide stack claim
Main / core
0%(0)
Required
0%(0)
Supporting / context
50%(1)
Nice-to-have
50%(1)
Skills mentioned with Bun
A shared posting does not always require both skills. Explicit alternatives are counted separately.