Hacker News new | past | comments | ask | show | jobs | submit login

So what? I don't care to compete with those developers or work for the companies who hire them.

If you live in a place where you can be selective with who you work for, I think this is the right approach.

If you are choosing to leave a company on your own terms you can be selective. If you are leaving because of layoffs or the company exploded, every week you wait you’re losing money.

Good luck with that.

In 17years I’m yet to have an interview where I’m quizzed on any JS framework or a store that isn’t relational, as a web and back end dev. Not heard the word GraphQL uttered In person ever :-).

A lot of jobs exist where they just want to know you can code and assume you’ll learn what you need as you go along. Experience in their languages seems most important.

The last time I had a hard core technical interview was in 1999. I had been working for 3 years and they needed someone who knew the ins and outs of cross platform C development.

By the time I got back out on the market ten years later, I was already 35 and I was able to talk about projects, architecture, trade offs involved in shipping, etc and I was applying for mid level roles - partially because I had become an expert beginner “engineer” even though I was good “developer” and they were getting me cheaply.

Eight years and three jobs later, my engineering skills had caught up with my age and I was applying for jobs where they needed a “change agent” or “someone who could speak experience into the team”. Now, I rarely get asked any programming questions. It’s mostly architectural and soft skill questions.

But, in the grand scheme of things. There are only two reasons anyone is interviewing for a job. Either they are being forced to find another job because of a layoff or the current environment has become inhospitable or they are choosing to find another job for more money/new challenges.

In the former case, where I need to find a job now, I need my resume to be buzzword compliant so I can find a job/contract fast. I also need to be ready to for more technical interviews especially for contracting.

In the latter case, I can be more picky and find jobs where they are looking for “principal developers”/team lead type of positions and the interviews tend to be more architectural/theoretical.

On a side note, I’m not sure what I want to do next. If I choose the cloud consulting/“digital transformation consultant”/“enterprise solution architect/consultant” route. Knowing a little about everything will come in handy - including something like Graph QL.

> There are only two reasons anyone is interviewing for a job. ...

I like the insight here about the two types of job and looking back at my jobs I think this is spot on.

There is another reason to change jobs which is for lifestyle reasons. Moving country, changing to a work from home/digital nomad would come under that. In the lifestyle case you are probably trading other factors for the lifestyle factor, so that would also more likely lead to the buzzword compliant route.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact