So What? A Recruitment AiDE, pt 1

Greg Wyatt • October 23, 2025

An introduction


Welcome to the first edition of A-nt—I Recruitment.


If you stuck around with me on substack over the past three years, some of this will be familiar. I’ll be curating my most popular series of

writing, for a new audience on LinkedIn.

I've stopped writing on that substack for now, but feedback is that it's engaging and helpful, which I hope you find the case too.


What can you expect? These are series that I've already published - around a year's worth of content.


  1. The AiDE framework for attracting ideal hires
  2. Innovation from iteration – how other industries can improve recruitment
  3. No problem – recruitment problems that drive opportunity
  4. Recruitment reflected – how candidate experience and resentment can improve our work
  5. Negotiate this – how 'Never Split the Difference' by Chris Voss applies to hiring
  6. The art of recruitment – Sun Tzu because of Ross, and because humans don't change
  7. Selected others


These were tremendous fun to write and, through sharpening my ideas, have made me a better recruiter. I’ve also seen recruiters I respect adopt my ideas, such as “reciprocate the care your candidates take” as a fair balance in a volume marketplace.


Why the tremendously stylised name?


You’ll see the capitalised AI, straddling nt, spelling out anti. But this isn’t about hating AI and recruitment – I love the opportunity both have. We all love an em-dash too.


It’s because the opposites in recruitment aren’t what we do, it’s why we do it.


Are you driven by systemised, scalable, profitable recruitment?


Or do you always want to put people first, with a candidate-centric approaches that delivers long-term outcomes?


I’d wager you can do the first without the second, and the second without the first.


The real win is when you nail the philosophy of human first recruitment, and enable it through technology.


It needs to prioritise on the needs of ideal candidates, so that everyone benefits. Instead of the typical employer first approach.


And so here we are with the first article, and part of the series on my AiDE (Attention ikigai Definition Experience) framework.


It’s called:


So What?


A couple of years ago, I ran an experiment on LinkedIn to see what meaning readers would take from this post:


“Today I ran 5km in 33 minutes. I am 42, 6 ft 2, 200lb and have a resting heart rate of 50bpm.

What does this say about me?”


The plan was to analyse the commentary, look for themes, and use these for further content on advertising, CVs and what people take from social media.


Across the 100 or so commentators, only one person rightly said “nothing at all”.


While the other commentators said anything from “don’t beat yourself up” to “well done” to “that resting heart rate indicates a high level of fitness” and questioned the running time.


One kind gentleman took it upon himself to describe his fitness journey and how I should be proud that I’d started running in my 40s.


He also took offence when I explained the rationale for the post, in a subsequent one.


The reason for the wildly different responses is that this post lacks context.


What kind of background can you imagine that would have given relevant substance to this post?


If all the post had said was that first line, a rational response would be:


"So what?”


It’s a post rife with ambiguity, where the only meaning is that which is taken from it.


And 99 people found their own meaning.


I did inadvertently lie though.


My 6 ft 2 height was confirmed by a doctor in 2008.


I went to the hospital a couple of weeks ago, and now I’m a smidge under 6 ft 1!


The gravity of the situation hasn’t passed me by, nor has the nature of subjective truth.


Does it matter more what we write, or more how others read those words?


Recruitment is an industry where ambiguity, clichés and clever-speak hide meaning from its consumers.


Take this classic first line in an advert:


“My favourite client is a market-leading employer of choice going through rapid growth.”


I think it’s only natural for an recruiter who knows no different to write this and both believe it and believe that readers will believe it.


What follows will typically be something like -

“Their friendly, innovative and progressive team is looking for a Retro encabulator designer with these responsibilities: <insert anonymised job description>”


Before the grand finale of “We act as an employment agency, don’t do isms and if you haven’t heard from us in one week, you are dead to us”.


It’s a natural thought process, and symptomatic of a transactional recruitment system.


Without a full brief, without insight, without training or an inclination to learn copywriting, and with a need to advertise, how can you do any different?


If it were the only advert to say exactly this, it wouldn’t necessarily be a problem.


Except that adverts commonly do read like this, making it pointless to actually read their content. You might as well just go off the job title, salary and location.


