Show HN: HackerSurf – All the hacker jobs in one place
hacker.surf
hacker.surf
If I apply to work at a company remotely - how do I know that I'm not getting screwed over (not paid)? I'm 19 and some of my friends have gotten screwed over by a few foreign employers whilst working remotely. Do You have any tips to find a good place?
- Get paid some percentage up front
- Set out milestones throughout the project where you get paid an additional percentage
If they don't pay when a milestone is completed, development stops. This limits your risk exposure to a percentage of the project rather than the whole thing.
If you are in fact applying to be a remote full time employee, I would do my research on the company before applying. Has anyone else had payroll problems with this company? The same freelancer rules above apply though; if they start to miss paychecks, you start looking for a new job.
To add to this, I would ask new clients for a few days pay up-front as a sign of good faith.
There were several clients who ran away, absolutely outraged, they'd never heard of anyone asking something so ridiculous in all their life!
Running away screaming was very rare though, and by some good fortune, all of my regular clients were an utter delight to work with.
Stick to your guns though: get paid up-front, and invoice as often as you can. (Weekly in my case).
Offering clients a small discount for paying for a good chunk amount of development time in advance also worked well for me. (Lowest I'd typically go was 2 months with a 5% discount).
A feature that would be nice for us europeans, considering a massive fraction of the jobs are in the US, would be a map to see the ones closer to us.
http://careers.stackoverflow.com/jobs
I did have a scan of the source code but I'm none the wiser.
I'd like to see an uncheck all. Or an easy way to just target one site, instead of having to uncheck all but that site.
Probably the next thing would be to pull in the Who's Hiring - https://news.ycombinator.com/item?id=8681040 - then scrape and parse it and incorporate it into the site somehow.
:)
Scraping is easy. Trying to figure out the best way to parse/display is hard.
For example, the whoishiring user[0] gives convenient access to every post[1] that would interest you.
0 = https://hacker-news.firebaseio.com/v0/user/whoishiring 1 = https://hacker-news.firebaseio.com/v0/item/8681040
Let me know if anyone's interested.