<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.odesk.com/community" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>oDesk Community - Buyers posting same job twice, hiring 2nd, and leaving 1st posting open. - Comments</title>
 <link>http://www.odesk.com/community/node/4057</link>
 <description>Comments for &quot;Buyers posting same job twice, hiring 2nd, and leaving 1st posting open.&quot;</description>
 <language>en</language>
<item>
 <title>thanks</title>
 <link>http://www.odesk.com/community/node/4057#comment-11421</link>
 <description>&lt;p&gt;Yang,&lt;/p&gt;
&lt;p&gt;Thank you for clarifying that for me.&lt;/p&gt;
&lt;p&gt;Perhaps a method could be implemented that would allow users to see when there are one or more active hires currently assigned to the still-open job (and notify existing Candidates and Interviewees of the update). &lt;/p&gt;
&lt;p&gt;This would let prospective Applicants know that the job is still active ( rather than collecting dust). At the same time, it would provide existing Candidates and Interviewees with information on the status of the project for which they applied. They could then use that information to update or retract their candidacy and/or direct their focus towards other projects as they see fit.&lt;/p&gt;
&lt;p&gt;~Jeff&lt;br /&gt;&amp;nbsp;&lt;/p&gt;
</description>
 <pubDate>Mon, 21 Jul 2008 19:40:24 -0700</pubDate>
 <dc:creator>jwichman</dc:creator>
 <guid isPermaLink="false">comment 11421 at http://www.odesk.com/community</guid>
</item>
<item>
 <title>Hiring and keeping job open is perfectly okay</title>
 <link>http://www.odesk.com/community/node/4057#comment-11415</link>
 <description>&lt;p&gt;Jeff, what you are seeing is a result of our implementation rather than any buyer intent. When a buyer posts a job on oDesk and then hires a provider for the job, he is given the option to either close the opening (if he&#039;s done hiring) or hire but still keep the job open so he can continue to interview other providers. In the latter case, you would see a clone of the original opening with a single candidate that is immediately hired. I believe this is exactly what happened in the 2 cases that you&#039;ve observed. We apologize for the confusion. This is a legacy implementation issue rather than improper buyer behavior.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Yang&lt;/p&gt;
&lt;p&gt;oDesk&lt;br /&gt;&amp;nbsp;&lt;/p&gt;
</description>
 <pubDate>Mon, 21 Jul 2008 15:10:20 -0700</pubDate>
 <dc:creator>yang</dc:creator>
 <guid isPermaLink="false">comment 11415 at http://www.odesk.com/community</guid>
</item>
<item>
 <title>Buyers posting same job twice, hiring 2nd, and leaving 1st posting open.</title>
 <link>http://www.odesk.com/community/node/4057</link>
 <description>&lt;p&gt;I am curious as to why I have noticed (at least 4 or 5 times) a Buyer will post a job opening and then a few days later re-post the same job, often with the same title and description, and in the same category. I noticed this last month and just thought it was weird, but I was looking over some old candidacies today and found two more examples of this (two different Buyers). Oddly enough, both of these examples show the buyers re-posting a job, and then (the same day) hiring a single Provider who applied for the job. &lt;/p&gt;
&lt;p&gt;As a Provider, this adds just another ghost candidacy to our candidacy list, and a pointless job posting to the Job index (which means people are spending time writing cover letters for jobs that are already filled). I suppose one could keep double-checking each posting, or manually ending these particular candidacies, upon realizing the Buyer has already filled the job under another posting... but I&#039;m curious as to why these second postings are occurring to begin with. Admittedly I am unfamiliar with the Buyer interface and any advantages that such a strategy may or may not provide. My first guess was that perhaps a Buyer is posting in multiple categories or simply &amp;quot;bumping&amp;quot; their listing, but why then are both of the examples I have showing a single candidate hired on the same day of the posting? Perhaps there is some kind of database issue going on?&lt;/p&gt;
&lt;p&gt;Anyways, I&#039;m not sure whether or not it&#039;s offensive to the parties involved, so I&#039;ll hold off on posting the links for the duplicates until a mod. gives me the go-ahead. &lt;/p&gt;
&lt;p&gt;~Jeff&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;form action=&quot;/community/crss/node/4057&quot;  method=&quot;post&quot; id=&quot;nodevote_form&quot;&gt;
&lt;div&gt;&lt;fieldset&gt;&lt;legend&gt;Vote Result&lt;/legend&gt;&lt;div id=&quot;nodevote result&quot;&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;img src=&quot;/community/modules/contrib/nodevote/star_off.png&quot; alt=&quot;-&quot; /&gt;&lt;/div&gt;&lt;div id=&quot;nodevote result&quot;&gt;Score: 0.0, Votes: 0&lt;/div&gt;&lt;/fieldset&gt;
&lt;input type=&quot;hidden&quot; name=&quot;edit[form_id]&quot; id=&quot;edit-nodevote-form&quot; value=&quot;nodevote_form&quot;  /&gt;

&lt;/div&gt;&lt;/form&gt;
</description>
 <comments>http://www.odesk.com/community/node/4057#comment</comments>
 <category domain="http://www.odesk.com/community/taxonomy/term/22">Feedback</category>
 <pubDate>Mon, 21 Jul 2008 14:27:20 -0700</pubDate>
 <dc:creator>jwichman</dc:creator>
 <guid isPermaLink="false">4057 at http://www.odesk.com/community</guid>
</item>
</channel>
</rss>
