> I used to mainly work in support, from 1st/2nd/3rd line to sysadmin, systems design and spec, network architect, everything. I do Windows, Linux, Mac OS, networking, comms, some programming knowledge, training, all sorts. But I'm too old to get work as a techie.

Across all the organizations where I have ever worked, I remember plenty of "old" guys doing this kind of IT stuff.

With that background, it's probably going to be hard to apply for anything different. Hundreds of applications but very low interview rate sounds like some sort of insurmountable mismatch between background and job. Or something silly in your application that is raising some sort of "red flag" for no good reason. If your age or date of birth aren't in the application, then that can't be it.

A likely-accurate age estimate is easily discernible for applicants who follow the common practice of putting their education history with graduation dates. A much rougher estimate is also possible with nothing more than specific technologies. You can do pretty well with employment history as well -- and I'd suspect that many among hiring managers or HR staff quickly develop a profile (consciously or not) that rules out both inadequate experience AND experience that feels too scattered or too long.

There could also be other factors, of course. Timing can be an issue. I've heard stories of people applying for hundreds of jobs (who were getting hundreds of applicants per open position) during the 2001-2003 bust. I wouldn't be surprised if it were the same thing in 2009 (though I found 2009 was a great time to be contracting -- businesses still wanted stuff done, they just didn't want the liability of an FTE on the books).

And there's always the possibility that the GP was simply not matched to the job, but it's not the foregone conclusion you seem to be assuming.

> I remember plenty of "old" guys doing this kind of IT stuff.

Most of the people I remember working with have health insurance, too, so naturally not having health insurance has rarely been a problem for working people.

(Which is an indirect way of saying: survivorship bias! The existence of companies that employ workers over 30/40/50 is positive to observe for anyone who'd like to make software/IT their career as long as possible, but the figure that'd probably matter most would be the relative hire rates among different age groups.)

I have tried most things.

I removed all the dates from my CV. No difference; a minimally intelligent pimp can add up. Degree, that's 3y; 3y in this role, 2y in that role, 2 years there, 16y freelancing... This dude is old.

So I removed the early junior jobs from my career history. Result, I got quizzed on how I walked straight into senior roles straight out of university.

So I left out some gaps in the timeline (I've freelanced quite a lot) -- and got curious about the specific tech I'd worked with in particular roles. Deploying Windows NT Server 3.1, or managing a migration from DECnet to TCP/IP, dates you.

You can fool the idiots, sure. But then your CV gets passed to non-idiots.

I don't advertise a DoB any more, nor dates of education, but I do give the years of my various permie jobs. It's easier to just be honest.

If they're ageist, as many are, then you can't lie or BS your way past that.

For example, I took a typing class back in the day and I was taught to always put two spaces after the end of a sentence. But today this flags you as "old".

Also, for me a properly formatted phone number looks something like this, per convention back in the day: 800-123-4567. But today you'd better write it like the following, else you're "old": 800.123.4567.

And so on.

Of course, one of the benefits of being "old" and still working in the tech field is the ability to toss out little gems like the following, which can be remarkably effective at putting some youngster in their place, when necessary: "Jesus, what a freaking noob thing to say/do!"

Another benefit is being able to walk into a situation where the local kids are maybe in a bit over their heads, whipping out what is to them some old and mysterious IT magic, and then start solving their problems in short order. One of the last times I did this I heard "Wow, we've been trying to figure out how to do that for years now!"

But I have done the pulling-magic-fixes-out-of-a-hat thing. It's fun. :-)

BTW, I think I remember a couple more of those resume flags. Back in the day I was taught to list things out like this, this, and this - that last comma being known variously as the Oxford, Harvard, serial, or series comma. (See what I did there?) But the "modern" way of doing it is this, this and this - with no Oxford comma.

Another had to do with email addresses. Dare you ever list something like an aol.com email address (which my wife still has, for example) lest it flag you as "old school"?

Interesting aside here as to things like Facebook: a few years back there was a notion being promoted among hiring folks (no doubt being pushed by Zuck himself) that if you weren't on Facebook then there must be something seriously wrong with you - that you were probably socially or technologically inept, and you were likely then not a good fit for hiring purposes. Today, of course, "Delete Facebook!" is all the rage.

1994-1998 Univerisity of Whatever

BS CS

—

Let’s guess the likely minimum age?

For the first >50% of my career, my speciality was that I wasn't a specialist. I can work anything with a keyboard and a display, fix it, tune it, make it talk to anything else, or at a push virtualise it.

But that's an obsolete skill in the near-monoculture of today, when IT means Unix, Windows and nothing else, talking Internet protocols. It's all boring now.

Usefully, though, I also write, so I changed course and became a tech writer. That's working out OK so far.

I am very happy about the move. I'm glad to have left the UK and my quality of life now is far better than it was. I wasn't forced into it. I had a fallback plan: I wrote and sold a book, and used the proceeds to pay for a TEFL course. My plan was to go travelling as a TEFL teacher.

As it happens, I didn't need to do it. Just as I was planning on it, a role abroad came up, and once I adjusted to the idea of a 75% pay cut from what I was expecting, it was a very good move.

I wouldn't particularly wish the fate of being _forced_ to change countries on anyone, but it's not a bad thing. Mind you, I had no family, no dependents, nothing. And I now have the disposable income to visit ageing parent more often than I did from London.

For 2 reasons.

[1] I only did broadcast/scattershot approach for the first year. After I got kicked off benefits the 2nd time (for attending a meeting of my startup -- an unpaid position -- in another part of the country) I stopped trying for anything I could do at all, anywhere, and started targeting my applications far more specifically, at things I was a really good fit for, with customised CVs etc.

No difference. Maybe a slightly higher rate of rejection letters.

[2] As others have said, timing.

I was freelance for most of the period 1996-2001 and 2003-2007. I decided to return to F/T work in '07 and applied for about 500 positions in 4 months before I got my first interview. I was hired over the phone, first interview.

It's getting to the interview that's hard. I interview well. I'm smart, lucid, eloquent, approachable.

These days, that means keyword matching, to get past 1st and maybe 2nd level selection.

2009/2010 were very bad. 2011, I got a role, but only very very briefly. 2012, I was even flown to Scotland for a 2nd interview, then got a second, non-IT role. 2013, I retrained in TEFL and went looking for teaching roles. End 2013, I applied for, and in early 2014, I got, a role in Brno, Czechia.

Doubftul. I was 40 when I was looking a couple years back and had a better conversion rate of application -> interview than I've had in my entire life. This is for Rails/React work. I had 15 interviews out of maybe 25 or so applications, had a few opportunities I turned down and landed perhaps the best job I ever had.

I'm beginning to look again at 42 and got 5 interviews in the first week and turned down at least at least 3x as many ops that I didn't like because I'm rather picky.

Are there companies that are pushing my resume to the side because they can glean my age by work history and graduation year? Perhaps.

What I will say though is your experience matches much of what I saw circa 2001 during the .com upheaval. I applied to 50 companies in the first month after the startup I was at blew up at, not a single interview. I was 25 at the time though. I knew many people in their 20s who gave up trying to get work.

I imagine looking for work in 2009 was a whole heckuva lot like 2001 depending on what field you were in.

It does seem to be better for programmers.

I was primarily a support guy, but also systems admin, network architect/rollouts/installation, training, even project management and security consultancy at a push.

We're regarded as far more fungible than coders. Coders make more money and if you are good in a niche, something popular, or something wildly obscure where it's hard to find people, then it's easier to find work.

2 of my former partners are programmers. One a general database programmer; she found it hard to retrain into suitably trendy databases, but once she did, she was off and running. Another in a very obscure language, but once she found a role, after a few years, she was making 50% more than my best-ever pay in London.

Either you write in something desirable (even if niche), or you're good enough to switch languages easily and readily (and regularly) retrain in something desirable. If you do that and are good, there's work out there.

If you're a humble grunt who fixes stuff, it's much much harder.

This is really where the notion of age discrimination would come into play, just this concern someone has been doing the same thing for X years and stopped growing - passion and curiosity is ageless.

That said, regardless of this timing is a big concern. I am bracing myself for a difficult market if the tech bubble deflates, and to that extent the next position I get is one I plan to be at at least 3-4 years.

* How do you even send that many applications? Is there some site where you can click thousands of checkboxes and apply? Do you send individual emails?

* What modifications do you make when applying from job-to-job?

* What adjustments did you make along the way? Did you change your resume or make any other major changes to how you were presented?

* For how many of those jobs did you proceed to an interview?

> * How do you even send that many applications? Is there some site where you can click thousands of checkboxes and apply? Do you send individual emails?

(3500/2) = 1750 hours, or just shy of one work year with holidays/vacation/etc.

If he is applying to multiple countries, of the course of 5 years, I wouldn't be surprised if 3500 jobs were posted for him to apply to that his qualifications were relevant for.

To be honest, I've applied to a non-negligible number of jobs every year just to keep interviewing and looking for better options. At 30min per application, the limitation was my time rather than the # of positions that were open given how flexible I am about location.

The only difference is I've been continuously employed and the applications are as much about maintaining my ability to interview effectively as it is firing bosses I don't care for.

As I said, though, from 2010-2013 I became a lot more selective, meaning it was only an hour or 2 a day.

I tried to use as broad a range of places as I could find. I bought the Guardian every Thursday for the ads in the Tech pull-out, until they cancelled that. I subscribed to Computing and Computer Weekly and went for any print ads in there, too. I applied to a few from New Scientist as well, borrowing friends' copies or going to the local libraries.

There are indubitably many ads for each role, and also fake ads for agencies wanting lots of people on their books, but you can't really tell real from spam, so I just applied for them all.

A few questions:

1. How many events do you attend per week? (could be related to any industry at all - could be a tradeshow, a panel of speakers, tech meetups - anything really)?

2. How many hands do you shake at each event?

3. How many people from these events do you follow up with?

If your score is "0" for all of the above then you are doing it all wrong.

You need to meet people in person, each week. The only way to do that short of showing up at the front desk, resume in hand, is to go to events.

You need to set a goal of attending 1-2 events per week (minimum), and figuring out how to get in front of hiring managers from companies you admire.

Figure out what events those people might attend socially or professionally. Get up to speed with events in various industries in your city.

Get comfortable with being uncomfortable at events, and find a way to make them enjoyable.

People who log facetime at events do immediately jump to the top of the pile compared to people like you who are #200-300 at the bottom of the stack in the applicant tracking system for some BS job posting on Monster (many of which are for non-existent jobs).

Don't be #300.

Start attending events!

There's no reason you should have to apply for 3,000 jobs, that is a waste of time.

Start working smarter - even if you are introverted and awkward in person.

Now pick your head, up, get out there and get started!

You can do this!

D.

90% of all successful placements come from people who have personal contacts with the hiring manager or somewhere else at the place doing the hiring.

90% of the remainder (9% of the total) come from headhunting firms that are actively looking for candidates to fill a particular special position.

The final 1% comes from placement advertisements and job search facilities.

And this from the lady who ran the job search facility for the University of Oklahoma (at Norman), called the “Job Location Program”. It covered every single staff and faculty position that was being hired for across the entire University.

So far as I can tell, the job placement situation hasn’t really changed much in the 30 or so years since.

So, you have to ask yourself, where do you want to spend your time and money? Do you want to spend it all in the area with only 1% placement success, or do you want to spend it somewhere else that might have a higher probability of getting you something?

I had a file of application letters, needing minimal customisation to fit. Copy, paste, add salutation/role/location, attach CV, send.

My CV is longish -- 3 pages -- but then, so's my career. I've done what I can to optimise it for keywords that will get hits when pimps do searches.

The CV didn't get customised for specific applications unless I really wanted that role and thought I'd be perfect for it. It didn't help. I don't bother doing it any more. I maintain a "writer" and a "techie" CV, just in case.

Every morning, I would make a cuppa and breakfast, sit at the PC, read a few comics and the news, then start applying. I'd keep going until there were no vaguely relevant positions left. It took from 2 to 5 hours most days.

I logged every application in an OpenOffice/LibreOffice spreadsheet: date, title, reference number, agency. Every fortnight, I signed on at the Jobcentre, and took the printout of the last 2 weeks' applications to get it initialled as evidence. I needed that in August; by then, the printout was about 2cm thick.

I probably still have it somewhere. Perhaps I should put it on Dropbox for people to see the evidence. :-)

Without knowing the details, I'd guess that the age prejudice is in your head, and instead your resume just raised a bunch flags. One common mistake is listing several disparate skills, with no coherence; recruiters need to be able to categorize you in one of their "boxes" - SRE, engineer, Unix sysadmin, Windows sysadmin, security analyst, leader CTO-type, etc. Jack-of-all-trades are usually the first ones to be dismissed.

Other common flag is lack of consistency in your trajectory. Candidates jumping between jobs too quickly may be a problem, unless you're looking for a short-term contractor.

Also, after you've been out of the market for a couple of years, it gets harder to get back in. So it's natural that now you're having to turn down offers. Again, another proof that age had nothing to do with your low success rate.

You should keep this fact in mind as you write a resume and decide which jobs to include, which jobs to perhaps delete, and whether you want to include your graduation date. It isn't necessary to include a graduation year or all of your jobs, so you can usually shave some years off your age "on paper" without being considered as deceptive.

Sometimes I'll add a line "Previous experience included..." to indicate that there is prior work experience, but I don't list the years.

1. Don't include graduation dates in your resume, just the University/School name and Major(s) 2. Truncate your resume to just slightly over the required years of experience. e.g., include past 12 years experience for a job which requires 10+ years 3. Keep your resume to under 3 pages (max). Nobody has the time to wade through an 8 page resume, even if you have worked on the most awesome projects at the start of your career

Seemed to work for me

That may answer the question for you, but ageism is a legal concern and disqualifying candidates because they didn't tell you when they graduated isn't dissimilar to asking someone how old they are in a job interview and refusing to hire them if they don't.

The goal is to appear no older than a 30-39 year old professional on the job application as much as possible.

22+15 = 37 (24+15 = 39, if a masters)

Do you as a potential employer care that I was an Informix DBA in 2000?

HR wants experience who isn’t at peak earnings. If you tried to recruit me from a Jon I liked at 30, a 40% raise would be affordable. Now, no mas.

A 15 page menu isn't better than a 1 page menu... A spa advertising every stone in its parking lot doesn't make you think nice things about their mud baths...

The implication of your post is that the hiring managers responsible for 3500 jobs are *all" discriminating on age. That seems unlikely, if only because there are people in the UK tech sector older than that who can still find roles, so evidently not all managers discriminate.

It is endemic in the Anglophone world. I also speak a little German, French, Norwegian and at a push Spanish and Swedish, and I applied to anywhere that was hiring English speakers there, too... with cover letter in the local language, naturally.

Zero interest.

So I think it's a Western problem.

Q.v.

https://techcrunch.com/2010/08/28/silicon-valley%E2%80%99s-d...

https://newrepublic.com/article/117088/silicons-valleys-brut...

I encounter virtually none here in the former Communist Bloc, where people are more interested in me because of my experience.