A Method I’ve Used to Eliminate Bad Tech Hires
11–20 of 517 posts
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#12This system is interesting but has a crucial flaw: I legally can't take part. I have a job now, which claims ownership over any tech-related IP I create. There are processes for getting exceptions, but a) you won't get them for actual job-related things b) I'm not asking Google for an exception so I can interview somewhere else. This is true for nearly anyone with a standard SV job. So if you're willing to restrict y…
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#13This system is interesting but has a crucial flaw: I legally can't take part. I have a job now, which claims ownership over any tech-related IP I create. There are processes for getting exceptions, but a) you won't get them for actual job-related things b) I'm not asking Google for an exception so I can interview somewhere else. This is true for nearly anyone with a standard SV job. So if you're willing to restrict y…
Playing devil's advocate here: how will this come back to bite you if you do it on your own time and equipment? How would the current employer know to care? Not saying you should require your candidates to break the law. Also, though IANAL, California does have laws that give employees the right to their own IP on their own time/equipment when it doesn't use work IP https://news.ycombinator.com/item?id=2208056 )
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#14I wish more companies would give example problems to solve in your own time. I did one for a fairly large Australian company, and they rejected it. By the time they got round to letting me know (very long turn around time) I had already found other employment. But still, their reasons for rejecting my solution - the output was not formatted to their liking, and they didn't seem to know what an anonymous function was…
"You should just find that out upfront" I hear you saying. Well that is not always possible. Recruiters either don't know the range, or lie about not knowing, or you have to submit a big packet of info (cover letter, history, resume, homework) before you can even talk to a human about salary.
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#15Closet thing I've been offered ironically was rather tough sys administration tasks for no pay for a few gigs (5 hours of work) or asked to solve an obscure ntp issue on a Linux server they couldn't figure out.
For programming jobs? Never.
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#16Re: A Method I’ve Used to Eliminate Bad Tech Hires
#17Re: A Method I’ve Used to Eliminate Bad Tech Hires
#18This system is interesting but has a crucial flaw: I legally can't take part. I have a job now, which claims ownership over any tech-related IP I create. There are processes for getting exceptions, but a) you won't get them for actual job-related things b) I'm not asking Google for an exception so I can interview somewhere else. This is true for nearly anyone with a standard SV job. So if you're willing to restrict y…
By that interpretation, you can never legally take part in a whiteboard coding session during an interview either since the code you whiteboarded also belongs to your current employer.
There is such a thing as being too literal.
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#19This system is interesting but has a crucial flaw: I legally can't take part. I have a job now, which claims ownership over any tech-related IP I create. There are processes for getting exceptions, but a) you won't get them for actual job-related things b) I'm not asking Google for an exception so I can interview somewhere else. This is true for nearly anyone with a standard SV job. So if you're willing to restrict y…
I'm probably in that pool. Really, I'm not creating anything of massive value by doing a little example project. If my employer wants to sue me over it they can go ahead. I will probably lose, but they will have a rep for suing people for taking interviews.
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#20This system is interesting but has a crucial flaw: I legally can't take part. I have a job now, which claims ownership over any tech-related IP I create. There are processes for getting exceptions, but a) you won't get them for actual job-related things b) I'm not asking Google for an exception so I can interview somewhere else. This is true for nearly anyone with a standard SV job. So if you're willing to restrict y…