Friday, 17 July 2026

An Open Letter to Tech Recruiters


Dear Tech Recruiters (and by extension, the clients you work for),

A recruiter messaged me directly last week, which should have been a good thing. An actual person reaching out - wow! 

Then they sent through the job ad itself: an AI-generated checklist so long and so specific that no real human could tick every box unless they were already doing the exact same job on the exact same stack at a direct competitor. The contrast between the personal touch and the impersonal wishlist was jarring, but sadly common in 2026.

The problem today is that AI has changed recruitment, and made it much, much worse. I want you to understand how this all looks to people like me.

First up - I've read enough job ads over the years to build up a "Hall of Fame" of recruitment nonsense, which I present to you now. My simple advice for all of these - do not do this.

Job Ads Hall of Fame

1. The vendor-specific must-have

Candidates must have direct hands-on experience in [Specific Platform].

A while ago I worked at a place which used a CMS I wasn't familiar with. But I've got 2 decades of experience in other CMS's, and 3 decades in tech. I asked a developer to talk me through the architecture, and as soon as he explained it, I could relate my existing knowledge to the new platform.

If you're in a leadership role, the skill is understanding the functionality, being able to define the problem, and knowing how to achieve the required outcomes. Functionally, every CMS, every CRM, every email system, every operating system, and every AI platform, does the same thing as its competitors. Learning one specific piece of software doesn't mean you understand the functionality and processes and decision making required to achieve the best outcome. Screening someone out for a technology leadership role based on a specific vendor is shooting yourselves in the foot.

2. The narrow sector obsession

Essential: minimum X years experience within [Specific Sector].

Modern software doesn't behave differently depending on which industry runs it. Sector context matters for some roles, but for most tech positions this requirement just shrinks the pool for no real gain. A technologist who's worked across sectors usually brings new ideas, concepts and processes that the narrow-industry-focused haven't considered. Screening someone out for a technology leadership role based on the sectors they've worked in previously is a nonsense.

3. The impossible experience requirement

10 years of experience as a pre-sales or engineering manager in relation to AI.

I've already covered this one: Google wanting someone with 10 years of AI experience. When I posted that on LinkedIn I got massive engagement, mostly the laughing emoji. It boggles the mind that this needs to be said out loud but - if your role requires more years of experience than the technology has existed, you are effectively telling us all exactly why we don't want to work for your company. Please apply some logic here.

4. The combination

Must have: [Specific Tool] certification plus X+ years in [Specific Sector].

This one combines several or all of the above. The only person who ticks every box is already doing this exact job, on this exact stack, in this exact sector, at a competitor. Which begs the question - why would they leave? And more importantly - why bother running an ad, when you know exactly who you're targeting - just pick up the phone and try to headhunt them!

5. The mystery salary

Salary: Competitive.

This tells me nothing, except that you're OK with me wasting an hour crafting an application for a role before finding out the role pays $50k less than my last role. A simple dollar range would save everyone some trouble.

6. The obviously AI-written ad

We are seeking a dynamic, results-driven professional who will leverage cutting-edge technology to drive transformative outcomes in a fast-paced environment — someone who can seamlessly wear multiple hats while championing innovation at every touchpoint.

You can spot these in the first sentence, and that em dash is a dead giveaway. It seems everyone wants a dynamic, results-drive professional and keyword keyword keyword these days. Please understand that when you post a job ad that sounds like a computer has generated it, you are telling us an awful lot about your organisation that maybe you're not intending to tell us.

Next up, we have all the ways candidates cop the raw end of the deal.

Bad Behaviour

  • The keyword-blast. Recruiters who've clearly run your CV through their keyword-matching software, without reading it, and then send "opportunities" that have little to no relevance to your actual skillset or stated preferences.

  • The silent rejection. A form email with no phone call and no feedback, when at senior level a 5-minute call costs almost nothing and leaves a completely different impression.

  • No rejection at all. You apply and simply never hear back, not even the generic form email. We know you have the automated systems to send that email, it's one click, and that's bad but it's still better than nothing.

  • The fake recruiter. A dodgy recruiter has basically stolen a job ad from a job board and started contacting potential candidates directly. Why do they do this? Unclear, but it gives the whole industry a bit of a bad odour.

  • The junior who manages the boss's LinkedIn account. As a candidate you may assume you're connecting with the senior recruitment expert on LinkedIn who understands both sides of the industry and is best placed to help you find the perfect role. And you would likely be wrong. You're just as likely to be talking to the office junior who operates that account on their behalf, and the senior expert never sees anything you've said.

  • AI interviews. Yes, the absolute best way to assess potential candidates is to put them in front of an AI bot as a first-round interview. Nothing speaks "cultural fit" and "positive work environment" like assessment-via-algorithm and the subliminal message that we're too busy to actually talk to you.

  • Recruiter wars. Two recruiters call you within minutes of each other about the same role, then spend more energy fighting over who called first than actually finding you a job, and somehow one of them ends up angry at you for it. (This really happened to me).

  • The non-compete trap. Recruiter-mediated contracts sometimes lock the candidate out of working directly with the client for a year after the contract ends. This does nothing for either the candidate or the client, it's purely to protect the recruiter's ongoing commission.
  • The fake job ad. Comes in three flavours: the same ad recycled every few months while a recruiter quietly harvests CVs for their database, the ad for a role that's already been informally filled but still has to be publicly advertised, and the outright scam ad whose entire goal is separating you from your cash.

