Saturday, October 27, 2012

Job Descriptions

I've been always curious to see job descriptions when someone reaches out to me about software engineer (or related) positions. Most of them don't really have anything uncommon, but sometimes you see something in them that could be an indication of how the company takes software development and what they value.

For instance,
  • "Write code that is art": this is the first time I see (or perhaps noticed) art in a job description. It is so nice a description with that (see my post Software As Art), as it may indicate a team/company/manager that seems it beyond utilitarism.
  • "Professional and Technical Competencies": it's good to see the word "professional", as that could indicate that this company may want to do things in a professional way.
  • "Use SOLID design principles and patterns.": this means, first of all, that someone at that company knows design principles. Points for that. And they seem to value them. So a bandaid code should be detected and not encouraged, as they should not be using any good principles or patterns.
I know what, if I have to write a job description in the future, I'll put these small signs in the text to those who are paying attention and looking for them.
Post a Comment