311–320 of 646 posts
I implore all of you to stop wasting your life interviewing. Spend your time more productively.
Standard software advice (including the famous Netflix document) is to interview every couple years. It also give you data points on your market worth, which is highly valuable even if you don't switch jobs.
As an anecdote, the major consulting firms (McKinsey, BCG, Bain), all provide constructive interview feedback after interviews. They do this regardless of if the candidate is moving on to the next level of not. It's strange that other industries haven't followed suit.
Earlier quoted context omitted.
Please stop referring to software developers as engineers, unless they are fully registered members of the state association of engineers.
Doesn't apply in my jurisdiction. And even in places where it does, like Texas, I've never heard of it being applied to software. Like Dell doesn't require a degree for their engineer positions.
I think if I introduce myself as a lieutenant, people will think I am brave and action-oriented. But that would be silly because I am not a military/police officer. Words have meaning, just because engineer sounds cool you shouldn't call yourself an engineer unless you are and actual engineer.
Earlier quoted context omitted.
In a vacuum that might be true, but software engineers know other software engineers, and there are plenty of forums for discussing hiring experiences, including HN. If a company systematically treats people they don't intend to go further with like crap, their reputation with other candidates will suffer. You'd like failed candidates to not talk shit about your company when their friend considers applying.
Except, that's the norm. Word isn't going to spread that a company is normal.
Earlier quoted context omitted.
Non paid take home projects... Huge red flag.
I disagree that it's an automatic red flag. 8 hours? Yeah that's too long. But I would rather do a 2 hour take-home project than a 2 hour whiteboard coding interview. Edit to add: as far as getting paid, nobody expects to get paid for an onsite interview so I wouldn't expect to get paid for a take home project either. As long as it takes the same amount of time that the coding portion of an onsite interview reasonabl…
As an anecdote, the major consulting firms (McKinsey, BCG, Bain), all provide constructive interview feedback after interviews. They do this regardless of if the candidate is moving on to the next level of not. It's strange that other industries haven't followed suit.
Earlier quoted context omitted.
Please stop referring to software developers as engineers, unless they are fully registered members of the state association of engineers.
Why? Is there a definition of engineering that does exclude software development, or is membership required to become one?
A lot of software developers call themselves engineers without even having taken physics 101!
I'm so disappointed to read comments on this thread to the effect of "There's nothing in it for the company but risk". I once put in about 8 hours on a take home project at a company (well known in these parts) that I had tremendous respect for, only to get an email back with "sorry, not up to par. We need someone with more experience". I asked them for a couple quick points on what I could have done better. I had ze…
Earlier quoted context omitted.
Non paid take home projects... Huge red flag.
I disagree that it's an automatic red flag. 8 hours? Yeah that's too long. But I would rather do a 2 hour take-home project than a 2 hour whiteboard coding interview. Edit to add: as far as getting paid, nobody expects to get paid for an onsite interview so I wouldn't expect to get paid for a take home project either. As long as it takes the same amount of time that the coding portion of an onsite interview reasonabl…