I'm sure there are more, and I'll keep adding them as I think of them (or experience them).

Understanding Tech People

The appeal of a career in technology for people like me, is the endless supply of new puzzles to solve. 

Job ads like the Hall of Fame give a whiff of "you must conform to exactly what we need" rather than "this is a place where we will value your contribution and you will learn and grow". A checklist like the one I received tells me that the recruiter is inundated by AI-generated slop CVs and is running a drastic slash-and-burn using AI, to narrow down the list and identify CVs with the most ticks, and this isn't really about people at all any more. 

The rest of the Bad Behaviour section is just more of the same - recruiters and organisations optimising for their own efficiency, and leaving candidates dealing with the consequences.

Technology Should Make Things Better For People

My philosophy around technology has always been that it should make things better for the people or organisations using it. So it's reasonable to ask who's actually better off with AI-assisted recruitment, and I've come to the conclusion that:

  • Job seekers aren't, since AI-written ads and AI-run screening have made it harder to get an application in front of a human.

  • Companies aren't, since filtering this hard on tick-box criteria screens out capable people before anyone gets an opportunity to assess whether they're any good.

  • Recruiters aren't, since they're flooded with applications which make it much harder for them to genuinely match the right person to the right role.
Excellent.

Looking Forward

Where does this leave us all? A few months ago I asked an AI tool to review my own CV, only to discover it was being identified as a beautifully optimised, circa-2010 CV. So I used AI to help me optimise it - for AI. I joked to a recruiter that AI writes the job ad, AI cross-posts it to every job board going, candidates use AI to mass-apply, and recruiter systems use AI to filter the applications. But where do the people fit in?!

Recently, a director of AI posted on LinkedIn about hiring for positions on his own team. Every resume he received was, in his words, "identical. Not similar. Identical." Flawlessly formatted and perfectly keyword-matched to the job description, to the point where he couldn't tell where the resume ended and the person began. He couldn't even use AI to sort the candidates, because when everyone feeds the same job ad into the same tools, the outputs come out looking much the same. His conclusion was that the most valuable signal left in an AI-run hiring process is evidence an actual human wrote it.

I left a comment under that post, which got more engagement than most of my own posts: "And the problem with not optimising for ATS is that you can't get through to an actual human in the first place. What a hopeless conundrum we've created. 😂"

I've got decades in the tech industry and I'm a strong candidate for a lot of roles, but all of these AI "enhancements" to recruitment only make me less likely to apply. I doubt I'm the only one.

The recruitment process is badly broken...

Regards,
A candidate your checklist just screened out, again.

Share:

Sunday, 28 June 2026

Adobe have disabled legacy activation servers 🤬

I bought Adobe CS5 Master Collection years ago on a perpetual licence at full price, which is supposed to mean I can install and use it for as long as I want, on whatever machine I want. Adobe allows two active installations at a time, so when you get a new device you deactivate the software on the old one and activate it on the new one. I've done this a couple of times over the years without any trouble.

I got a new laptop recently. This time, I deactivated it cleanly on my old laptop, then went to activate it on the new one and the activation process timed out. There was no error that made sense or obvious path forward, just silence.

After digging around online I found out why. Apparently, Adobe quietly switched off the activation servers for legacy pre-subscription software in 2025 without telling anyone.

I've never asked them to support the software. What they've actually done is remove the mechanism that lets someone who legally bought a perpetual licence activate their own product. There's a Consumer Rights Wiki page documenting this, and some Reddit threads and here full of other people describing exactly the same runaround.

I feel like I've been battling Adobe's bullshit for years. I tried (and failed) to upgrade to CS6 back in 2013 when they first started trying to force everyone onto Creative Cloud, and in 2015 I struggled for hours just to get routine software update to install due to their poor form. In 2017 I asked them how to use my product on a high resolution screen and their only advice was to upgrade, which was technically wrong - a guy called Dan Antonielli had already published a registry fix in 2014 that solved it without any Adobe upgrade at all, and when Windows finally added its own native high-DPI override in 2019, he documented that too. Neither fix cost a cent or needed a subscription.

