News for hackers. Stuff that matters.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by ryandrake on Wednesday August 03, 2016 @12:26PM (#12219153)
Yea. I think a lot of people might think the hiring market is healthy and that there are jobs everywhere purely based on the volume of recruiter spam in their inbox. In reality, tons of companies are INTERVIEWING but nobody seems to be HIRING.

I've got almost 2 decades of experience as a programmer, project manager and product manager, and I still estimate that, given the job market these days, it would take 1-6 months to line up another job if I started today. I've not seen an environment where you could "get another job on Monday" since 1999.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @12:31PM (#12219205)
You're too old. This gets back to the basic 'ageism' issue in tech, which is real and alive for many, and discounted as non-existent by others (usually much younger folks!)

Most of the 'older' tech folks I know take a while to get new jobs - took a friend of mine more than 9 months. This has nothing to do with actual skills/abilities, it's (at best, being charitable here) perception of skills/abilities.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by ryandrake on Wednesday August 03, 2016 @01:00PM (#12219487)
Yea, I'm sure ageism is part of it. But something definitely seems different nowadays (from both the interviewer and interviewee side of the desk), compared to 1999 or even 2005-2006. The focus these days seems to be "Find out ways to disqualify the candidate" and "Haze the chump", rather than "Find a good reason to hire him/her and then do it! We have a product to make!"
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @04:45PM (#12221358)
> But something definitely seems different nowadays (from both the interviewer and interviewee side of the desk), compared to 1999 or even 2005-2006.

You're 17 years older :)

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jazzyk on Wednesday August 03, 2016 @05:56PM (#12221880)
Yes, it is different - the economy is in the dumpster.

Official reports herald 1-2% GDP growth rate, but if you realize the inflation is more like 5-6% rather than the official 2% , the economy has, in reality been contracting.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by achompas on Thursday August 04, 2016 @03:48AM (#12224069)
These growth rates touted in newspapers etc. are always adjusted for inflation.

Source: I worked on these forecasts for 2 years.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jazzyk on Thursday August 04, 2016 @10:36AM (#12225776)
That was exactly my point - they are adjusted for 2% inflation, not the actual 5% inflation.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by elliotec on Wednesday August 03, 2016 @12:50PM (#12219382)
This is not discounted as non-existent by anyone. Ageism is a very clear and apparent problem to anyone. As a millennial, i know a lot of people who are clearly "ageists" but almost all of them have been gen x and my millennial peers are very aware of these things. I'm not saying millenials aren't to blame as well, but anecdotally the problem seems to stem from the generation above me and the generation below those who are feeling the ageism
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by superuser2 on Wednesday August 03, 2016 @01:05PM (#12219526)
Any time ageism comes up on HN, someone trots out "the people who are complaining about being victims of ageism just haven't been keeping their skills up to date; keep learning new things and you will be fine." It generally goes unchallenged. I would consider that to be discounting ageism as nonexistent.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by AnimalMuppet on Wednesday August 03, 2016 @03:47PM (#12220921)
I don't know if I have ever experienced actual ageism. Here's what I've found, though:

- If you want somebody who will work 14-hour days, well, that eliminates most people over 40.

- If you want to pay appropriate to someone who's 25, well, that eliminates most people over 40.

- If your company is a pit, if your management is insane, if your coworkers are psychopaths, well, most people over 40 have seem that enough times to not go there.

I've seen companies advertising for "senior software engineer". They want 5-7 years of experience. I've got 30. They don't want to pay for 30. Is that ageism? Or am I just too expensive? Or does my experience exceed the hiring manager's ability to correctly value?

I'm not saying that ageism doesn't exist. But I am saying that there are some reasons other than ageism that older software engineers find it harder to get hired.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by morgante on Wednesday August 03, 2016 @06:49PM (#12222111)
Tech is, ultimately, an up or out field.

The marginal return to experience is minimal after a decade or so, particularly when it comes to the average software job. If you have decades of experience, you need to be in a higher leverage position (either consulting or management) to get appropriate pay for the position.

This doesn't make tech ageist. My local grocery store also doesn't pay the senior cashiers any more than the high school ones.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by AnimalMuppet on Wednesday August 03, 2016 @06:55PM (#12222152)
I disagree, at least for some sub-fields. In embedded systems, 20 years of experience is more valuable than 5 years (and has pay to reflect that).

In web programming? Maybe not so much...

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by morgante on Wednesday August 03, 2016 @06:57PM (#12222158)
It sounds like we actually agree. Most of the accusations of ageism seem to be for fields where 20 years of experience is not so valuable.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by twblalock on Wednesday August 03, 2016 @09:03PM (#12222679)
That makes sense.

If all you need is someone with a few years' experience, the younger candidates are probably going to be willing to work longer hours, for less money, than the older candidates.

In other words, why pay a 20+ year veteran a lot of money to do Rails programming when a recent college grad knows enough to do a decent job, and can be paid an entry-level salary? Not every engineer on a team needs to be senior.

I suspect this is also good career advice: if you don't want to compete with entry-level programmers for jobs, specialize in an area where more experience makes you a more desirable job candidate.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by AnimalMuppet on Wednesday August 03, 2016 @08:13PM (#12222486)
> Most of the accusations of ageism seem to be for fields where 20 years of experience is not so valuable.

I don't have enough data/experience to confirm that, but it seems plausible.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by sanderjd on Wednesday August 03, 2016 @08:50PM (#12222641)
Can you articulate why experience is valuable in embedded systems and why it is not valuable in web applications?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by linkregister on Thursday August 04, 2016 @05:17AM (#12224360)
Mind that the parent poster didn't claim that experience was not valuable in web applications; just that there were diminished returns.

Embedded systems programming is far more architecture and device specific than web applications are, thankfully. Embedded systems programming requires a much large body of knowledge: chipsets and their features, device-specific options, the behavior of the RTOS (if there is one), esoteric configurations in the cross-compiler or build tool, ability to interactively debug (read the instruction set, use the interface (JTAG, etc), cope with interrupts), ability to thrive with extreme resource limits, and write comprehensive tests with a nearly-exhaustive test plan; since a final release can't be rolled back once customers have purchased it.

This isn't because of some inherent superiority or prestige of embedded systems programming (salaries are lower across the board compared to backend applications programmers), it's just plain more complicated.

A 20-year senior backend programmer should really have progressed to an architect or principal engineer role at that point in her career. An embedded systems developer with 20 years of experience is more typical because of its inherent complexity.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by elliotec on Thursday August 04, 2016 @01:44AM (#12223634)
Ageism.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by elliotec on Wednesday August 03, 2016 @08:34PM (#12222572)
You don't think having been programming for the web since the web came into existence is not valuable experience to being a web programmer?

That is absurd. That kind of bullshit talk is why ageism exists and what perpetuates it.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by twblalock on Wednesday August 03, 2016 @08:58PM (#12222663)
He didn't say it wasn't valuable. He said it might not be more valuable than 5 years' experience, presumably because technologies change so quickly in web programming. I don't agree with that, but he certainly wasn't being ageist.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jpindar on Thursday August 04, 2016 @09:23PM (#12229540)
Assuming that anyone over a certain age is going to require short hours, high pay, etc. IS ageist.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by elliotec on Wednesday August 03, 2016 @08:21PM (#12222517)
One or two gen-xers or millennials saying such things per ageism comment on HN might count as discounting ageism as nonexistent but only by those people specifically.

People know it's a problem. Whether or not they actually do anything about it is a different story. Like any "ism."

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by optimuspaul on Wednesday August 03, 2016 @01:17PM (#12219637)
lets start by removing the labels of gen x and millennial. It's degrading. I personally try to not take age (or gender, race, clothing choice(please can we stop with wearing suits and ties to interviews, it's dumb), or anything other than skills and culture fit) into account when interviewing people. But I can say that looking out over the people at the company I am at, it's mostly young people. Is that ageism? probably some but also, guess who costs more? old people. That's why older folks have a harder time getting hired. I also suspect that due to the glut of young kids coming into the market they will feel similar pains at trying to get hired just due to sheer numbers, and of course jerks who don't want those kids on their lawn.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by cellularmitosis on Wednesday August 03, 2016 @01:56PM (#12220017)
It is also easy to forget that more and more people are becoming programmers each year. The necessary result of this is that when you look at the average tech company, there will be fewer older programmers.

"Uncle" Bob Martin once gave a talk where he asked for a show of hands of "How many of you have been programming for 5 years? 10 years? 15? 20?". The results in his audience roughly correlated to his thesis, that the number of programmers has roughly doubled every 5 years since programming was a thing.

Are there fewer older programmers at a given company because of ageism? I'm sure that's part of it. But don't forget that there are far, far fewer programmers with 20 years of experience than with 5 years of experience.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by BatFastard on Wednesday August 03, 2016 @02:26PM (#12220240)
And if you got the choice of hiring someone with 5 year experience or 20, which would you choose?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by TheOtherHobbes on Wednesday August 03, 2016 @04:40PM (#12221327)
It would depend on the kind of experience and the quality of insight. Time served doesn't correlate to quality.

Programming is actually a very permissive industry. There are corporate environments in which you can be barely competent and still keep your job - if not gain promotions.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by AnimalMuppet on Wednesday August 03, 2016 @03:50PM (#12220943)
Depends on whether they cost the same. If the experience costs more, does it bring enough value to the position I'm hiring for to be worth the cost?

That's the key to getting a job with 20 years of experience. You need to be able to convince the hiring manager that you're worth the extra money in that job. (And then the hiring manager needs people above him that will let him spend the extra money.)

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by sokoloff on Wednesday August 03, 2016 @10:18PM (#12222941)
There's nothing stopping you from not wearing a suit to an interview. I never have, and I don't believe it's hurt me one iota.

The only candidates I see regularly wearing suits to interview are executives and college junior/seniors. I'm hiring you to code, not model. I couldn't care less what you're wearing as long as it's clean and reasonably respectable.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jpindar on Thursday August 04, 2016 @09:27PM (#12229552)
>who costs more? old people

That's an ageist statement.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @12:56PM (#12219446)
> This is not discounted as non-existent by anyone

Based on conversations in some of our tech groups, yes, it is seen as non-existent by some.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by pmiller2 on Wednesday August 03, 2016 @01:05PM (#12219528)
If people are ageist against millenials, who's hiring all the 25 year olds I work with?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by slavik81 on Wednesday August 03, 2016 @02:06PM (#12220099)
If you're suggesting based on your workplace that young people are more likely to find jobs overall, you are incorrect.

"On average between 1989 and 2007, the unemployment rate of workers under age 25 was 2.2 times as high as the overall unemployment rate. [...] In March 2015, the overall unemployment rate was 5.5 percent, and the unemployment rate of workers under age 25, at 12.3 percent, was 2.2 times as high."

http://www.epi.org/publication/the-class-of-2015/

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by pmiller2 on Wednesday August 03, 2016 @02:20PM (#12220202)
My comment and the article are specific to tech; your response is not.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dpark on Wednesday August 03, 2016 @01:55PM (#12220004)
He didn't say anyone is ageist against millenials. He just said millenials are not the ones who are ageist. I think this is probably still not true, but it's the claim.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by itchyouch on Wednesday August 03, 2016 @02:11PM (#12220137)
At my place, we have plenty of older folks(40-50s), but a lot of the older guys suffer from either NIH syndrome or do-not-want-to-innovate syndrome or barely surviving-syndrome. Some of them are in management and also just don't get it. This definitely biases myself against older folks if I ever have to interview, but usually interviewees can barely pass a phone screen anyway regardless of age.

It's frightening since I'd imagine that these things I implement now may be irrelevant 10-20 years from now and would imagine myself butting heads with the next gen of kids as an older guy.

I guess we will have to see if ageism becomes irrelevant as time goes on and the current generation of 20s kids that become the hiring managers 20 years from now lose their bias as they age. I'm hopeful as tech has had a lot of growth and the current 20-30s technologists value the older folks.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by YZF on Wednesday August 03, 2016 @04:12PM (#12221111)
Well, at my place I'm the "older" guy wanting to innovate :) I don't think either NIH or not wanting to innovate is an age thing. It's a mindset. Plenty of young people have that as well. Plenty of older innovators.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by itchyouch on Wednesday August 03, 2016 @08:00PM (#12222426)
There are a couple of older innovators in management positions as well. The guys who really want to innovate and make a difference have gone to other places unfortunately. I guess we are merely left with older guys who are comfortable.

Being in "regulated" finance makes for a lot of guys who have golden handcuffs. Great salary and benefits and no strong desire to ruffle the bureaucratic obligations placed on them. A very common theme is, "Hey can you work on this X feature? Would be really useful." "That sounds like a great idea! But sorry, I can't unless there is a billing code dictated by the business for that idea"

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by kamaal on Wednesday August 03, 2016 @01:27PM (#12219751)
>>In reality, tons of companies are INTERVIEWING but nobody seems to be HIRING.

Most companies tend to judge a programmer's ability by checking if they can solve the 4 latest questions on their favorite programming algo puzzle site within an hour.

No amount of work prepares you for this.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by akadien on Thursday August 04, 2016 @09:47AM (#12225425)
I had a first interview with a company where an engineer walked into the room with an eight page C++ exam. No interview. No meet-and-greet-tell-me-about-yourself. Just write, using pen and paper, several complete C++ programs for really hard academic-style problems (combinatorial optimization, dynamic programming, machine learning). Oh, and you had 1 hour. It wasn't an interview as much as a graduate level final exam.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by ionforce on Wednesday August 03, 2016 @01:42PM (#12219896)
What if you practiced these problems?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by muzz on Wednesday August 03, 2016 @01:52PM (#12219981)
GP may be able to do that and get the job, but then he or she would be working with others who've done that, and they may be good rapid puzzle solvers, but not good engineers. That's the problem with that interview approach, it tests only one particular skill (and even that with a high degree of variance).
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by itchyouch on Wednesday August 03, 2016 @02:24PM (#12220225)
I wonder. I've done a bunch of interviews and will tailor basic questions based on the resume. If they claim to understand networking, I'll ask them a basic "what is ping?" then progress to something like "what does arp do?" Then maybe a tricky, "whats the difference between a timeout and route unavailable error when pinging a host" And hit other topics. I wonder if this is too quizzy?

If it's about Bash, then basic questions about variables, exit statuses and such are asked. Surprisingly, so many people's resume accomplishments don't line up with what I'd imagine would be the type of knowledge they should/would carry based on the accomplishment.

If the candidate is out of college, then I am a bit more forgiving since I wouldn't expect them to know the intricacies of certain software stacks, but for someone working with something for 2-3 years can't really explain what they put on their resume, it's a big red flag and plays a very large part in disqualifying the person based on their technical merit alone even without getting to the "does this person play well with others" aspect of interviewing.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by vonmoltke on Wednesday August 03, 2016 @03:55PM (#12220987)
Your approach is pretty much standard practice in the engineering world. People in this industry like to claim that answers to those kind of questions can be faked, but you can't fake depth. At some point, if you know what you are doing[1], you will make them look like an idiot if they have been lying.

[1] If you don't know what you are doing, you have no business giving an interview. That's another big problem this industry has.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by coredog64 on Wednesday August 03, 2016 @03:21PM (#12220695)
I'm glad to know I'm not the only one that does this. I'd say my results echo yours. I had one candidate with a resume that bragged about years of shell scripting experience. When I asked the trivial question of "What is your favorite shell?" he gave a panicked-deer-in-the-headlights look and muttered something about Ubuntu.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by itchyouch on Wednesday August 03, 2016 @08:09PM (#12222468)
Phew. Glad to know that I'm not the only one dealing with bullshitters on resumes.

I noticed that the recruiting firm that got me my current job is that the candidates that they send aren't that great. I only met this firm because a friend passed the gig on to me. They just send anyone and hope that someone sticks. But once they find someone that sticks and is doing well, they keep on coming back once the headhunting contract limits are off.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dpark on Wednesday August 03, 2016 @01:59PM (#12220034)
This isn't relevant to the claim that "No amount of work prepares you for this". You can indeed prepare for "puzzle" interviews. Whether this is good interviewing culture is an entirely different question.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by kamaal on Wednesday August 03, 2016 @02:55PM (#12220488)
>>You can indeed prepare for "puzzle" interviews.

The term 'Preparation' is a misnomer here.

That process literally involves living your life on sites like TopCoder, HackerRank etc. You will likely be spending any time you can spare on such sites, to 'prepare'.

You can be the most productive person in your current job. That doesn't prepare you for these interviews.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dpark on Wednesday August 03, 2016 @05:37PM (#12221739)
> That process literally involves living your life on sites like TopCoder, HackerRank etc. You will likely be spending any time you can spare on such sites, to 'prepare'.

In the same way that keeping up with current events means living your life on sites like CNN, Reuters, NPR? The same way learning a language means staring at DuoLingo all day?

Most people don't require 100% time allocation to learn something.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by pyre on Wednesday August 03, 2016 @06:26PM (#12222018)
At the same time, you can be amazing at your job without being amazing at toy-problem-brain-teaser questions.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by majormajor on Wednesday August 03, 2016 @08:29PM (#12222551)
I think there's a big, meaningful difference between "no amount of work prepares you for this" and "no amount of [anything] prepares you for this."

With very few exceptions, a job where you're doing useful work, is not going to prepare you for those sorts of data structures/algorithms memorization questions. Libraries exist, you should (generally) be using them, not rewriting them every day. And yet I've been interviewed several times for roles where my actual work has turned out nothing like those interview questions. It's merely a way of trying to check "do they have a good enough memory and grasp of the basic concepts to work things out" as a (lazy, IMO) substitute for trying to see if they have relevant, immediately-useful skills that will complement your team. The less training and onboarding you want to have to burden yourself with, the less you should be asking those questions.

Fortunately, on my current team, I had the flexibility to change up our interviewing approach. And then other teams made comments along the lines of "how did you hire such good senior people who grasped our problem space so quickly?!" :)

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dpark on Thursday August 04, 2016 @09:53AM (#12225464)
> I think there's a big, meaningful difference between "no amount of work prepares you for this" and "no amount of [anything] prepares you for this."

Something you spend time on to do better in interviews is work as far as I'm concerned. Brushing up on algorithms is work in this context. So is doing programming puzzles if you expect to see those.

> It's merely a way of trying to check "do they have a good enough memory and grasp of the basic concepts to work things out"

It's generally not about memory. That's a factor but not the intent. Programming puzzles are about finding out if the candidate has a sufficient grasp of technical basics (i.e. if you don't know what a hash table is, or if you don't know Big-O notation, that's a big concern), and yes, whether they can work through a problem. If you can't work through a problem, that's also a big concern. It could mean you just don't interview well, and that's a problem I don't know how to solve. It could also mean that you just aren't able to think through complex issues.

Toy problems are not completely representative of real work, but I find it odd when people claim they don't do anything like this in their work at all. I use Big-O to discuss work and give code reviews with some regularity. I work on problems that require juggling some moderately complex state to solve correctly, that require good choice of algorithm and data structure to solve efficiently. That's definitely not most of my work, but it's a part.

I try really hard to ask questions that someone with good grasp of fundamentals can solve, though. I stay away from questions that are dependent on a clever trick (find a loop in a linked list with two pointers) or esoteric/trendy knowledge (use circular hashing and a bloom filter!).

On the other hand, "brain teaser" puzzles seem mostly to be pointless, but I've not personally been asked one of those in a real interview and I don't know anyone who uses those.

> as a (lazy, IMO) substitute for trying to see if they have relevant, immediately-useful skills that will complement your team.

I don't generally care if people I'm hiring have immediately-useful skills beyond the fundamentals. I don't care if they're well-versed in our stack or languages or whatever. It's a bonus if they are, but I care far more that we hire smart people who can learn.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by majormajor on Thursday August 04, 2016 @01:58PM (#12227295)
A lot of it is memory. If you have recent memory of writing, say, a bunch of tree traversal implementations, you're going to solve those problems a lot faster than someone without that recent practice. And if you're talking a 45-min or 1-hr one-or-two-question phone screen, companies are putting a lot of value on that quickness.

I haven't seen many interviewers (as candidate or as a fellow interviewer) who truly value "talking knowledgeably about Big O notation" or "knowing what a hash table is" anything near as much as "wrote a whiteboard implementation of topological sort quickly enough." It's the latter part that I object to.

The areas where I've found looking for immediately-useful skills helpful are (a) to ship specific projects in new areas where I'm not an expert fast and (b) to verify that someone has the patience/diligence to go deep in at least one area. Friend of mine is at a place that seems to need this desperately: about 15-25 "smart people who can learn" mostly straight out of school, but a culture that's mostly the-blind-leading-the-blind and rediscovering known solutions (or worse, rediscovering practices with known issues). He's currently trying to sell them on the value of having automated regression testing, but that's not the type of skill learning they were selected for.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dpark on Thursday August 04, 2016 @04:56PM (#12228418)
> A lot of it is memory. If you have recent memory of writing, say, a bunch of tree traversal implementations, you're going to solve those problems a lot faster than someone without that recent practice.

It is a factor but not the purpose. Yes, if you don't remember how to do something, you'll have a hard time doing it unless you can derive it from first principles. There is literally nothing you could ask in an interview that would not involve memory, though. "How would you reverse a linked list in C"? Definitely some memory there. "How would you implement a hash table?" Also requires memory. "What did you work on at your old job?" Again, memory.

> And if you're talking a 45-min or 1-hr one-or-two-question phone screen, companies are putting a lot of value on that quickness.

Eh, maybe. I think studying up on interview problems is a good idea in general, because it gets you practice thinking through problems and recognizing similar situations. However, I don't consider it a positive to see someone burn through the "right" solution with no apparent thought. If you've seen the problem and don't say so, I have to lean toward no-hire, because pure rote memory is not interesting. If you have clearly done the problem recently but deny it when asked, I have to question your ethics, too. You might just be a genius, but them I expect you to seem like a genius when we discuss technical matters and not just when solving interview questions.

> I haven't seen many interviewers (as candidate or as a fellow interviewer) who truly value "talking knowledgeably about Big O notation" or "knowing what a hash table is" anything near as much as "wrote a whiteboard implementation of topological sort quickly enough." It's the latter part that I object to.

I don't ask questions like that and most of the my colleagues don't either. I do ask technically difficult questions and expect code, but I don't expect perfect code. I expect candidates to work through a reasonable solution out loud and write at least part of it in code that could work with a little polish. If you write terrible code and leave off-by-one errors everywhere and can't recognize them when prompted, it's probably a no hire.

> Friend of mine is at a place that seems to need this desperately: about 15-25 "smart people who can learn" mostly straight out of school, but a culture that's mostly the-blind-leading-the-blind and rediscovering known solutions

Your friend works somewhere with poor staffing practices, then. If you don't have some senior people promoting proper dev culture and practices, it's going to be a mess of poor engineering and reinventing the wheel.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by majormajor on Thursday August 04, 2016 @06:37PM (#12228944)
It seems like we're mostly on the same page, just approaching it from different directions. Maybe I've just gotten unlucky in my interview experiences at startups/establish Bay Area "coding question"-focused shops. :\
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dpark on Thursday August 04, 2016 @07:05PM (#12229078)
Seems like we're not that far apart, at least.

I won't lie. Interviewing is tough. I've been involved with some bad interviews from both sides. I wish there was a better way, but I'm not convinced that any of the alternatives typically proposed are actually better.

I gave some interviews when I was at Yahoo that I recognize in retrospect were pretty terrible. Questions with clever/trick answers, trendy topics, etc. The only thing I never did was the pure brain teasers (a fox, chicken, and farmer need to cross a river...). I try to do better now. :\

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by muzz on Wednesday August 03, 2016 @03:35PM (#12220824)
True. I did change the topic and offer my opinion.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by kamaal on Wednesday August 03, 2016 @02:59PM (#12220520)
You can't exactly practice these problems. There is generally some trick involved somewhere which the interviewer expects you to demonstrate.

Some tricky way of traversing a tree, or expecting you to know the complexity of every sorting algorithm that exists out there. There is so much of material out there, you'd pretty much be on top of it all the time to 'not forget' stuff with the passage of time.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mdpopescu on Wednesday August 03, 2016 @12:47PM (#12219354)
The market in Ireland seems amazing. I'm a bit older than you (25+ years of experience) and last year I went to Dublin for an interview, didn't like the job very much, went to about six more interviews, got two very good offers, chose one. This was all in a timespan of about a week.

Then again, it might be because I'm mainly a contractor; I didn't try to get employed full-time.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @12:53PM (#12219405)
> it might be because I'm mainly a contractor; I didn't try to get employed full-time.

I bet that's most of it. Can't speak for Ireland, but almost every country has a lot of extra burdens and regulations that come with "employees" vs "contractors".

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by tomphoolery on Wednesday August 03, 2016 @12:58PM (#12219470)
This is why Comcast hires all developers as independent contractors.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mikereedell on Wednesday August 03, 2016 @02:05PM (#12220080)
My team, and most of the teams in my division, are full-time Comcast employees. Our PM and QA orgs, however, is full of contractors.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by YeGoblynQueenne on Wednesday August 03, 2016 @03:48PM (#12220929)
So, um, where does one find contracting work in the UK? As a programmer, obviously.

It's the first time in five years I'm withouth permanent work. I think I might give it a try to do a bit of freelancing or contracting for a change.

Where does one even get started though?

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mdpopescu on Thursday August 04, 2016 @01:46AM (#12223639)
I usually upload my CV to monster.com, dice.com, indeed.com and I start getting emails from recruiters. You can also search for recruiting agencies and contact them directly. Don't ignore Twitter and LinkedIn, some of the people seeing your messages might know someone who knows someone.

Don't stop at the first "no", send a few dozen applications and see what answers you get.

This is pretty much the easiest thing you can do; I'm happy with the results because my income expectations are lower (being from Eastern Europe) than those of a native British. Meet-ups, investigating companies' needs and everything else that @patio11 describes are needed for much better results.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by YeGoblynQueenne on Thursday August 04, 2016 @08:57AM (#12225162)
Thanks- sounds like what I when I'm looking for a permanent role, so I got no excuses not to know the drill. :)
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by passiveincomelg on Thursday August 04, 2016 @06:32AM (#12224611)
Two of those pimps you can upload your CV to are: http://www.hays.co.uk/ http://www.computerfutures.com/en
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by YeGoblynQueenne on Thursday August 04, 2016 @09:15AM (#12225239)
Thank you, I'll have a look.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by sammydavis on Wednesday August 03, 2016 @05:40PM (#12221764)
I also have 2 decades of exp and I'm over 50. I had no problem recently switching jobs but I also had good experience, and I'm a dev and have recent dev experience. I wonder if part of your problem is not being a dev but being pm of one type or another. PMs can have a rep as not being so technical. It might be painful but try to contact the people that didn't hire you and see what they can say.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mark-r on Wednesday August 03, 2016 @06:32PM (#12222043)
You would be extremely lucky to have someone talk to you about why they didn't hire. They have no incentive to talk to you and plenty of disincentives, for example just not having the time. It might be HR policy to avoid contact for fear of leaking info that could lead to a lawsuit.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by afarrell on Wednesday August 03, 2016 @12:35PM (#12219247)
Why would you bother spending engineer time on interviews if you aren't hiring?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by hibikir on Wednesday August 03, 2016 @12:48PM (#12219372)
There are companies that think they are hiring, but aren't, because their interview process is a trainwreck that passes on great candidates, aims only at former employees at big tech companies, and don't offer those people competitive salaries, so their accept rates are under 30%.

There's plenty of startups up there working on trying to improve the state of hiring, but little has changed so far.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by niemeyer on Wednesday August 03, 2016 @03:13PM (#12220641)
Interview processes aren't about ensuring 100% of the good candidates get hired, but rather about trying to ensure that the candidate finally selected is good.

Being several times on the hiring end of that conversation, there's a class of great people that are very hard to identify over an interview. It feels quite bad to suggest a no-go in those cases, but living through such choices, sometimes for years, increases the fear of mishaps.

These days I mainly look at track record. Involvement in projects, conversations, issues filed, quick hacks, etc. Often language or tech doesn't even matter, as long as there's flexibility and an ability to talk over problems.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by gohrt on Wednesday August 03, 2016 @02:54PM (#12220478)
If these companies aren't really hiring because they aren't offering competitive salaries, that means that someone else is hiring and offering competitive salaries.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @12:58PM (#12219467)
> There's plenty of startups up there working on trying to improve the state of hiring, but little has changed so far.

Probably not much will change, because it's an internal culture thing, not an external "wish we had this tool" sort of thing. Yes, some tools/services can reduce friction to make it easier, but if someone still has a policy which is counterproductive, and will not remove the policy, you won't get the necessary change.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by rhizome on Wednesday August 03, 2016 @01:44PM (#12219916)
>Probably not much will change, because it's an internal culture thing

Is it even internal? This just occurred to me so it's not even well-formed in my head, but I would posit that the policy is (or appears to be) shared even if it's subconscious. Systematic bias is a thing and nobody thinks they're the bad guy, but emergent behavior can be mistakenly attributed to "internal culture" while nothing gets better. Blinders.

There are a lot of commonalities in the anecdotes in threads on this topic, and if it was code being analyzed by a programmer they might say these shared behaviors could be pull-up refactored (or extract superclass, or...) from a scattershot of presumed-local traits ("policy") into characteristics of the entire system.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by muzz on Wednesday August 03, 2016 @01:45PM (#12219925)
My view is that companies are hiring, but are looking for nearly-perfect candidates. I wonder what part recent changes to the field have to do with this, i.e. higher salaries for engineers the past few years, open office floor plan facilitating/requiring more interaction and communication, etc.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mark-r on Wednesday August 03, 2016 @06:37PM (#12222060)
I've seen plenty of situations where there was a real intent to hire somebody, but the final approval just never came through. When money is tight you'll find this happening, especially if the situation is worsening over time.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by toomuchtodo on Wednesday August 03, 2016 @12:38PM (#12219273)
[deleted]
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by hx87 on Wednesday August 03, 2016 @12:43PM (#12219320)
Time that could be spent doing more productive things, and is thus not a sunk cost.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by linkregister on Thursday August 04, 2016 @05:02AM (#12224319)
Yes, much of this recruiter email is from 3rd party recruiters that hope to get a commission from the hiring company. They reach out with the broadest search terms.

A nitpick: it's not the companies that are interviewing without intent to hire, it's the 3rd-party recruiters that are blasting you. Developer time is expensive and typical companies don't waste that.

I think "get another job on Monday" is a euphemism; 1-3 months would be pretty representative of the current market in the SF/SV and Washington, DC areas.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by emodendroket on Wednesday August 03, 2016 @02:24PM (#12220220)
That may be the case, but why bothering interviewing if you have no intent to hire?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by henrik_w on Wednesday August 03, 2016 @01:11PM (#12219576)
Another job as programmer, or another job as a project-/product-manager?