4 ms·

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 go

by CaRDiaK 11y ago

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 shouldn't have a problem with that either.

forgetsusername 11y ago
>as they've seen the goods to influence their decision on the hire Or, they haven't. Which is why articles debating interview coding policies show up on HN almost every day. There is no "one" way. >But if you're any good And yet it's also well known that companies just can't get the engineering talent they require. Where is the discrepancy occurring?
- lordCarbonFiber 11y ago
  As an aside, I can't find any data to support your second point. There seems to be a great deal of talk how companies can't find the engineering talent for bargain bin prices, this is why the H1B visas are so popular. The biggest issue on this site, imo, is that we can't take our heads out of our asses and admit that the vast majority of programming positions are brain dead easy. You don't need a rigorous test to vet the developer you're hiring to make what is essentially a CRUD app (and your product probably fits that description). It's to the point where companies with deep pockets (think finance) don't even bother hiring solely CS students anymore. You can take any reasonable motivated graduate, put them in training for 2 months and pop out a budding developer for your tech pipeline. One two punch of competent tech worker, and company loyalty all in a super cheap package.
alistairSH 11y ago
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.
- stutsmansoft 11y ago
  See I'm the inverse. I'd take the 8 hour project over the whiteboard. Thinking in a quiet, relaxed environment beats trying to reason through a problem while also thinking about how you are "performing."

by CaRDiaK 11y ago

forgetsusername 11y ago

>as they've seen the goods to influence their decision on the hire Or, they haven't. Which is why articles debating interview coding policies show up on HN almost every day. There is no "one" way. >But if you're any good And yet it's also well known that companies just can't get the engineering talent they require. Where is the discrepancy occurring?

lordCarbonFiber 11y ago
As an aside, I can't find any data to support your second point. There seems to be a great deal of talk how companies can't find the engineering talent for bargain bin prices, this is why the H1B visas are so popular. The biggest issue on this site, imo, is that we can't take our heads out of our asses and admit that the vast majority of programming positions are brain dead easy. You don't need a rigorous test to vet the developer you're hiring to make what is essentially a CRUD app (and your product probably fits that description). It's to the point where companies with deep pockets (think finance) don't even bother hiring solely CS students anymore. You can take any reasonable motivated graduate, put them in training for 2 months and pop out a budding developer for your tech pipeline. One two punch of competent tech worker, and company loyalty all in a super cheap package.

alistairSH 11y ago

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.

stutsmansoft 11y ago
See I'm the inverse. I'd take the 8 hour project over the whiteboard. Thinking in a quiet, relaxed environment beats trying to reason through a problem while also thinking about how you are "performing."