Find tech jobs shared by GitHub communities.
Openings brings public job listings into one focused search experience
while keeping every opportunity connected to its original source.
Search open jobs · Browse communities · Read the overview · Star on GitHub
Technology communities publish job openings in public GitHub issues. Those listings are useful, direct, and easy to miss when they are spread across many repositories.
Openings makes that public activity easier to discover. Instead of checking communities one by one, candidates get a searchable view of supported listings, with the repository, community, author, location, work model, seniority, and stack still attached.
You spend less time jumping between repositories and get a clearer path to the listings worth opening.
With Openings, you can:
- search jobs by title, stack, seniority, location, and work model;
- rank searches by relevance with synonyms and conservative typo tolerance;
- filter by real job geography, recency, salary disclosure, employment type, language, and structured technology taxonomy;
- save jobs and preferences in the current browser, see what is new since the previous visit, and compare up to three jobs through a shareable URL;
- browse dedicated pages for communities and GitHub authors;
- inspect public community synchronization status, including the latest successful sync and posting date;
- read each job in a clean, consistent layout;
- share a direct job or community page;
- continue to the original public listing for current details and next steps.
Openings is a discovery layer, not another job board asking communities to publish the same role twice.
Saved jobs, viewed state, and preferences stay in the current browser. They do not require an account and do not sync across devices.
The public openings-dev/data-pipeline project connects GitHub communities to the Openings experience.
- Communities publish jobs. Maintainers and members share openings through public issues in supported GitHub repositories.
- The data project organizes them. The community catalog and generated public data files turn those scattered issues into a consistent index.
- Openings makes them discoverable. The website presents searchable jobs and dedicated profiles, then sends candidates back to the original listing.
Public GitHub issues → openings-dev/data-pipeline → openings.dev → original listing
The data pipeline and the frontend are both public. Anyone can inspect how a listing reaches the product.
Openings reduces the work of monitoring separate repositories. You can narrow the catalog quickly, compare relevant context, and decide which original listings are worth opening.
Each supported community gets a shareable page for its open jobs. That page can live in a README, website, or social profile while the original GitHub issue remains the destination for complete details.
Find your community or read the community listing guide.
Openings helps people discover public job listings. It does not own those listings, verify employers, guarantee that a role is still available, or manage applications.
Before applying, candidates should confirm the requirements, availability, contact information, and next steps in the original public source.
Openings grows through two open repositories:
openings-dev/webcontains the product experience;openings-dev/data-pipelinecontains the community catalog and public data workflow.
You can help by improving the experience, refining the documentation, or expanding the supported community catalog. Start with the contribution guide, and leave a star if you want to follow the project as it grows.
Architecture, public data files, local development, integration details, and contribution workflows live in the product documentation.
Read the Openings project overview →
Openings is available under the MIT License.