This is great. The best way to see if someone can do the job is to give them a job to do and pilot test. Introducing variables, like interviews, logic games, etc. reduces the likelihood that a potential employer can figure out whether or not you can actually do the job.
I will not do a tech interview
551–554 of 554 posts
Re: I will not do a tech interview
#552Earlier quoted context omitted.
Maybe somebody can explain this better to me -- but if you freeze up in interviews, are you also going to freeze up in developer meetings? During code reviews? When you're in the room with clients? Of course not. Interview situations are very, very different than the others. Meetings and code reviews are with co-workers, whom you know and trust. Meetings with clients could be nerve-wracking for other reasons, but the…
>Of course not. Interview situations are very, very different than the others. Really? I disagree. There even exist situations (in the case of some positions) where you will be talking to a client of the company you're working for, effectively interviewing with the client, representing the company. And interviewing is a subset of "sales", which is important for working on many teams -- including selling management on…
Sure, it sucks for the company that talented people take a look at their process and fire them as employers, but how is that a bad filter for him?
The first impression the company gave him was "we have a bad process" for arguably one of the most important tasks they do - hiring. If they're broken about interviewing, why should he think that the people they do hire are going to be people he wants to work with? Or that any of their other processes are going to be less broken?
My current job (site reliability engineer) gave me a take home programming assignment, and one of the engineers did a code review face to face after I turned it in but before they gave me an offer. The quality of his review was a big factor in me taking the offer - I was impressed that they cared that much about code quality from a non software engineer.
Re: I will not do a tech interview
#553Earlier quoted context omitted.
>It's in fact illegal in most jurisdictions, including California. IANAL, but AFAIK it's absolutely not illegal in California; what's illegal is preventing you from working for a competitor AFTER you quit. I've never had a salary employment contract in California that DIDN'T say they owned everything I did in my off time, at least if I was working on something in a similar domain. The best contracts explicitly state…
That document actually says that YOU own everything you do outside of work, so long as it doesn't use company resources or is directly related to your work at company.
The document most certainly said that my employer owned everything that I did that was related to my employer's business. The thing about working on salary is that there's no punching in and out; just because I'm working at home doesn't mean I'm necessarily "outside of work" -- I worked at home doing paid work for over three years, in fact, seeing the inside of their office only 2-3 days a month.
I work in games. If I do something in my free time that's game-related, it's arguably related to the work my company does.
So I quit and started contracting. Now I own what I work on when I'm on my own time.
Re: I will not do a tech interview
#554Earlier quoted context omitted.
if you freeze up in interviews, are you also going to freeze up in developer meetings? Are you really saying that your developer meetings are as high-stakes as job interviews?
Are job interviews really that high-stakes? There are always more jobs for skilled tech people.
"More jobs" doesn't really matter if you really want to work at a specific place.