241–250 of 271 posts
Most companies are going to put it right in the bin at 115K. Not sure if you understand that.
I think 115K for a quality, senior engineer is not unreasonable (even for a remote job). I received an offer for a pure-telecommute job (which I declined) for slightly above that figure a month ago.
Earlier quoted context omitted.
>I earned 220k last year, all remote Are these short or long term contracts? Or a permanent position?
Long term contract, I just passed over a perm gig for $140k + benefits and options which would be close to the same in terms of total compensation. I mainly do very large JavaScript apps with Dojo and jQuery, I also do iPhone and Android development. Ruby and ROR are similar in compensation to those technologies.
I'm going to say it because it seems no one else is. I apologize ahead of time for my brutal honesty. You need to consider the possibility that you're not as competent as you believe yourself to be. Dunning-Kruger[0] is real, and your post doesn't demonstrate the self-awareness the best developers seem to possess. Your writing is sprinkled with emoticons and rife with reduplicated punctuation, both of which (especial…
This may be a common attitude, but I hope you're aware that it is quite inconsiderate to the person in the long run. Yes, it is painful to tell people they suck. It may be terrible to do it during the phone interviewing process. But have you at least considered following up with a brief email telling the person that the interview actually didn't go that well?
Yes, this is a potential minefield. But if you never give people this type of feedback, how are they going to improve?
Earlier quoted context omitted.
What is your local market?
Orange County, CA
Given the cost of living in the area, 70k for a senior developer is a nightmare for everyone, but the fact is there's no shortage of people willing to make the trade so it works for you guys and that is fine. There's a bit of a blowback though, because of the low salaries and beliefs they are normal, it's not the best place to start a company doing anything cutting edge that requires the top tier of talent, and that's why all the really cool stuff is still in the Bay and will probably always be there.
Earlier quoted context omitted.
Re: weird extra steps: the idea isn't that they're cool. The idea is that if you are willing to attempt it and solve it successfully, it says something about your problem-solving skills. It's not the be-all end-all, but it seems like a decent first-pass filter. The problem is that you're asking candidates to spend 1+ hour before you've even given them a personal response. I've seen positions with well known companies…
I fought really hard to keep my hiring process from requiring a time intensive hoop for candidates to jump through. I felt that it would put off all but the most desperate. Desperate isn't what I was looking for.
Earlier quoted context omitted.
I'm curious, and maybe a bit skeptical. Why does it bother you that your role is needed?
I'm naturally frustrated by the fact that I know less about the positions I am trying to fill than both the hiring managers and the applicants. It takes a lot of work to learn where I can and can't add value.
I'm going to say it because it seems no one else is. I apologize ahead of time for my brutal honesty. You need to consider the possibility that you're not as competent as you believe yourself to be. Dunning-Kruger[0] is real, and your post doesn't demonstrate the self-awareness the best developers seem to possess. Your writing is sprinkled with emoticons and rife with reduplicated punctuation, both of which (especial…
I do interviews at a large Internet company, and one of my goals--one of the goals that I've been trained to seek--is to ensure that the candidate, no matter how bad, walks away from the interview feeling good about himself/herself and the company. If you're doing really poorly in an interview, I'll toss you some easier questions than I normally give, because I have all the information I need, and I don't want you to…
It's, as you claim, painful, and the net gain for the company is close to zero. Why do it?
I'm going to say it because it seems no one else is. I apologize ahead of time for my brutal honesty. You need to consider the possibility that you're not as competent as you believe yourself to be. Dunning-Kruger[0] is real, and your post doesn't demonstrate the self-awareness the best developers seem to possess. Your writing is sprinkled with emoticons and rife with reduplicated punctuation, both of which (especial…
"API's"
"potentially/maybe/sorta/kinda/probably/possibly"
"Machine learning ...." Earlier quoted context omitted.
"...6 people interviewing me serially. That sort of thing is grueling..." This sort of thing is a standard process in many companies - precisely to avoid the single-person bias mentioned in other post. Besides, the interviewers (in the properly organized case) are usually one's future coworkers - and if you did not like them maybe working there would not have been a good idea for you to begin with. "...didn't have mu…
Well I guess if your goal is to have me not take the job but to have a "co-worker" learn then they accomplished their goal. If it wasn't that, then having a bad interviewer on his own was a complete waste of my time and of the other 5 people who I interviewed with that day.
On the other hand, ditching your rounds with the subsequent interviewers just because you became emotional about one of them does materially decrease your chances to get a job - instead of one "bad interview" round feedback you got that one plus all the subsequent ones. This is a sub-optimal strategy. And, arguably, a waste of both your time and the remaining interviewers'.