Thirteen years on, it's the same company finding a new way to push the same outcome. I'd like to say they are the epitome of enshittification, except they haven't gradually enshittified, they've always been shit to their legacy customers.

What actually happened

The case history is worth laying out because of how many times I had to start the conversation from scratch.

  • Case 1 - ADB-45560212-Y9G0 (3 June). Opened and closed the same day. The summary field says "informed regarding EOL," which is Adobe's way of telling me the product had reached end of life without offering anything resembling a fix. I replied two days later refusing to accept that, but by then the case was already closed, so my reply bounced to an unmonitored inbox.

  • Case 2 - ADB-45614666-D7P5 (5-11 June). Reopened through chat and told the backend team would review it. Five days later they came back with an offer to sell me a Creative Cloud subscription at a discount, which wasn't what I'd asked for at all. I said no, told them I wasn't interested in renting software I already owned outright, and pointed them to the Consumer Rights Wiki page and Reddit threads. They escalated again, and two days after that issued a new serial number, which turned out to be invalid. They closed the case before I had a chance to tell them that, so I had to wade back in again.

  • Case 3 - ADB-45714968-L0H3 (closed 12 June). A dropped chat, closed with the explanation "sorry, we were disconnected" and nothing resolved.

  • Case 4 - ADB-45761286-P4T8 (16-17 June). The agent ran a remote support session and worked through everything I'd already reported, finding nothing different to what I'd already told them. He said he'd escalate it. I woke up the next morning to find the case closed, with no further communication at all.

  • Case 5 - ADB-45818350-V0L7 (19-23 June). This is the one that worked. I got through to an agent called Paridhi, who actually engaged with the problem. I had to point out myself that the "new" serial number from Case 2 was for CS6 rather than my actual product - when I asked why I'd been given the wrong version, I was told they'd assumed I'd appreciate the extra features - and Paridhi escalated it properly. My product is CS5. It doesn't have CS6's features, because it isn't CS6. A new, working CS5 serial number arrived within 24 hours.

The best part of a month, 5 case numbers and 2 serial numbers, one of which was for the wrong product entirely, on top of a dropped session, a session that vanished without explanation, and an outright refusal dressed up as a routine end-of-life notice. Not everyone I dealt with was as capable as Paridhi. A few of the advisors along the way genuinely didn't seem capable of troubleshooting or resolving anything. Closing tickets seemed to be the actual goal rather than fixing the problem, which made me wonder if that's a training issue or a KPI. I'm not even sure if there was a single reason it finally got sorted, but I was prepared to keep pushing.

Being handed back what I already own, framed as a favour

When the working serial number finally turned up, it came with a condition attached: a limit of two future activations, with me responsible for managing them from here.

That's presented as a concession, as if letting me use software I already paid for in full is something Adobe is generously extending to me rather than the bare minimum they owe a customer who bought the product outright. I own this licence. Adobe doesn't get to decide, after the fact and off the back of their own decision to shut down the servers, how many more times I'm allowed to install it.

If you're here because the same thing happened to you

Given that my 2015 CS5 update post is still the second most visited page on this blog after all these years, there's a decent chance you found this the same way. A few things that helped.

Understand that this is deliberate, not a bug. Adobe retired the CS5 and earlier activation servers on purpose, and there's no self-service fix or working offline activation option. Some of the "solutions" floating around online involve replacing DLL files with unofficial downloads, which I'd avoid entirely given the security risk and the likelihood it breaches your licence terms anyway.

Don't accept the first no. Every case that got closed without a fix was closed by someone who either couldn't or wouldn't escalate it properly. The one that worked only worked because I kept going back and eventually reached someone who took the problem seriously.

Cite the paper trail. Referencing the Consumer Rights Wiki page and the Reddit threads in my emails visibly shifted the tone of Adobe's replies. It tells them you already know this is a documented, ongoing issue rather than something you've stumbled into alone.

Ask for the case to stay open until you've tested the fix. Not that this actually worked - hence my 5 case IDs - but it's worth asking anyway so it's documented. The first 4 of my cases were closed before anyone confirmed it actually worked, but Paridhi could see this had occurred within my account and they committed to keep the case open, and actually did follow through.

If you're in Australia, mention the ACCC. This behaviour is a breach of Australian consumer law. I couldn't tell you whether it would hold up as a formal complaint, but every little bit helps.

This wasn't incompetence, it was a decision

Adobe have spent years trying to entice perpetual licence owners onto Creative Cloud. It didn't work on me because there's nothing in the subscription that's worth the additional cost to someone who already owns the software outright. Once persuasion failed, they moved to the next option: if you won't switch, you can be forced to. Switching off the activation servers isn't a cost-cutting decision about old infrastructure, it's a deliberate move against exactly the customers who'd already said no to the upsell.

