How skills work
Skills on Jobs Web3 are tags on jobs and on candidate profiles: they filter the board, rank applicants by match and, on some jobs, decide who can apply.
Job skills
- Most jobs: skills are read from the job title and, for engineering and security roles, from the description. The description check uses a fixed list: Solidity, Rust, Go, TypeScript, JavaScript, Python, Java, C++, React, Node, Kubernetes, EVM, Solana, smart contracts, zero-knowledge and Move.
- Jobs posted on Jobs Web3: the company picks one to three required skills and up to twelve preferred ones from the site's skill list, plus the languages the role needs.
Reading skills from text can miss some or add a wrong one: the job description states the real requirements.
Profile skills
You add them to your profile yourself, from the same skill list. If a skill is missing, you can suggest it, and a moderator reviews it before it appears.
Jobs Web3 does not check them. The Verified badge confirms identity, not skills.
What skills do
- Filters. Search web3 jobs by what you can do. The Skills filter on the board and every skill page, such as Solidity jobs or Rust jobs, show the jobs tagged with that skill.
- Job alerts. An alert with a skill filter emails you new jobs with that skill.
- Who can apply. On jobs posted on Jobs Web3, only candidates whose profile lists the required skills and languages, and who live where the company can hire, can apply. A company invitation skips this check.
- Ranking. Applicants and Talent Search results are ordered by a match score: required skills count for half, preferred skills for 20%, languages for 20% and location for 10%.
For candidates
Add the skills you would be happy to be tested on, and keep the list current. A missing required skill locks you out of some jobs posted here.
For companies
When you post a web3 job, each required skill shrinks the pool of people who can apply. Keep required skills to the ones the role cannot do without and put the rest under preferred.