|
|
|
|
|
|
by awaythrow101
3236 days ago
|
|
|
I've been leaning toward that perspective recently. I actually had a remote job in the pipeline but they ended up not being able to pay a commensurate salary or benefits (i.e. it was a significant pay cut from what I'm making now). At least this process has got me back to studying data structures and algorithms again, so perhaps I can interview at Google Pittsburgh again and try for a better outcome this time. Any tips for finding a good remote position? |
|
|
Always be looking, and don't relax your criteria (compensation, work/life balance) because its remote.
Just because a position is advertised as on site doesn't mean you can't negotiate it to be remote.
Here are some remote job resources I keep bookmarked:
https://remotebase.io/
https://github.com/lukasz-madon/awesome-remote-job
https://remoteok.io/
https://weworkremotely.com/
https://stackoverflow.com/jobs/remote-developer-jobs
https://www.wfh.io/
https://jobmote.com/
Salary negotiation cheat sheet: http://salarytutor.com/wp-content/uploads/2015/08/Salary-Tut...