Hacker News new | ask | show | jobs
by chpmrc 2769 days ago
Don't worry, it won't turn into a public shaming list, we already thought about that. We will update the form to make this clear.
1 comments

How can you release the all the data about bad recruiters publicly without making it a public shaming list?
We will only release data about companies, not individual recruiters. We will then use their name to (try to) get their contact details and send them a link to the data so that they can be more aware of how their actions affected (and how many) people. What we're doing should ideally benefit both sides, not just us.

Hence why I said we should make this more clear, as in: we're not going to publish the names of the individual recruiters.

You're currently collecting this data under false pretenses. If you care about unprofessional behavior and giving people bad experiences, you should remove the line about releasing all the data to the public from the start of your survey.
No we are not. We are clearly stating that the data will be publicly available EXCEPT for those fields where the opposite is explicitly indicated. I really don't see how this could be more clear.

EDIT: by the way we updated the related field so that it's clear that the recruiter's name might be shared with the agency (but without releasing anything else about the entry to avoid tracing it back to the candidate). If you have any suggestions on how to communicate this better we would really appreciate it. Thanks!

Your front page still says

> We are collecting stories from devs all over the world and plan to release all data to the public (for free!) so that no more fellow devs will have to suffer

If I filled your form out, I would expect that all the data I entered would be released to the public. You then turn around and contradict that in the form, making it less clear about what I should expect. You need to be consistent in both places, and link to a more detailed explanation on how this data will be anonymized and shared.

This also makes it less clear whether other fields will be shared publicly. Is field 7 going to be public or is it just something I'm sharing with you? I'm honestly not sure about that now.

What's more clear than being explicit about which fields will be published and which not? IMHO adding that to the main page is redundant and a waste of time and space.

Specifically about field 7 are you suggesting we rephrase the description? If so how?

We can definitely work on a page that explains the process in more detail once we decide exactly how to proceed.