I'm not a lawyer so I can't say this is illegal. But deliberately disabling a paying customer's ability to use software they own outright, then handing it back with conditions attached as if it's a favour, is unethical at best.

I will never pay Adobe another cent. Between open source tools and general purpose AI now handling most of what I'd have reached for Photoshop to do, I don't need to. Adobe knows the subscription pitch didn't land with people like me. I suspect that's exactly why they stopped dangling the carrot and decided to brandish the stick instead.

I got there in the end, but it took the best part of a month I shouldn't have needed to spend. Most people don't have that kind of time, and Adobe is almost certainly counting on that too.

Share:

Thursday, 7 May 2026

Privacy Risk in Australia


This week is Privacy Awareness Week in Australia, and I attended a webinar on AI, automated decision-making and privacy risk, presented by privacy law expert Anna Johnston from Helios Salinger. Over a thousand people registered for the webinar, an impressive effort.

The webinar covered a lot of ground. What it mostly did for me was reinforce a view I’ve held for a while: privacy risk in Australia is consistently underestimated, frequently treated as a compliance checkbox, and almost never given the same weight as financial or reputational risk, despite being directly connected to both.

Read the full article 

This article was first published on the ENVEE Digital blog.  

Share:

Thursday, 30 April 2026

Using AI to review and optimise your CV


A couple of months ago I returned from a sabbatical and, out of curiosity, asked claude.ai to assess my 2025-version CV the way an ATS (automated recruitment screening) system would.

Turns out I'd nailed it - it was perfectly optimised - for 2010, which was a little confronting. 😂 

The advice back then was to stuff in as many keywords as possible so you'd get indexed in recruiters' databases. Most people with a tech-based CV from even earlier had a "Technical Summary" page which listed every product name you'd ever laid eyes on. I'd removed that but kept the keywords and it used to work pretty well. But systems got more efficient, AI got added, and I hadn't updated enough to stay relevant.

I ended up working through a process using AI to help me to audit and rebuild it. Everything went into a master document, which means now I can pull together a tailored CV for a specific job application in about fifteen minutes. It took some time to set up but I'm quite pleased with how it works now.

I joked with a recruiter recently that AI writes their job ad, AI cross-posts ad to recruiter website and job boards, potential candidate uses AI to mass-apply for roles, recruiter systems use AI to filter - where are the people?! It's not really a joke though. If you're applying for roles and hearing nothing back, it's worth considering whether your CV is actually reaching a human. 

Learn more about What AI actually does well on the ENVEE Digital blog.

This article was first published on LinkedIn 

Share:

Friday, 17 April 2026

"So, how was your weekend?" 😂

I read an interview with a female CEO in the The Australian Financial Review the other day (unfortunately paywalled so I can't share it), and she was asked what was the most valuable career advice she'd ever received. Her answer - "treat people the way they want to be treated."

This reminded me of a workshop I attended in the early 2000s, run internally by the global software company I worked for at the time. All the project managers were put through Myers-Briggs and DiSC assessments and spent the day learning how to apply that understanding when working with others - not just to understand themselves but also to learn to recognise what other people actually needed from an interaction.

The instructor started with a story I've always found amusing. Like a lot of us, he'd grown up being taught to treat others the way he wanted to be treated - "do unto others" - and he'd recently worked out that wasn't quite right.

He was a chatty guy, the type who liked a bit of small talk and would ask about your weekend before getting down to business. He just got a new boss, who was logical, direct, always on the move and clearly just wanted to get sh*t done. The working relationship was proving challenging and the instructor was starting to think about moving on.

Then he did this same workshop and worked out he was a high "I" in DiSC (Influence), and his boss was quite likely a high "D" (Dominance). So he changed his approach. Instead of the friendly small talk, he started opening his boss's door and saying "Morning - about that report - do you want option A or B? And then should I do C or D?" The relationship improved almost immediately.

A few weeks later he was at his desk on a Monday morning when his boss came over, leaned casually on the edge and asked "So, how was your weekend?". Yep - the boss had just done the same workshop. 😂 

I've thought about that story a lot over the years, and told it a few times myself - particularly to IT teams, where the "us and them" dynamic with the rest of the business can take on a life of its own. It's a really effective way to demonstrate the point about how to get the best outcome from an interaction. It helped shape how I approach leading teams, work with clients and navigate organisations - by trying to work out what someone else actually needs from an interaction, rather than defaulting to what I'D want. I realised much later that's basically the foundation for Design Thinking, although we didn't have the name for that then.

Happy Friday 🍷 

This article was first published on LinkedIn 


Cover image: By User:JakeBeechMyersBriggsTypes.png, CC BY-SA 3.0, Link

Share:

Archive