State of the Market

[Fraidycat]

If you don't have any recent experience (because you've been on the bench for a while), it might be worth spending some time on that rather than cycling all day. At the very least, you can see whether it makes any difference to your future interviews.

That is actually one of the few advantages a developer who has been on the bench has over others.

The obvious thing to be to work on a bleeding edge pet AI project, so you can show you have used and understand the latest AI buzzwords like MCP.

Its not commercial experience but it is way better than 0 experience on the topic, and better than saying you have done no development work in the last few years.

And most head of ITs are under pressure to think about how they can integrate AI into their products so may show some interest rather than just roll their eyes.

[SchumiStars]

That is actually one of the few advantages a developer who has been on the bench has over others.

The obvious thing to be to work on a bleeding edge pet AI project, so you can show you have used and understand the latest AI buzzwords like MCP.

Its not commercial experience but it is way better than 0 experience on the topic, and better than saying you have done no development work in the last few years.

And most head of ITs are under pressure to think about how they can integrate AI into their products so may show some interest rather than just roll their eyes.

I agree with all that you are saying. However I have never been one to learn tech without a business driver.

I also have too many hobbies which I would rather be doing that reading about boring stuff. Sorry but it is.

Think I am becoming more less marketable by the day.

That's how life works, I suppose. So whether I like it or not, retirement may now be calling. I just have to work out to get through the next 10/20/30yrs before I do buy the farm.

[Dorkeaux]

Had an interview for a permanent role which I didn't get. Can't really moan as they found someone they preferred and I wouldn't have changed the presentation or interview if I did it again tomorrow.

<ElSnippo>

Indeed.
I occasionally blow interviews, but mostly I've presented myself in the clearest manner I'm capable of.

It gets back to what I keep saying about the lack of correlation between one's apparent skills and suitability for a role and actually being hired to do it.
It's a numbers game. Do as many as you can, as well as you can and if you make any mistakes try to learn from them.
Something will eventually stick.

I'd love it if the rare feedback I got from interviews was useful, but it never is.
Mostly (as many other posters have found) it's factually incorrect, genuinely stupid or simply exposes the vast chasm between the job spec and the interviewer's expectations.

[willendure]

I'd love it if the rare feedback I got from interviews was useful, but it never is.

Applied for a job recently in a niche technology. I am also the top contributor of open source libraries in this area. Feeback - not enough experience!

[fulcon]

Applied for a job recently in a niche technology. I am also the top contributor of open source libraries in this area. Feeback - not enough experience!

Reminds me of this tweet:

[SchumiStars]

Applied for a job recently in a niche technology. I am also the top contributor of open source libraries in this area. Feeback - not enough experience!

This is brilliant. Makes me feel better.

It's really odd ATM. Interviews used to be a way of gauging whether a person would fit in and is capable of doing the job.

Now unless you have exactly what they want at that exact time it will be a no.

Just as an example, I can see you have experience in Java 8 but this project requires experience in Java 17. Yes, it's no problem, I can learn the newer version and I have all the other skills.

That would not work in today's market. 10yrs ago, that answer would be acceptable In fact, I have been underskilled and expected to pickup the remaing items.

Last year, I predicted incorrectly that the market would be returning by Oct 25. Looks like that estimate may now be Oct 26.

And what happened to that massive new AI business park the government was creating outside Bedford, it's all gone a bit quiet on that front. I knew it would die before it started. Stupid idea or incentive really.

[willendure]

Just as an example, I can see you have experience in Java 8 but this project requires experience in Java 17. Yes, it's no problem, I can learn the newer version and I have all the other skills.

In that situation you put Java 17 on your CV and spend 1/2 hour mugging up on whats new in 17 before the interview.

But yes, I get your point, everyone is being highly highly specific about what they want and any application that doesn't tick ALL the boxes is binned. Hardly surprising when you know they are getting 500 applications.

Unfortunately it means that genuine talent is finding it hard to get through - or being forced to outright lie just to get a foot in the door. If you don't you get nothing, so what is there to lose beyond the embarassment of getting caught in the act?

One of the solution architects I worked with currently is a complete blagger and not very good at his job. I think I see how he got it though - told a good story on his CV then blagged the interview. The interview process was not thorough at all.

[willendure]

Reminds me of this tweet:

With AI technology evolving so rapidly so you this kind of thing quite often there. Need 10+ years experience with LLMs or something.

[SussexSeagull]

Indeed.
I occasionally blow interviews, but mostly I've presented myself in the clearest manner I'm capable of.

It gets back to what I keep saying about the lack of correlation between one's apparent skills and suitability for a role and actually being hired to do it.
It's a numbers game. Do as many as you can, as well as you can and if you make any mistakes try to learn from them.
Something will eventually stick.

I'd love it if the rare feedback I got from interviews was useful, but it never is.
Mostly (as many other posters have found) it's factually incorrect, genuinely stupid or simply exposes the vast chasm between the job spec and the interviewer's expectations.

I really don't chase feedback that much as it is usually more to justify their decision to themselves rather than to help you, plus you can't legislate for one of the other two (I believe) people they talked to being more suitable in their minds.

As you say though, it is a numbers game and one will eventually fall into your lap.

[SussexSeagull]

Not having any personal projects or a history in open source is also kind of prejudice against people with a life and commitments outside of work as well and is another example of the ageism that is prevalent in the industry.

I remember when the only way that work used to intrude in my private life was making me go down the pub on a Friday.