There are also two cases with the worldwide option. A company hiring worldwide allows the employee to set his/her own schedule/working in own timezone. For example, remote Indian can work in IST and chat/stand-up/meeting in company timezone. Some companies may want the remote employee to work in their timezone say EST. Here comes the individual preference, some remote Indians may like working in the night or some in the day. Setting the expectations clearly in the job description will save the time of both company and applicant.

Agreed !! Obviously if companies are willing to share their listings on our job board, then I will make sure that happens ( and it is pretty much inherent from the tagline). But then it's a far off dream. At this moment of time, I want to experiment with a crowd filtering exercise to get high quality data for the community. Because I don' want to spend time in writing scrapers and even the best of scraping algos might find it difficult to infer whether an opportunity is relevant for the community or not. I admit this approach is not scalable (and it is very much dependent on the community), but I feel it has the potential for value addition to our community. Once we have more people on board, then we will have more bargaining power in the whole process. But for now, we will have to embrace the constraints !!