If your sending out hundreds of CVs a week (!) consider the poor people at the other end who are receiving those hundreds of CVs a week from developers like you.
Are they going to read every one carefully, or will they look for any excuse to drop it in the trash?
This is an exercise in strategy: do you write five good applications, or a hundred bad applications? What's the most efficient strategy. I choose to go with the first from my experience of applying for jobs, and reading CVs when hiring. But if there's data on the subject...
My worry about the second approach is that can lead to a vicious circle. None of my hundred applications worked out? Next week I will write two hundred, etc, etc.
If your sending out hundreds of CVs a week (!) consider the poor people at the other end who are receiving those hundreds of CVs a week from developers like you.
Are they going to read every one carefully, or will they look for any excuse to drop it in the trash?
This is an exercise in strategy: do you write five good applications, or a hundred bad applications? What's the most efficient strategy. I choose to go with the first from my experience of applying for jobs, and reading CVs when hiring. But if there's data on the subject...
My worry about the second approach is that can lead to a vicious circle. None of my hundred applications worked out? Next week I will write two hundred, etc, etc.
You raise a very good and valid point. Though my situation was more "I need a job and I'll take anything" rather than "This is a job I want".
But you raise a good point, maybe spending a bit more time per CV and sending less out may have done better.