It'll depend on what you've worked on, what you want to work on and how you present at interview. If you've got 25 years specialised in some crackpot internal

It'll depend on what you've worked on, what you want to work on and how you present at interview. If you've got 25 years specialised in some crackpot internal system that noone else cares about you may have a bad time. If you can obviously add value to whatever the company is currently worried about, it'll be fine. There's some risk you'll be grilled on optimal hashtable design by a raw graduate who doesn't know the right answers. Some places expect you to write code using unfamiliar tooling while someone watches over your shoulder. There's a lot of nonsense in programming interviews. That's not very age dependent though, except in that you might remember a less absurd approach from last time around.