And if you do bore yourself dense reading them, can you come away with any response but “so what?”.


So – so what?


As well as a natural reaction to piffle, it’s a handy editorial tool, used by anyone that wants to strip away ambiguity and show both context and meaning.


It’s much like 5Y, an iterative question that lets you peel back onion layers to find meaning.


So what, “market-leading” – what does that look like in practice?


Why are they growing rapidly – is it because they’re full of hot air?


What does innovative and progressive look like in their team? What is friendly?


Ask ‘So what?’ of your content and you’ll give better meaning.


Better yet, ask others what they make of your content.


Does your advert actually have any meaning?


Can people tell what your job is from your job description?


Do your interview confirmations regularly get questions asked of them?


Back to that post at the top. I did follow up with some good posts (IMO) showing the problem of ambiguous meaning. Here’s one of them from last week:


“What your CV says: ▪ 2021-2022, Sales Manager - achieved £500k in sales

What a reader might assume: ▪ sacked after 12 months falling 50% short of a £1m account management target

What you meant: ▪ achieved 125% against a £400k new business sales target, completing a 12-month maternity contract

Ask 'So What?' of the responsibilities on your CV. Give better meaning to your words, so that we don't have to find our own.

Unless you were indeed sacked, in which case ambiguity may work in your favour.

Agree, thoughts?”


I don’t think it’s much of a leap to find wildly different meanings from the ambiguous words you may find you use.


Ask So What, and do yourself a favour.


Thanks for reading.


Regards,

Greg


