How Brazilian frontend developers turned GitHub Issues into a job marketplace

Where do you usually look for a job? Most people go to HeadHunter, scroll through endless Telegram channels, or check Habr Career. In Brazil, web developers did things differently. They took an ordinary GitHub repository, threw out the source code, and moved the entire hiring process to the Issues tab.

The project is called frontendbr/vagas. It has 15,000 stars, hundreds of forks, and not a single line of executable code. The repository consists of a README file, several templates, and clear moderation guidelines. Meanwhile, the platform has successfully replaced commercial job search sites for the local community since 2016.

Why hire through tickets

It seems strange to post a job opening where people usually complain about bugs. But if you look at the platform's capabilities, the idea makes sense.

GitHub already provides a ready-made set of tools for publishing structured content. There's Markdown formatting, a label system, search with filters, and templates for new issues. Candidates don't need to register on third-party portals or fill out twenty identical fields in someone else's forms. They simply open the familiar interface, read the requirements, and immediately see the recruiter's contact information.

The subscription system is interesting. A job seeker clicks the Watch button on the project page and selects Watching mode. After that, notifications about new posts arrive directly to their email or the interface bell.

<!-- Пример стандартного заголовка тикета -->
[São Paulo] Front-End Developer na [NOME DA EMPRESA]
[Remoto] Senior React Developer na Acme Corp

The employer creates a new Issue, fills in the fields according to the template, and adds tags. The community immediately sees the post.

Rules that keep the repository clean

Any open job board without strict control quickly turns into a spam dump from recruitment agencies. The creators of frontendbr/vagas established strict moderation rules from the start, and tickets that violate them are deleted without warning.

The rules are simple but strict:

• Anonymous job postings are prohibited. Companies must specify their real name. No posts like "A major fintech is looking for a developer."
• Intermediaries and recruiters must openly state which exact end client they are hiring for.
• There's an activity limit. One company can post a maximum of three job listings per calendar month.
• Format must follow the template exactly. If a recruiter missed required fields, moderators close the ticket.
• There's a time limit. If the author hasn't left a comment about the search status within three months, the issue is closed as outdated.

This approach solves the main problem for job seekers: it saves time on responses to ghost companies and filters out irrelevant offers from a year ago.

Labels and searching for the right stack

Instead of a complex filtering interface, the creators used GitHub's standard Labels system. Each post is assigned a combination of labels based on experience level, work format, and technologies.

Опыт:     Junior | Pleno (Middle) | Senior | Lead
Формат:   Remoto | Híbrido | Presencial | CLT | PJ
Стек:     React | Vue.js | TypeScript | CSS/SASS

The job seeker opens the filter and enters a search query:

is:issue is:open label:Remoto label:Senior label:React

As a result, the search shows only open remote positions at the desired level. In the ticket comments, candidates can publicly ask the employer questions, clarify the salary range, or point out inaccuracies in the description. The process is transparent for all participants.

How a local idea became a network of repositories

The success of the frontend board led other technology groups to create forks for their needs. Now a network of independent repositories for different development areas has grown around the project:

• By direction: backend, QA, UI/UX design, chatbot development.
• By language: Python, Go, Rust, Kotlin, .NET, PHP, Vue.js, Flutter.
• By geography: separate platforms for developers from Portugal, Angola, and specific regions of Brazil.

They all work on the same scheme. The community moderates its own branches, and employers post positions for free, getting access to a targeted audience without intermediaries.

What this project teaches us

The Brazilian community's experience shows something interesting: you don't always need to write complex backend code and spend money on servers to create a useful service. Sometimes it's enough to take ready-made collaboration tools and layer well-designed regulations on top of them.

This approach works great for Russian-speaking niche communities. If you're developing a local club for Rust, Zig, Elixir, or rare frameworks, setting up such a board within GitHub takes about twenty minutes. You'll need to configure Issue Templates, create a set of labels, and monitor rule compliance.

The frontendbr/vagas repository proves that open tools and clear moderation can replace bulky HR portals when a united community takes charge.