Interesting. Some (if not most) of the problems author describes would be a non-problem should he live in some of the more prosperous EU countries, so strictly

Interesting. Some (if not most) of the problems author describes would be a non-problem should he live in some of the more prosperous EU countries, so strictly speaking they are not linked to author's profession. Few hints he gives in the description of the interview process ("you'll be asked about algorithms", "you'll be asked why aren't you a CTO", etc) imply that he's interviewing for "Just A Programmer" positions -- is this the case? It looks like most of the difficulty in finding a job came from the disconnect between the position the author was applying for and his experience. JAP positions, even if they are advertised as "senior" normally require just the basic coding skills (i.e. you don't have to be really smart, mediocre is just fine) and therefore majority of applications will be much younger than the author, thus forcing the HR to ask the questions above. In a broader context of discussion about older developers, what's more interesting for me are two things: 1. Why there are so few roles being advertised for truly senior developers? There are plenty of complicated commercial software around. For example, Apple works on a novel mobile operating system with its own set of technical challenges, so I would expect kernel specialists to be in demand, but those openings are rarely visible (even at apple.com/jobs). 2. What do truly senior engineers employed by major companies do on a daily basis? How mere mortals like us can get closer to their expertise set? I'm talking about Guido van Rossum at Dropbox, Brian Goetz at Oracle, Michael Stonebraker (though I'm not sure he hasn't moved to academia full-time), etc.