By Greg Wyatt • November 12, 2026
While 2027 remains surprisingly far away, with plenty of time to start applications, attend interviews, gain an acceptable job offer and even start work, I'm already thinking about the biannual update to A Career Breakdown Kit. Only, nothing's really changed in terms of what might affect the steps you take, overall, since the last update, so any changes are likely to only be minor. This might surprise you, if you feel that AI has increasingly eaten into how applications are administered and assessed. While the changes that are actually happening make the treatise of this article more important, which is to look at how recruitment actually happens in informing your strategy. Changes that may not be widespread but are emerging - deprioritising advertising roles in favor of sourcing (looking for candidates), because of the volume of applications; adding extra friction into applications, penalising relevant candidates because of AI applications made automatically; even discounting applications wholesale if they come from they are sent by a mass-apply service. I do see people regularly showcasing features of various ATSs over the years that seem to show automated rejections, yet these features rarely worked well, and haven't changed much in two decades. As I mentioned to Martyn, at a recent Recruitment Technology standards launch in the UK, "it doesn't matter how good the technology layer is, if the human layer is the problem". Martyn Redstone is Head of Responsible AI at Warden, and I'm fortunate that he will be joining me and Simon Ward on a LinkedIn Live as we discuss what this topic means for job seekers. I'll update this newsletter with the event when it's live. In the meanwhile, Martyn is well worth following to understand what's actually happening with AI in recruitment. It's still important to acknowledge the poor experiences job seekers have, and to try and shed light on what is happening, in what I call: 6 - De Facto Automated Rejection and You When there’s any discussion over Beat the Bots, job seekers often assume they are unfairly treated, while people from the recruitment profession deny it happens at all - “that’s not how the ATS works”, “we don’t use AI that way”, and so on. The best objection I see to the common recruiter stance is, “What does it matter how we are rejected, if we were never fairly considered?” That question is the heart of this chapter and, to answer it, I need to propose a new term: De facto automated rejection. Definition: where an element of a recruitment process leads to an application being either rejected or not considered, irrespective of capability, contribution, or potential alignment. That may sound an awful lot like Automated Rejection, yet it isn’t the same thing. Examples: No application after number 100 considered Illegal discrimination Legal discrimination - location, salary, industry, qualification, etc - legally permissible decisions driven by assumption Relying on configured ranking within an ATS to prioritise applications Not considering candidates who aren't picked up by a Boolean search (sourcing) Filter questions at advert stage (e.g. do you have a work permit?) Applying after the vacancy is at interview stage And many more All de facto automated rejections have one thing in common, and it isn’t automation - it’s human decision-making, including shortcuts and assumptions. Some of those examples above are cited when talking about auto-rejects. However, these are all consequences of human intervention and the choice not to intervene. There are an increasing number of AI products that automate these steps, with the requirement of human oversight - I've yet to speak to a recruiter that wholly relies on them, and few who don't view every application. This is one reason why ATS Compliance and Beat the Bots are a red herring. The advice fails not because it’s wrong, but because it optimises the wrong layer. The system is only a component in the process, governed by humans. If you misdiagnose de facto automated rejection as a technical problem, you’ll keep trying to outsmart systems instead of changing how you’re seen, found, and prioritised by people. Understanding how recruiters handle their process and giving them what they need in an application has to take priority. While the same steps that “optimise human compliance” are implicitly system-compliant. The challenge is that human compliance relies on what makes us individual: our skill level, our insight, our psychology, our biases, our resources and the time available to us. As well as how you navigate these. Without forgetting that we are people like you, often trying to do too much with too little. It’s no wonder our frustrations mirror yours, with the difference that we earn a salary for our experiences. ATS Compliance feels more comfortable, because it gives a clear direction, even if it’s the wrong one. It is true we use filters and keywords to prioritise how our applications are presented to us. We do the same when we look for candidates, whether on LinkedIn, job boards, our ATS or other means. All this does is present results in a way that allows us to spend more attention on those that meet the criteria we have set. When we review those results, the way that information is presented informs whether we progress them or not. To be human compliant, your application has to be discoverable, then it has to convert interest. Fail on either front and you’ll either be rejected or you won’t hear at all. If humans are the reasons you are rejected for reasons unrelated to capability or contribution... well, I think that’s rather more problematic than technology. Beat the Bots and ATS Compliance aren’t just a red herring - they can actively hold you back. Because they place the wrong priority by presenting a strategy, rather than simple hygiene. Your wider strategy should encompass far more than applications - getting found, starting conversations, doorknocking, networking and all these other opportunities that can get you closer to a job: These are fundamentally covered in a human compliance strategy. I just happened to call it A Career Breakdown Kit instead, with how to do these in Parts 2 and 3. I realise this may create a feeling of overwhelm, when you realise there is much more to a better application than the transactional steps of ATS compliance. Yet these same steps will improve every aspect of your job search and some are straightforward to take - go to www.bwrecruitment.co.uk/resources for the free CV template that is an easy starting point. 
By Greg Wyatt • November 11, 2026
I've written many variations on the article below, over the years, and it seems sensible to revisit given the UK government's announcements around salary transparency. On the whole, I'm for it, with the many advantages it brings. But like a lot of things in recruitment, there is a more involved discussion to be had, especially when this fix treats the symptoms, not the rot. That's not to say the fix isn't worth doing, just that it won't fix many of the problems underlying a lack of transparency. This article is a little dated, in terms of the research shared, but I think the points are as relevant as ever. Originally published May 2023 Salary on the Job Description? Yes, the headline is trolling. The question should be ‘salary on the job advert?’ You wouldn’t confuse a job description with an advert, would you? This is a subject rife with disagreement around ethics and practicality, and worth broaching again considering recent campaigns in the UK to increase salary transparency and ban the ‘what’s your current salary?’ question. Let’s focus on some practicalities first, based on UK research I ran last year for my “Accessing a Candidate Short Market” guide:  Job boards can penalise you for not listing salary. As of December 2021, Totaljobs penalises adverts that don’t list salary, and these aren’t sent out as job alerts to candidates (who may be passive). These adverts are considered sub-standard. Unlisted salaries attract fewer qualified applications. This was estimated to be between 20% and 45% fewer, across the job boards I talked to. LinkedIn reported that not only can you expect more applications, you may also expect better-qualified applications when the salary is advertised. My work supporting senior job seekers confirms this - many would not apply to adverts that had no salary or "competitive salary" because they felt this was a waste of their time. There is less emphasis on salary negotiation from the candidate side, due to transparency in pay. This is a key part of equity, relating to gender, race and intersectional identity. According to Payscale 's research, white men are most likely to negotiate the highest salary. It’s simple – if you advertise vacancies and don’t list salary, you risk receiving fewer, less suitable applications. Then there’s the ethical question, where a common argument is that there is ‘no ethical reason that salaries can’t be listed’. Now, while I’m a proponent for advertising salaries, where possible, I think this ethical argument isn’t the right one - ‘can’t be’ is a strong statement. I think a better question is ‘how does this do harm’ when establishing reasons for not listing salary. This balances pragmatism with the most important aspect of ethics. It can be a complicated question too in scenarios like this: How do you establish salary transparency for job families across multiple regions where the local pay is established by HQ in one country? Currency exchange rates and cost of living mean that a fair salary one day may not be the next, therefore flexibility in not listing salary may be ethically the right thing to do if the intent is right. What about new vacancies that serve to solve a business problem and can be recruited at different levels? What about practical situations like recruiting hard-to-fill vacancies during a wider redundancy programme, whereby listing a salary would create concern in unrelated areas of that unsettled business? It's not always as simple a question as we’d like to think. If you’re facing a complex situation in advertising a role, I recommend describing your stance in the advert itself, if you legitimately can’t state the salary. At the same time, as we’ve seen in the US, legislation to enforce salary transparency creates situations such as Netflix apparently advertising a range of $90-900k. Who does that help? The problem with this kind of legislation is that companies can comply while continuing the behaviour that led to the legislation in the first place. It’s palliative, rather than treating unfairness at its root. We should also consider the unforeseen consequence of salary transparency, such as this research which appears to show a reduced link between performance and pay: Influence of Pay Transparency Helping candidates negotiate better pay or terms is a privilege I enjoy. And there's more to understanding someone's existing remuneration than simply establishing whether they can afford to move. Sometimes these conversations reveal that someone is being underpaid. With evidence of what their experience and contribution might command elsewhere, they can go back to their current employer and make the case for a pay rise. That might mean they decide not to move at all. Which is a perfectly good outcome for them, even if it isn't for the vacancy in the short term. It also opens up the counteroffer conversation early. If their employer could resolve the reason they're considering leaving, I'd rather understand that before they accept an offer elsewhere. There's a benefit for prospective employers too. A new employer may budget £52,000 for a role, believing that to be market rate, based on historic data. But if conversations with suitably experienced candidates reveal that their existing remuneration, expectations and other opportunities consistently indicate otherwise, there's good reason to revise either the budget or the requirements. If that budget does prove unrealistic, and it's the same budget other team members are measured against, it can also create the argument to revisit everyone's salaries - subject to affordability, of course. After all, it's cheaper to retain fairly paid staff with all the knowledge they have than to replace them. Of course, conversations with candidates aren't a substitute for proper salary benchmarking. But they can reveal problems that wouldn't otherwise be apparent. There are also situations where understanding the whole package matters. What if someone currently receives a 16% pension contribution and moves to a role offering a 10% pay rise but only a 5% pension? Car allowances, RSUs, tax-efficient packages? Remuneration is a more involved conversation than simply salary. And none of this means someone's existing salary should determine what they're worth to their next employer. If their previous salary was unfair, using it to determine their next salary risks perpetuating that unfairness. And if an employer routinely offers a 15% increase on previous earnings, the new salary may have little relationship to the contribution that person can make. It makes sense to pay commensurately with contribution and capability, rather than what may be irrelevant history. So I understand the reasons for wanting to ban questions about previous salary. They're often used badly. But I think there's an important distinction between asking to establish someone's worth and asking to understand their circumstances. One can perpetuate unfairness. The other can help identify and correct it. If legislation restricts these conversations, I'll adapt how I offer this support. But I'd hope any restrictions recognise the difference between using salary history to determine an offer and voluntarily discussing remuneration to help someone make better decisions. I hope you’ve found these thoughts helpful to start a broader conversation in your business. My thoughts aren’t set in stone, so please let me know your opinions if you disagree. Thanks for reading. Regards, Greg p.s. While you are here, if you like the idea of improving how you recruit, lack capacity or need better candidates, and are curious how I can help, these are my services: Commercial, operational and technical leadership recruitment Manage part or all of your recruitment on an individually designed basis for one client Outplacement support Email me on greg.wyatt@bwrecruitment.co.uk if you'd like to discuss.