Hacker News new | past | comments | ask | show | jobs | submit login

>- How do you verify that the reviews are actually from current/former employees?

People who write review would have to upload recent pay slip or after when committing review provide their email at employee to receive some passcode active within 2 months

>- Can the data be open for the public to verify while protecting the people leaving reviews?

Verification explained above. Token to employee at employer domain email would be anonymous. Reviews would be randomly visible within 1-8 weeks after submission.

>- How could the service get funding? Donation model?

Jobs advertisement ads and website getting commission if someone got hired from advertised jobs like most agency get. Hired person would get small bonus for confirming got accepted.

>- How would you overcome the initial issues with trust?

Just reliable reviews that got verified with payslip and domain email and maybe even passport just to make sure employer doesn't create dozens of fake payslips and domain emails.

>- How do you prevent companies from manipulating the scores/reviews?

See above

>- How do you handle legal challenges if you're based on something like a donation model? Companies would surely sue you at one point or another if they cannot take down reviews themselves

Just create account in some law friendly country. Don't store any user data such as passport, payslip, user employee emails etc - after verifying just delete those




> People who write review would have to upload recent pay slip or after when committing review provide their email at employee to receive some passcode active within 2 months

If I was leaving a review, even if I cared about it a lot, and I'd have to upload a recent pay slip I'd just leave the site and not bother with it anymore.


Any data-breach would be an utter nightmare for the users with that sort of info on the site.


The idea would be not to store those data on server only process it and keep anonymous data or even only aggregated. Some processing maybe could be done also on the client or payslip user name masked after verifying it matches passport holder locally before sending to server. Other option using blockchain with open source repo.

I know a lot of HN users are in theory very distrustful about anything new but in practise still:

- using VPNs (even paid one don't guarantee your data is safe)

- tor

- open source password managers (w/o reading source code)

- Dropbox etc

- compiling random open source code first without reading

- having no issue telling hour rate or daily rate recruiter on linkedin when asked and attaching resume.

So what's so very sensitive in payslip if you already providing this kind of information to any recruiter?


> So what's so very sensitive in payslip if you already providing this kind of information to any recruiter?

Domestic violence victims who are trying to avoid being found? People seeing political asylum? Anyone who wants to maintain privacy? There's a number of reasons you would not want this information in pastebin.


> So what's so very sensitive in payslip if you already providing this kind of information to any recruiter?

I know 0% people out of my circle who would share payslips with any potential employers, even less any recruiter, while we frequently talk about our pay with each other and co-workers at our work.


Ok but genuine question why? Does in other countries payslip has any other more sensitive information than name, company and salary? Any more sensitive information than CV you attaching to recruiter?


Yes: in the US, your SSN (or EIN) is on every single paystub. (You could always manually redact it if some third-party asks for a copy).

By the way, another huge reason: images of paystubs can be and have been used by identity thieves to open fake accounts/loans, remotely.


> - open source password managers (w/o reading source code)

The open source qualifier here is weird, like you're implying closed source managers are preferable, but then your objection can hardly be over reading the source code


> People who write review would have to upload recent pay slip or after when committing review provide their email at employee to receive some passcode active within 2 months

The employer controls their email domain.


>People who write review would have to upload recent pay slip or after when committing review provide their email at employee to receive some passcode active within 2 months

No sane person is uploading a pay slip so they can leave a review on some internet site. In fact, I'd daresay the only reviews you'd see at that point are from individuals (or companies) with sufficient incentive to generate convincing-looking fake pay stubs.


Would they also risk making convincing fake passport that has the same name as fake payslip? Not a lawyer but this probsbly could be considered a fraud.


>Jobs advertisement ads and website getting commission if someone got hired from advertised jobs like most agency get. Hired person would get small bonus for confirming got accepted.

>Just create account in some law friendly country. Don't store any user data such as passport, payslip, user employee emails etc - after verifying just delete those

The more you try to detach from the countries that will (possibly) make you retain that information (or block you from collecting it) the harder it is to do business with companies from those countries (or to enforce contracts against them for things like commissions).


Your model would get you a grand total of 5 users.


if we're not counting the internal devs & testers, I'd take the under


>- How could the service get funding? Donation model?

I have a more hellish proposal: want to publish a review? Pay. Want to see reviews? Pay.

Small amounts of course, but I would like to see someone actually sign off assigning a budget for something like this in a sufficiently large organization.


> Jobs advertisement ads and website getting commission if someone got hired from advertised jobs like most agency get.

If you rely on income from the same companies that are reviewed on your site it will inevitably become just as bad as glassdoor




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: