This file was last updated in 2017, so it's perhaps time to update it.
Changes
Requirements/preferences changes:
Removes full LAMP stack and replaces it with a requirement for PHP/MySQL with a preference for Apache/Nginx. We don't really do server admin stuff.
Changes server-side programming language experience from a preference to a bonus, because we haven't done any of that recently.
Adds preference for local scripting languages, and explanation of how we use them.
Replaces generic version control requirement with a Git requirement with GitHub preference.
Adds React as a preferred frontend framework.
Wording changes:
"Strong communication skills" was listed, but not as either a requirement or a preference. I've made it a requirement here, and rewritten the following sentences to better explain why.
Cosmetic changes:
replace bolded headings with actual h2 headings
colons after labels in the summary section
splits up the dataviz/photo/illustration/design item
Questions for review
[ ] Does this match our most-recent job postings?
[ ] Does this match new team members' experience of our requirements and preferences?
[ ] Should we separate preferences from requirements, or otherwise highlight which things are required versus preferred versus a bonus?
[ ] The description opens with "Working closely with our senior developer" — do we need to make a senior dev position description?
This file was last updated in 2017, so it's perhaps time to update it.
Changes
Requirements/preferences changes:
Wording changes:
Cosmetic changes:
h2headingsQuestions for review