Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Ultimately, I'm not sure what form of interview process would satisfy you.


A work sample test set that is restricted to material relevant for the job you are doing? Only writing code on a laptop text editor?

Ex: Code this mini app, code this mini api, figure out why this code is buggy, design this app / backend service that does this, why did you choose that, etc.


When I started my career a simple interview and can you start Monday sufficed. You’d be be let go by Wednesday if you couldn’t produce. I’d return to that, it worked. Perhaps with a few harder questions about hexadecimal and a code review.


Many people move across the country or even between countries for these jobs, especially to the SF Bay Area. You want more assurance than that before you uproot your life.

Additionally, the time to spin up at a mature company with it's on tooling and enormous amounts of existing code can be really long. I don't think you can generally tell in two days whether a person is going to do well.


If you can do common things well, you can learn a codebase.

Remote contracts are a thing as well.

I'm not sure international hires are relevant to the discussion, they are at best a sliver of the whole.


The biggest problem with this is that in bigger companies it is assumed you will need up to a year to "onboard" and that your first first few months will be drinking from a firehose of custom local knowledge and infrastructure details. We don't expect new hires to be productive for at least a month or three after hire.




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

Search: