News for hackers. Stuff that matters.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @11:53AM (#12218823)
> I’ve been telling my students, “Take a chance, you can get another job on Monday.”

For students, maybe, especially if they're entry level jobs. However, for anyone even mid-level, I don't think this has been good advice for several years. Perhaps in SF it's been fine, but even for many mid-level (and certainly sr folks) I know, finding another job "on monday" has not been the case. (getting an interview, especially via a recruiter, has still been relatively quick, from what I hear).

Employers have been far more picky than I think many people expect. Compounding this is that they sometimes have suboptimal folks in particular roles, and those people tend to exacerbate the problem when interviewing/finding new folks.

In any event, glad to see somewhat balanced view, vs the extremes we normally see.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by cpprototypes on Wednesday August 03, 2016 @01:08PM (#12219549)
The message is loud and clear for senior engineers (10+ years experience): startups don't want you. They may say they do, but they really don't. And the message from SV big tech is also clear: we don't want you unless you're in the inner club (Google, FB, Amazon, etc.)

The solution is to avoid these companies. There's a huge world outside SV. These may be known as "boring" (banks, insurance, etc.) but they will not have the stupid ageist algorithm games known as "technical programming interviews". And they respect experience. And they won't have an ageist culture, it will be ok to go home early and be with family.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by Periodic on Wednesday August 03, 2016 @01:31PM (#12219794)
If the problem is that you can't get a job if you're not in the club, why not join the club?

I used to work at Google and I did a lot of interviews. I loved when we finally got an experienced engineer in to interview. I could stop asking the toy algorithms questions and actually talk about design.

But maybe they only want to hire fresh college grads? The company is sorely lacking in experience. I wouldn't be surprised if the reason they can't find experienced engineers to interview is that everyone with experience who is qualified to work at Google either works there already or doesn't want to.

Maybe you're in that camp of not wanting to work at Google. That's fine. I enjoyed it for a while but it wasn't for me. Just having it on my resume has opened a lot of doors.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by gedy on Wednesday August 03, 2016 @01:55PM (#12220005)
Interviewing at Google a few years ago (with some experience) was not positive - the interviewer actively avoided talking anything about design or systems, and insisted on asking me brain teasers about weighing boxes of pennies, etc. Was a stupid waste of time for me and turned me off from Google totally.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by gohrt on Wednesday August 03, 2016 @02:53PM (#12220474)
How many years ago? Google famously publicly renounced those ~5 years ago.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by gedy on Wednesday August 03, 2016 @03:37PM (#12220835)
True, was about 5-6 years ago.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by ruste on Wednesday August 03, 2016 @02:45PM (#12220393)
I think I'd actually prefer that...
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by gedy on Wednesday August 03, 2016 @03:42PM (#12220880)
It wasn't just the type of questions, was the whole experience - I did answer, then then interviewer insisted I could do it in one fewer step, and would not proceed or assist until I came up with a better answer. Then time was up, and he answered no questions of mine. Emailing the recruiter to ask if this was expected or if there was another role and received no replies back. Sorry, but to hell with working for Google after that...

Bear in mind at the time I had 8 years experience in non-trivial roles, including some mgmt and architecture, and they were the ones who reached out to me.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @04:37PM (#12221306)
> and they were the ones who reached out to me.

I had a google recruiter call, we spoke, then set up a longer interview. I asked about pay, and was told they don't talk about it until after an interview, which meant travel and time away from current projects. It's not that I couldn't do it at all, but it meant some schedule shuffling and I wanted a ballpark - just a ballpark or ...minimum floor. She wouldn't give me any info.

I then asked another question which she didn't know the answer to ("no one's ever asked that before!") and told me she'd have an answer in a couple days. That was ... Aug 2013? I'm still waiting.

I told the story before and someone said "well, that's no way to get a job!" as I described my questioning the recruiter. "I didn't apply for a job - they called me - they can answer a couple of my questions if they want me to take time out to come visit them".

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by rubberstamp on Thursday August 04, 2016 @03:35AM (#12224021)
can you please share what that question was? just curious. I've read many other articles about candidates having had similar experiences. Its one of the reasons i dont like Google as a company
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Thursday August 04, 2016 @06:39AM (#12224641)
role was developer evangelist. she mentioned bonuses were based on performance review, and I asked what the metrics were. how did they measure the 'success' of a developer evangelist? number of presentations? blog posts? conferences? miles traveled? She didn't know, and apparently no one has ever asked that question (at least at that stage of the process) before.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by rubberstamp on Thursday August 04, 2016 @07:58AM (#12224905)
that is an entirely natural thing to ask. thanks for taking time to reply. i like the way you replied with right amount of info and good clarity
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Thursday August 04, 2016 @09:52AM (#12225461)
Thank you :)
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by bpchaps on Wednesday August 03, 2016 @07:04PM (#12222179)
Interviewing at google was the absolute worst experience I've ever had over two weeks:

First interview was a cold call from a bored sounding engineer-turned-recruiter. The guy asked me some questions and some I didn't know at the time, but since my experience was pretty solid, they scheduled an interview anyway.

They forgot the first interview. No call, no email, no answer from emails, etc. It's not a first, so I took it as, "shit happens".

They forgot the second interview.

The third interview finally happened, but the engineer on the other end of the phone was ~extremely~ uninterested from the beginning of the call. How in the hell am I supposed to be excited for the interview or even working with someone like that?

To make matters worse, all three interviews required me to leave work early. Because that's obviously not suspicious. Never got a call or email or apology after that ordeal.

"Welcome to Google, we hate our lives, want to hate yours, too?".

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by ruste on Friday August 05, 2016 @01:58PM (#12234449)
That does sound pretty miserable. I'd be upset too.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by quantumhobbit on Wednesday August 03, 2016 @02:05PM (#12220089)
If the problem is that you can't get a job if you're not in the club, why not join the club?

Problem is the club doesn't seem to want any new members above a certain age.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by SomeCallMeTim on Wednesday August 03, 2016 @07:31PM (#12222317)
"A certain age"? I "joined" the club by getting a gig at Amazon at 46. Before that I'd never worked at any of the big tech companies. I also get interest from startups all the time, but from what I can tell they don't want employees above a certain salary, not a certain age.

I don't think it's age but attitude and skills that distinguish people who can get "in the club." If the attitude is "SHOW ME THE MONEY" when Google is well known for paying way above market rates, or if the attitude is "WHY SHOULD I KNOW THESE CS PROBLEMS!?", when it's well known that Google cares about those problems...well, then no, you can't join the club.

At this point I've interviewed at Google but turned them down when they could only offer me what sounded like a glorified accounting programming position (in the Boulder office, which doesn't have as many teams as in Mountain View). I might have fun working at Google on the right team, but I have other options (including Amazon) that also pay well and are very attractive for other reasons, so why not?

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @02:14PM (#12220159)
> Problem is the club doesn't seem to want any new members above a certain age.

Which is precisely the problem that was being pointed out earlier - how meta! :)

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by vonmoltke on Wednesday August 03, 2016 @03:38PM (#12220847)
Despite my shitty experience last time, I would be willing to give Google another chance (as long as it isn't in California). They've decided to ignore me.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by kmonsen on Wednesday August 03, 2016 @05:29PM (#12221668)
pm or email me if you want some help [email protected]

Also I have worked for Google in NYC and London so feel free to ask any questions.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by linkregister on Thursday August 04, 2016 @04:44AM (#12224271)
Since when does Google fail to ask toy algorithms question of senior engineers?

I'm not being snarky; everything I've ever read, heard, and experienced with Google interviews is that these trivia algorithms questions compose the majority of the on-site interviews. [1] [2]

You appear to be different, but please don't claim your interviewing style as representative of even 1/4 of Google interviewers.

> [maybe] everyone with experience who is qualified to work at Google either works there already or doesn't want to.

If memorizing algorithms is a necessary condition of a senior engineer being qualified to work at Google, that is fine. But it is disingenuous to claim otherwise, since clearly many have found it is algorithm memorization that has been the gatekeeper from getting an offer at Google, not non-abstract large systems design, linux systems internals knowledge, concurrent and asynchronous programming, etc.

[1] http://www.nakov.com/blog/2007/12/27/overqualified-to-work-i... "Trust me, a 15 years old schoolboy who is a good programming contestant (e.g. some of the Bulgarian National champions) can pass these questions without having any experience in commercial software engineering. I expected more software engineering questions about software design and architecture, large-scale databases and information systems, Internet applications, information security, parallel programming, threads, synchronization, development process, software quality, testing, life-cycle, software project management, agile development, etc. but the interviewers didn’t even mention any of these topics. I applied for senior position and it was normal to expect serious software engineering and technical questions, but this didn’t happen."

[2] https://www.glassdoor.com/Interview/Google-Senior-Software-E... (the typical response is some variation of "they asked me a question that was similar to a problem in Cracking the Coding Interview while not offering a single question about my previous accomplishments or potential culture fit."

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by kamaal on Wednesday August 03, 2016 @01:23PM (#12219708)
Most start ups really want people in early 20's, Unmarried without responsibilities, who have a very idealistic view of the world and are ready to fail, without any financial profit in return.

>>stupid ageist algorithm games known as "technical programming interviews"

Unless you are in "exam mode" all the time. Spending away all your life in the pursuit of the interview preparation. This kind of interview preparedness isn't possible anyway.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jasoncchild on Wednesday August 03, 2016 @01:48PM (#12219956)
^yes. when an early-stage startup (seed or just hit series a) emphasizes that they are a 'family' this is not quite accurate. yes, caring and support abounds, but its not so much a family as a group of friends...and like every group of friends when you can't hang at the bar until closing a few nights a week or spend a weekend 'adventure camping' the group just stops inviting you. quickly you lose sync, don't get the in-jokes and most importantly you lose value in the eyes of the group. 'oh, she/he used to be cool, but they just don't hang anymore'.

when it comes to work this has a very destructive effect. team-building exercises that require people to choose between spending time with their families and participating are, in my opinion, at the least cruel and at the most nefariously aimed at driving a culture wedge between you and the company.

your children only grow up once. no second chances.

your elderly parents deterioration and eventual death only happens once. no second chances.

most of us will work the majority of our lives, occupying several roles at more than one company. in my mind this amounts to numerous 'chances' to do things better/differently/more carefully/more thoughtfully/ etc etc etc.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mholmes680 on Wednesday August 03, 2016 @04:43PM (#12221349)
To his credit, I had a (rather eccentric) founder in NYC ask me if I planned on having kids anytime soon as the first question of his interview - after all the tech questions from people under him.

When I said yeah, and I was planning on commuting from NJ, he said "well I don't want to break up a family, so see you later" <end of interview>. I thought it was rude at the time, but here I am 3 years later and damn if he wasn't right. Dodged a bullet that only he saw was coming right at me.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mandevil on Wednesday August 03, 2016 @07:50PM (#12222381)
I'm pretty sure that in the US that question is illegal to ask an interviewee. It might have been beneficial in your case, but is still totally illegal because it is one of the ways the sexual discrimination in hiring propagates.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dragonwriter on Wednesday August 03, 2016 @08:03PM (#12222438)
> I'm pretty sure that in the US that question is illegal to ask an interviewee.

It is not. (Like most questions that people think are illegal to ask in interviews, its merely ill-advised to ask because it asks specifically about something on which it is illegal to discriminate in hiring, and asking about it in an interview is -- on its own, weak, but still -- potential evidence of its use in a hiring decision.)

(Cargo cult HR helps perpetuate the myth that these things are illegal to ask.)

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mandevil on Wednesday August 03, 2016 @09:12PM (#12222711)
Okay, it might not necessarily be illegal in the general case, but in the specific case described by the OP, asking that question, getting an answer, and then saying "See you later <eom>" makes it clear that that was discrimination in the hiring process based on family responsibilities, no?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by dmoy on Thursday August 04, 2016 @03:33AM (#12224016)
It's not illegal but it opens many very wide doors for lawsuits.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by voltagex_ on Wednesday August 03, 2016 @09:12PM (#12222709)
That might be the first example I've heard of positive cargo-culting.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by fibonachos on Wednesday August 03, 2016 @02:55PM (#12220484)
As a long time independent consultant looking for a regular 9 to 5 job, my recent interview experiences would be consistent with this statement. After a series of phone interviews and a 4 hour on-site, all of which yielded positive feedback, I was told the position went to someone "more passionate" about the company mission.

After reflecting a bit on what I may have done or said wrong, it hit me. This place had the typical startup perks: catered lunches, stocked kitchen (with plenty of energy drinks), and a younger demographic (I'm 40). My conclusion is that "More Passionate" is actually code for "willing to work 14 hour days."

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jpindar on Wednesday August 03, 2016 @10:31PM (#12222997)
And what if I'm past my 20's, but still unmarried with no responsibilities and I love pulling all nighters and am willing to work long hours for relatively low pay? There's no real way to tell potential employers that, is there?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by vvanders on Wednesday August 03, 2016 @01:32PM (#12219804)
That seems to be common in other high-churn areas of the industry as well, ex: GameDev.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by susan_hall on Wednesday August 03, 2016 @01:39PM (#12219876)
I have faced something similar. Though I have 14 years experience with technologies that are suppose to be in demand (Ruby On Rails, NodeJS) I have had a very difficult time finding work this year. It's certainly more difficult now than in 2012 or 2013.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by cpprototypes on Wednesday August 03, 2016 @03:43PM (#12220889)
I had no issue interpreting the likely intended meaning of this: This person is saying they have been keeping up with new technologies the past 14 years (such as RoR, NodeJS now, but years ago Java held that spot, etc.) https://en.wikipedia.org/wiki/Principle_of_charity helps here especially these days when typing on a mobile phone can easily lead to typos and mistakes.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by altano on Wednesday August 03, 2016 @02:00PM (#12220047)
Neither Ruby on Rails nor NodeJS has existed for 14 years.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by kafkaesq on Wednesday August 03, 2016 @06:45PM (#12222096)
She was simplifying; most likely she meant:

"I have 14 years of commercial experience overall, with recent emphasis in high-demand technologies like RoR and Node.js"

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jgroch on Wednesday August 03, 2016 @03:01PM (#12220531)
yet FORTRAN and COBOL do

and so do reams of magnetic tape around the Beltway

who will maintain old code? you?

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by MOARDONGZPLZ on Wednesday August 03, 2016 @03:27PM (#12220754)
The poster specifically mentioned 14 years with these technologies. The fact that there are technologies 14+ years old is irrelevant to this point.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by logfromblammo on Wednesday August 03, 2016 @05:01PM (#12221485)
You can parse that statement in a more favorable way. She has spent 14 years acquiring experience with relatively new (or newly popular) technologies.

So 14 years ago, she would have worked with a technology that is now slightly more than 14 years old--I'd guess C#, which is now 16 years old. Maybe 9 years ago, she worked with Ruby on Rails, which is now 10 years old. Maybe 6 years ago, she started on Node.js, which is now 7 years old. Even now, she is likely keeping an eye on HN to see what would be most useful to learn next.

In other words, she has been continuously jogging on the technology treadmill, rather than staking out a niche to ride out until retirement.

This is likely the only way to avoid moving to progressively stodgier and less interesting companies as you age. The young and hip companies use the young and hip tech stacks. Established companies wait to see whether the new thing can cut costs or increase revenues before migrating, and part of that equation is not paying a premium for specialist developers that are currently in high demand.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by auggierose on Wednesday August 03, 2016 @04:34PM (#12221278)
Replace "with" with "including" and all the strange comments to this post evaporate. Every experienced programmer knows what is meant by this. By the way, anyone experienced picks up Node.js in a week.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by bfung on Wednesday August 03, 2016 @09:13PM (#12222715)
It's interesting to see so many comments on an imprecise wording of a sentence.

As humans, people can parse this sentence and infer the thinking and meaning behind it.

The related part of the problem with this the difficulty in finding a position is that computers and compilers cannot infer meaning - the statement must be exact (not precise, not accurate, exact). And for a programmer, making such logical gaffes is detrimental to speed and quality of a particular piece of work.

Could be unfair in assessing one as such, but a line of reasoning here does exist that I believe to be testable and valid. And life isn't fair.

Perhaps a piece to help you in finding a position better is to form the idea first, then reword it for the right audience (for programmers, be exacting, don't leave room for interpretation).

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Thursday August 04, 2016 @06:42AM (#12224655)
do you think it's anything to do with the name "susan"?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jgroch on Wednesday August 03, 2016 @03:00PM (#12220526)
I don't know why you've been grayed out.

Skills are skills. Even if you don't have the latest iPhone or Android flavor TangoUniformVoo 8.9.

Considering that i'm a bit rusty (no allusion intended), if i'm certified in Sun's Java 1.5/5.0, can i still program in OracleJava, and what about Google'sJava? ....Though maybe it takes a little bit of elbow grease and sharp elbows to push the script-kiddies currently in HRManagement aside.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by eitland on Wednesday August 03, 2016 @03:12PM (#12220635)
>> Though I have 14 years experience with technologies that are suppose to be in demand (Ruby On Rails, NodeJS)

> I don't know why you've been grayed out.

Because we oldtimers know that ruby on rails and especially node.js hasn't existed for 14years. Ruby on rails had it's first stable release about 11 years ago.

Actually used to be a recruiter joke/meme : young rails wizard wanted, minimum 10 years experience (back before 2005 :-)

That said, I didn't downvote, but I suspect this is the reason.

Edit: removed this, I might have misread the post as pointed out by others -> (not being careful with facts, massive hyperbole)

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by reitanqild on Wednesday August 03, 2016 @03:02PM (#12220540)
Joke or mistake?
[dead]
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mdpopescu on Wednesday August 03, 2016 @03:48PM (#12220925)
In that link we can read:

_I have done one major project with Node._

She was talking about details of NodeJS, in particular "all the latest packages".

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by brazzledazzle on Thursday August 04, 2016 @01:04PM (#12226954)
The lack of charitable interpretation in this thread is embarrassing.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by jgroch on Wednesday August 03, 2016 @03:02PM (#12220544)
interesting that that's interesting enough for you to research and note.

(please re-read the original article.)

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by vacri on Wednesday August 03, 2016 @05:48PM (#12221816)
It's in the first page of the user's comment history, not that hard to find on a quick skim.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by serge2k on Wednesday August 03, 2016 @03:22PM (#12220714)
> stupid ageist algorithm games known as "technical programming interviews"

I think there are problems with the current model, but is ageism really one of them?

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by potatolicious on Wednesday August 03, 2016 @04:22PM (#12221184)
To a large degree yeah - performance in "stupid algorithm games" is basically perfectly inversely correlated with "years since undergrad CS courses".
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by FT_intern on Wednesday August 03, 2016 @10:03PM (#12222877)
It's more of "years since last studied algorithms". University algorithms classes are useless for these types of interviews for the most part when 90% of the focus is on the proofs.

Most people I know spent time studying by themselves outside of class/class material.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by akadien on Wednesday August 03, 2016 @01:10PM (#12219567)
I'll add another voice to the job market for experienced developers and managers. It's terrible. I have an advanced CS degree, in-demand programming skills and leadership experience. I've hunted for full-time, part-time, and contracting work for a couple of months.

Interviews tend to go the following way: pass the initial interview, pass the programming test, pass the technical interview and never hear back (even after a couple of following up emails and/or phone calls). This grind really wears down one's self-confidence and outlook. It's been a depressing summer.

I have over 12 months of living expenses in my savings account and a very supportive wife, so I'm going to do a startup and see how far I can take it. It feels like a better use of my time and promises some new learning experiences compared to more interviewing.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @01:13PM (#12219592)
> I have over 12 months of living expenses in my savings account and a very supportive wive

Good on you. The family support is key during this - have been unemployed and non-productive, and family support helps tremendously to get through that period.

What sort of skills do you have, and what are you looking for (email me if you'd like)

It definitely can get very wearing on your self-confidence. Good luck to you!

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by sammydavis on Wednesday August 03, 2016 @05:37PM (#12221744)
I suggest reaching out and asking those companies why they didn't hire you. The recruiters might tell you something. Are you asking too much salary, or too little? There might be something setting you off. In seattle, there is still huge demand for devs.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by morgante on Wednesday August 03, 2016 @02:11PM (#12220142)
If you're interested in contracting work, I highly recommend checking out Gigster. It's extremely meritocratic—if you're good, you can easily make $200k+ a year, and there's no in-person interview hoop to jump through.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by erdevs on Wednesday August 03, 2016 @01:20PM (#12219682)
Wow, really sorry to hear about the struggle. And I hear you on this process undermining confidence.

I think going for a startup is a great idea, and it's awesome you have the family support to do this. Any ideas on what the startup will be yet? Lots of friendly people here who are willing to help in whatever ways they can!

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by sjackso on Wednesday August 03, 2016 @04:21PM (#12221167)
I went through a very similar period a couple of years ago. Would be glad to trade war stories (or just talk freebsd :) -- find my email in my profile if you like. Good luck, either way!
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by drharby on Wednesday August 03, 2016 @03:23PM (#12220716)
so it's not just me. When I was transitioning out of the miltary this time last year, getting a new gig was difficult but manageable. I have been at it full-time (since I tabled my start-up after 6 months of work) and you described my current experience.

You have to come in guns hot.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by 31reasons on Wednesday August 03, 2016 @01:46PM (#12219933)
I am in exactly the same boat. Advanced CS degree with high-demand skill set and live in CA but struggling to find job for last 2 months.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by equalarrow on Wednesday August 03, 2016 @01:16PM (#12219633)
Good luck! Truly. I think if you can't find a place that wants you, then you make your own. Or at least try. Something will work out for you, I'm sure of it. Key is to not quit, to not stop, and to always look for another way. :)
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by zubat on Wednesday August 03, 2016 @07:44PM (#12222360)
It's a good idea to bias entreprenurial in tech, IMHO. It's hard but it escapes the crush of the job search. If you can find a bit of investment that's even better.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by akadien on Thursday August 04, 2016 @09:28AM (#12225319)
Wow! Thank you all for the positive comments and encouragement. I think it's helpful to us all to share these experiences to show that we aren't seeing these trends in isolation.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by thedufer on Wednesday August 03, 2016 @10:53PM (#12223067)
> in-demand programming skills

No offense, but hasn't your experience shown that, regardless of how strong your skills are, they are clearly not in demand?

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by akadien on Thursday August 04, 2016 @09:33AM (#12225349)
Maybe, but I doubt it. I've had no problem getting interviews and navigating them. But I don't really know because most companies don't respond to follow-ups asking for feedback on why I didn't get the job and what I could do better.
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?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by johnward on Wednesday August 03, 2016 @12:49PM (#12219375)
I've seen co-workers, who were way more skilled than me, be on the market for almost a year. One in particular was my mentor and it took him about 8 months. Another was my direct manager and it's been over a year.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by alain94040 on Wednesday August 03, 2016 @01:26PM (#12219740)
There is an order of magnitude fewer jobs available for manager than for regular engineers. That's why it probably would take about a month to find a job as an engineer with a few years of experience, but 6 months or more for an engineering manager with 10-20 years of total experience.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by johnward on Wednesday August 03, 2016 @01:35PM (#12219844)
That makes sense. I think my manager is going to go back to being an engineer.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by initram on Wednesday August 03, 2016 @02:00PM (#12220044)
The rule-of-thumb is that you should expect to spend 1 month looking for a job for every $10,000 of salary you expect to make. So it's not at all surprising that an engineer would take 8 months to find a new job.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by morgante on Wednesday August 03, 2016 @02:17PM (#12220182)
I don't think that's a very helpful rule of thumb. For one thing, it defies the notion of supply and demand.

The hot jobs with modern skills are paying the most and also desperate to find people. It's people who favor older stacks who have trouble finding a job and get paid less.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by forgetsusername on Wednesday August 03, 2016 @12:23PM (#12219125)
>However, for anyone even mid-level, I don't think this has been good advice for several years.

The implication is that this advice has been good historically, but is "going away". In the article he argues to value jobs over job prospects.

Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @12:32PM (#12219214)
"Historically" is relative - I don't think it's been good advice for at least 15 years, but it might have been 'actionable' advice in SF/NY/etc for a bit longer.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by arenaninja on Wednesday August 03, 2016 @12:05PM (#12218953)
I agree. On my latest job, it took more than three weeks from me accepting their offer to a starting date, normally this is fine, but I was unemployed at the time. By contrast, my previous job was ready to start weeks before I was.
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by mgkimsal on Wednesday August 03, 2016 @12:08PM (#12218985)
How long did it take to get that offer, from when you started looking?
Re:Not Saying Winter Is Coming, but Where’s Your Coat? by arenaninja on Wednesday August 03, 2016 @01:34PM (#12219833)
Between 2-3 weeks, though I think my first interview was 1.5 weeks from when I started looking.