Content pfp
Content
@
0 reply
0 recast
0 reaction

positron pfp
positron
@positron.eth
One thing I have seen hiring web3 teams struggle with the most, is job descriptions. Here are 5 tips that I recommend to my teams 🚀
5 replies
0 recast
4 reactions

positron pfp
positron
@positron.eth
Humans have a relatively short attention span, and combined with the fast-paced nature of web3, it's easy to lose a candidate's interest. Make the descriptions as short as possible 📝 So what should the JD include?
1 reply
0 recast
0 reaction

positron pfp
positron
@positron.eth
🎯 Mission I suggest allocating a good portion of the JD towards explaining your mission. Use this section to describe the person's impact on building toward the mission compared to directly moving on to listing the requirements (like in the web2 style JDs)
1 reply
0 recast
0 reaction

positron pfp
positron
@positron.eth
🤠 Titles As fun as they may seem, avoid using unique titles (e.g. coding ninja). Instead try to think about what title your target candidate would enter in the search engine. Experiment with titles and compare the kind of talent you attract.
0 reply
0 recast
1 reaction

positron pfp
positron
@positron.eth
Take the applicants perspective. What do you think they value when they look for a new job? 👇
1 reply
0 recast
0 reaction

Ivy pfp
Ivy
@ivy
this is such good advice, really contextualizes what makes web3 unique well
0 reply
0 recast
1 reaction