Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Which information do you want to see in a job offer for programmers? In which order? What are the most important points for you?

share|improve this question

closed as not constructive by Bryan Oakley, Glenn Nelson, Kate Gregory, gnat, thorsten müller Feb 25 '12 at 14:55

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

It looks like you are expecting a list, which will invite several similar but slightly different answers –  mhoran_psprep Feb 25 '12 at 12:24
When you say "job offer", do you mean "please accept our offer to work for our company for a salary of $xxx"? Or are you asking about a job advertisement? –  Bryan Oakley Feb 25 '12 at 13:24
@BryanOakley I'm talking about a job advertisement –  Camille Feb 25 '12 at 13:38

1 Answer 1

up vote 11 down vote accepted

Here are the most essential ones:

  • Joel Test, with details. This is probably the most important point. If a company has 2/12, it really doesn't worth answering to the offer.

    It's especially important to include details. For example I can understand that a startup doesn't have hallway usability testing, and it's ok for me. On the other hand, no matter what is the company and how many developers are working here, if you don't use source control, you mustn't hire any developer at all.

    For the missing points, it is a good idea to explain why they are missing. For example, you don't have testers because you're a small company with just one developer and one designer. Yes, you care about testing, but you cannot afford a third person for that.

  • Skills/level required from the candidates, written by a person who knows what he's talking about.

    It always surprises me to read job offers written by a person who believes that JavaScript and Java is the same language.

    It also surprises me to read job offers which require 3 years of college. Why they don't want a developer with 15 years of professional experience, but they are ready to hire instead a fresher who doesn't know anything about programming below what he learnt in college?

    The requirements must be precise and reasonable. Don't expect developers with 20+ years experience and deep skills to be excited if all they can do in your company is to write CRUD applications or to maintain a spaghetti legacy codebase they can't even refactor because nobody is ready to pay for that.

  • What the job is about. It's unbelievable how many times I answered to a job offer to discover that it has nothing to do with development at all, and is not suitable for me.

    You don't "search for a developer", in general. You search for a C++ developer who will participate to a project of an OCR application in a team of ten other developers. You search for a Java developer to maintain and refactor your company website and add new features. You search for a guy who is able to build an ETL to process a specific set of data to obtain precise BI results.

  • The type of work. Are you searching for a full-time developer who will probably stay the rest of his life in your company? Are you searching for a person who will participate to a six-months project while doing other projects outside of your company meanwhile?

  • The type of your company (or, better, the name of the company). A startup is not the same thing as a large business started thirteen years ago. They have different management, different spirit.

    More detail is better. If you do TDD, talk about it. If you have QA department, we would like to know it. There is a huge difference between working for a company of two people, both not knowing very much about IT, or working for a large software development company where only 20% of the time is spend actually writing code.

  • The salary. Even if in most cases, the salary depends on the candidate and is negotiated case by case, it's a good idea to know the range the company expect for this job. This allows to eliminate job offers with the salary below expectation and also avoids the ambiguous situations when the interviewee is too afraid to talk about money during or before the interview.

Depending on the job offer, you may need to include additional points.

share|improve this answer
If only there was a way to filter out jobs ads that I am not interested in automatically and intelligently... –  Job Feb 25 '12 at 21:55

Not the answer you're looking for? Browse other questions tagged or ask your own question.