Here are some guidelines for writing a great job post for GitHub Jobs.
Give your job post a title that sets it apart from others. Try to mention the language or technologies the job requires.
For example, instead of writing
Looking for a good developer
You may want to try something more descriptive:
Seeking bad-ass Ruby specialist for working on rockets
It's important to the reader of the job posting to understand everything they can about the position before contacting you.
Try to answer the following questions in your job description:
- What is the position all about?
- What are the intriguing aspects to the position?
- What will the candidate be responsible for?
- Will the candidate work with a great team or use some new tools?
You should try to describe what makes your company stand above all the others. What kind of culture do you have?
For example, at GitHub, everyone manages their own time. Similar qualities could be something to include in your job post.
When talking about your company, don't be shy. You should mention anything you are proud of and that differentiates your company from others.
Mentioning benefits will help demonstrate how much you care for employees. Talk about any health benefits for employees and their partners, as well as any general benefits to working for you.
When listing skills, avoid including every available technology. Simply listing the main ones in order of importance will help potential candidates scan the list quickly.
Ideally, someone who already does the job should proofread your posting and be able to answer the following questions:
- What is a list of skills that makes sense considering the skill level of the candidate?
- What skills are mandatory?
- If there are secondary skills that you'd like candidates to have or to learn, how important are they?
The total length of the job post is something you should definitely think about. Shorter is always better. After writing your description, edit it down.
The format of your job post really matters. GitHub Jobs supports writing in the standard Markdown format. You should consider using bullet points, links, and headers to make your post more legible.