Guide · Open source
How to use vagas: browse and post front-end jobs on GitHub
Updated · written with AI from the project's own documentation and checked against our catalogue data
frontendbr/vagas is a job board for front-end developers that runs on GitHub Issues. Companies and recruiters post each opening as its own issue, and developers browse those issues or follow the repository to get notified. The README is in Portuguese and focuses on Brazil, so this guide explains how to browse the board, how to post a role, and which rules to follow.
frontendbr/vagasfrontendbr/vagas · ★ 15.5k · MIT Install options & downloads Quick start
- 1Open the issues list. Go to https://github.com/frontendbr/vagas/issues to see the current job openings.
- 2Set up notifications. Click Watch on the repository, choose Watching, and adjust your delivery settings in GitHub notifications if needed.
- 3Read the rules. Check the posting rules in the README, including the 3-posts-per-company-per-month limit.
- 4Open an issue for your role. Create a new issue with the city in brackets, the job title and the company name in the title.
- 5Add labels and follow the template. Add labels for the experience level and contract type, and fill in the issue template completely.
- 6Maintain your post. Every 3 months, comment that the role is still open or close the issue with the outcome.
What the frontendbr/vagas board is
The repository is a space for sharing front-end job openings through GitHub Issues. Only front-end roles are accepted. The README points to separate repositories for other areas, such as back-end, UI/UX, QA and specific technologies.
The README is written in Portuguese, and the posting rules and job posts are in Portuguese too.
- Each job opening is one issue.
- Only front-end roles belong in this repository.
- Other areas and technologies have their own vagas repositories listed in the README.
Browse the open job posts
Open the issues list of the repository to see the current openings. Each post is an issue, so you can read the details in the issue and comment on it.
If you prefer a search interface, the README also links to openings.dev, where you can search and filter the Front-end Brasil vagas. Each result still links back to the original issue in this repository.
- Issues list: https://github.com/frontendbr/vagas/issues
- Search and filter: openings.dev, community frontendbr/vagas
- Each openings.dev result links to the original GitHub issue.
Get notified of new job posts
You can receive updates on new openings by email or through GitHub notifications. The README says to click Watch on the repository and then choose Watching.
You can change how you receive notifications in your GitHub notification settings.
- Click Watch on the repository.
- Select Watching.
- Adjust the notification method in your GitHub notification settings.
Post a job opening
Open a new issue. In the title, put the city in square brackets, followed by the job title and the company name. Then add the labels that describe the experience level sought and the type of contract. The README gives this title format as an example.
Use the issue template in the repository, since posts that leave out information or do not follow the template are not accepted.
- Open an issue in the repository.
- Title format: city in brackets, then job title, then company name.
- Add labels for the desired experience level and the contract type.
- Follow the issue template (.github/ISSUE_TEMPLATE/adicionar-nova-vaga.md).
[São Paulo] Front-End Developer na [NOME DA EMPRESA]Follow the posting rules
The README lists what is not accepted to keep the posts useful. Moderators may comment on an issue, delete it, or ban the user from the organization without prior notice if a rule is broken. The README also asks everyone to use good judgement, since the rules are hard to enforce completely.
Keep each post open for the right time. Every 3 months, the author should comment that the role is still open or close the issue with a comment saying whether the person was hired through the group or elsewhere. An issue left without updates for more than 3 months may be closed by a moderator.
- Not accepted: postings without the company name.
- Not accepted: third-party postings that do not name the company the candidate would work for.
- Not accepted: posts with missing information or outside the issue template.
- Not accepted: more than 3 postings from the same company per month, counted across all its roles.
- Every 3 months, comment that the role is still open or close the issue.
Optional: make a local copy of the repository
The README lists cloning as optional, for those who want a local copy of the repository. You do not need it to browse or post on the board, which the README describes as a web-based process through GitHub Issues.
git clone https://github.com/frontendbr/vagasWhat people use it for
- A Brazilian front-end developer browsing the issues for remote or local openings.
- A recruiter or company posting one front-end role with a city, title and company name in the issue title.
- A developer who follows the repository through GitHub notifications to hear about new posts.
- A junior developer reading recent posts to see the range of front-end roles on the Brazilian market.
Frequently asked questions
Is frontendbr/vagas only for Brazil?
The README is in Portuguese and focuses on Brazil, and the board is run in Portuguese. Non-Portuguese speakers will find the rules and posts hard to use.
Can I post a job on frontendbr/vagas for non-front-end roles?
No. The repository only accepts front-end roles. The README links to separate repositories for other areas, such as back-end, UI/UX, QA and specific technologies.
How do I post a job on frontendbr/vagas?
Open an issue with the city in brackets, the job title and the company name in the title, for example [São Paulo] Front-End Developer na [NOME DA EMPRESA]. Add labels for the experience level and contract type, and follow the issue template.
How many job posts can one company publish?
The rules allow no more than 3 posts from the same company per month, no matter which roles they are. Posts beyond that limit break the rules.
How do I get notified about new front-end job posts?
Click Watch on the repository, then choose Watching. You can receive updates by email or through GitHub notifications, and change the settings in your GitHub notifications page.
Are there alternatives to frontendbr/vagas?
The README lists other vagas repositories, such as backend-br/vagas, vuejs-br/vagas and react-brasil/vagas for specific stacks, and remotejobsbr/design-ux-vagas for UI/UX. It also links to openings.dev for searching and filtering Front-end Brasil posts.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
frontendbr/vagas suits Portuguese-speaking front-end developers, especially those in Brazil, who want to browse or follow posts through GitHub. It is less suitable for non-Portuguese speakers, people looking for non-front-end roles, or companies that need to post many roles at once. Use the separate repositories in the README for other areas.
Install options & downloads