221–230 of 524 posts
A couple of months ago I did a 'homework' assignment for an interview (it involved writing a simple REST service in go, even though I have at least one personal project demonstrating exactly this skill -- to an even greater degree -- in my github profile). During the phone-discussion after turning in the project, the mid 20-something lead developer couldn't find anything to nitpick (I could have) and even told me he…
Earlier quoted context omitted.
A's hire A's and B's hire C's. http://www.hrdusa.com/As_hire_As.html
And since everybody knows they're an A, the only explanation for a 'no hire' decision must be that the interviewer is a B.
Funnily enough, often people who clearly are top rate don't think so (impostor syndrome). Dunning–Kruger appears to be very healthy in development circles.
Not writing code for a potential employer or being asked to in an interview is a warning flag to me personally. I feel better if they do, as they've seen the goods to influence their decision on the hire. It's more about "How does this person think, how do they approach the problem". How can you measure that unless you're there? I see a lot of "I shouldn't have to do that". Well yeah, ok. But if you're any good, you…
Well yeah, ok. But if you're any good, you shouldn't have a problem with that either. Whiteboarding, sure. Homework assignment that takes 8 hours, as the author experienced? No way. I'm good, my hourly rate reflects that, and I don't work for free.
Thinking in a quiet, relaxed environment beats trying to reason through a problem while also thinking about how you are "performing."
A couple of months ago I did a 'homework' assignment for an interview (it involved writing a simple REST service in go, even though I have at least one personal project demonstrating exactly this skill -- to an even greater degree -- in my github profile). During the phone-discussion after turning in the project, the mid 20-something lead developer couldn't find anything to nitpick (I could have) and even told me he…
That is correct. The market is so flooded with workers that ageism is easily affordable.
You can keep trying if you want but the suggestion "it will all work out if you just try harder because the system is ultimately rational" is inaccurate and unproductive. If you glance around the work place and count the percentage of people 10 years older than you, you can guesstimate the odds of continued employment.
dfraser992 advice is, unfortunately, they way the world really works: neither ageism nor the flood of workers is going to be widely admitted to let alone addressed in the foreseeable future.
A couple of months ago I did a 'homework' assignment for an interview (it involved writing a simple REST service in go, even though I have at least one personal project demonstrating exactly this skill -- to an even greater degree -- in my github profile). During the phone-discussion after turning in the project, the mid 20-something lead developer couldn't find anything to nitpick (I could have) and even told me he…
> ... and even told me he thought I was a better programmer than him. Probably that's exactly why you were ignored. The guy was scared of competition. (Maybe they were looking for a tech lead and he felt threatened by your expertise.)
Earlier quoted context omitted.
They want someone who uses asynchronous programming in coffeescript to build a blog and use shit load of preprocessors and if the library was just released on HN they expect you to use it in production and deal with it. Don't do these take homework projects. Don't work for free.
My company has you write a simple twitter clone using the php framework we use. If you know the framework, it shouldn't take you more than an hour, if that. I see nothing wrong with simple projects like this. We only ask you to do it after your initial interview to make sure you're a fit personality wise.
A couple of months ago I did a 'homework' assignment for an interview (it involved writing a simple REST service in go, even though I have at least one personal project demonstrating exactly this skill -- to an even greater degree -- in my github profile). During the phone-discussion after turning in the project, the mid 20-something lead developer couldn't find anything to nitpick (I could have) and even told me he…
> A couple of months ago I did a 'homework' assignment for an interview (it involved writing a simple REST service in go, even though I have at least one personal project demonstrating exactly this skill -- to an even greater degree -- in my github profile). I would have asked them to look at that code and ask me any question they have about it. If they are not willing to do that I wouldn't have bothered continuing t…
A couple of months ago I did a 'homework' assignment for an interview (it involved writing a simple REST service in go, even though I have at least one personal project demonstrating exactly this skill -- to an even greater degree -- in my github profile). During the phone-discussion after turning in the project, the mid 20-something lead developer couldn't find anything to nitpick (I could have) and even told me he…
Ageism is a thing in our industry. This may not be it but in other professions it is uncommon for those in the middle of their career to be applying for positions cold, there is usually an intro involved or in the case of the medical fields credentialing does this. As engineers we have poor soft skills that lead to weak professional networks (we think of our selves as mercenaries) and we don't have credentials of any…
Yeah, I dunno. I mean, some have poor soft skills, definitely. But I would argue that engineers in many companies are simply insulated more than other groups. The biggest reason for this is that Engineering is thought of as a cost center, which has a number of resulting consequences.
Other groups like Product are exposed to many other groups (Sales, BD, Exec, Engineering) and so naturally their networks are larger and more diverse.
A couple of months ago I did a 'homework' assignment for an interview (it involved writing a simple REST service in go, even though I have at least one personal project demonstrating exactly this skill -- to an even greater degree -- in my github profile). During the phone-discussion after turning in the project, the mid 20-something lead developer couldn't find anything to nitpick (I could have) and even told me he…
It's not a lie, you just forgot the last half of that sentence. "It's hard to find good developers, who are willing to work for the peanuts I'm offering."