You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2024. It is now read-only.
While talking to a potential applicant for the 18F Consulting Software Engineer role, I received feedback on the "Role Summary" section of the job posting. The feedback seemed thoughtful and actionable:
"More of a conversational tone would be good."
"More specifics — what is a typical day like?"
"One line about perks, one line about expectations... make it easy to read."
For inspiration about how to achieve a more conversational tone and make the job posting more readable, scannable, and attractive to candidates, we could look at the Careers page for Glitch, which I think does a good job in these areas: https://glitch.com/about/careers
Addressing this user feedback could involve working with the Writing Lab. Or it could involve gathering a group of interested engineers around a Google Doc to see what improvements we could make without expert outside help.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While talking to a potential applicant for the 18F Consulting Software Engineer role, I received feedback on the "Role Summary" section of the job posting. The feedback seemed thoughtful and actionable:
For inspiration about how to achieve a more conversational tone and make the job posting more readable, scannable, and attractive to candidates, we could look at the Careers page for Glitch, which I think does a good job in these areas: https://glitch.com/about/careers
Addressing this user feedback could involve working with the Writing Lab. Or it could involve gathering a group of interested engineers around a Google Doc to see what improvements we could make without expert outside help.
The text was updated successfully, but these errors were encountered: