That can have different reasons.
Some clients hire multiple freelancers and set up an early milestone for some testing. Then they continue the contract with the freelancer that delivered the best results. (Not all clients do that, some require samples for free - which you shouldn't do)
Other clients need to hire multiple freelancers because their projects are too huge or because a freelancer doesn't have all skills required to finish the whole project on his own but enough expertise in one specific part of the job and the client doesn't want to miss out on hiring him.
// edit: I just noticed that too, Nichola L Also no need to apologize!
Honestly, I thought it was a bug.
Doesn't it make more sense for the client to just open up two different job postings if they need two different people, instead of having a situation where my proposals feed is full of these so-called active candidacies for jobs where the hiring is clearly over?
I don't see why a client would ever have to miss out on working with somebody if they wanted to, just because they hired somebody else for one specific gig; it's pretty easy to invite freelancers to a new job posting if they are truly interested in working with that person. Plus having things set up this way could, as you said, inadvertently encourage a spec work environment - and that's bad for everybody.
Still getting used to the Upwork platform after Elance, and I just find this feature annoying… It's not very user friendly when I have to scroll through all these old candidacies that are classified as open for no reason before I can find my current opportunities.
There could be various reasons, but sometimes a client will leave a job open, because he or she is leaving his/her hiring options open, and might want to hire someone else for the same job. For example, a client who has a translating job that involves thousands of words - more than one translator could handle - will often hire more than one freelancer, which on Upwork shows as a 'hire'.
And by the way, it is the same on Elance; a job does not automatically get closed when a client hires a freelancer.
Edited to add: Apologies Sebastian, our posts crossed!
re: "which means that he doesn't want anymore freelancers then why would he keep the job open ?"
He may not be a very sophisticated or knowledgeable user.
When I'm done hiring people for a job, I close the job posting immediately. I would hope all clients do the same. But if a person is not so familiar with the system, they might fail to do so. Sorry.
I think it's just a scam to burn up Connects. You can only upgrade to one extra batch per month, they then sell them at $1 each!
The system is obviously designed to NOT close up jobs, even when a contract is accepted and the job in progress.
Is there any way that a client can add a contractor even after the job have been awarded?
Maybe an option to open the job again in case there's an issue with the current contractor?
One thing I've learned is to triple check if Hires: is still 0 / have not reach the number of required contrator in the description.
Sometime, While I'm typing my proposal etc.. Submit my proposal to find out that the client already hired someone. LOL Bad luck, not because the job is still open tho.
I'm pretty sure there's a better way to handle that kind of situation. On Elance, even tho I have typed the proposal, when I press submit, it will just show an error that the job is no longer available if I remember it correctly.
Yes, the client can choose to keep a job posting open or can re-open a closed posting. Some clients need to hire more than one freelancer for a job.