<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dixitkumar Jain on Medium]]></title>
        <description><![CDATA[Stories by Dixitkumar Jain on Medium]]></description>
        <link>https://medium.com/@jaindixitkumar?source=rss-50803771a321------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rRxa9uHTL8mF5KIkixrs4w.jpeg</url>
            <title>Stories by Dixitkumar Jain on Medium</title>
            <link>https://medium.com/@jaindixitkumar?source=rss-50803771a321------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:05:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaindixitkumar/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Verdict With No Trial: What AI-Detection Is Quietly Doing to Your Candidate Pipeline.]]></title>
            <link>https://medium.com/@jaindixitkumar/a-verdict-with-no-trial-what-ai-detection-is-quietly-doing-to-your-candidate-pipeline-31dd9a280089?source=rss-50803771a321------2</link>
            <guid isPermaLink="false">https://medium.com/p/31dd9a280089</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[recruitment-process]]></category>
            <dc:creator><![CDATA[Dixitkumar Jain]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 10:52:07 GMT</pubDate>
            <atom:updated>2026-06-03T11:14:57.144Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>An unproven AI-cheating accusation ended a process I had already passed. Thus, below are the points why every hiring leader should care and what it is costing you without your knowledge.</blockquote><p>Somewhere in your hiring pipeline right now, a qualified candidate may be getting quietly rejected, not for the skills gap, not for a bad reference, but on an assumption that they were “too good to be real.” No Evidence. No Hearing. No Appeal. Just a verdict, delivered and closed in the same breath. I know that because, <strong>that candidate was ME</strong>.</p><p>I cleared two genuine technical rounds for a senior role, the kind where you reason out loud and defend every choice. I expected the next conversation to be about the offer. <strong>Instead, an AI-suspicion flag I was never shown, never asked to answer, and never able to defend, ended everything.</strong></p><blockquote><strong>And the part that should worry you is not what it did to me, it is your own process that can do the exact same today and you would never know it happened.</strong></blockquote><p>I am telling this plainly, without naming anyone, because it isn’t really about one company. It is about a new failure mode that AI-detection has introduced into hiring, one that punishes the prepared, requires no proof, and gives the candidate no say. If you own a hiring process, this is the talent leak you cannot see on any dashboard.</p><p>What actually happened? I was interviewed for a senior position through one of the Big 4, who were hiring on behalf of their client. I cleared two technical rounds, the real ones, where I was asked to reason out loud and defend your choices. I expected the next conversation about the offer. Instead, I was told there would be a short round with the client directly.</p><p>That client conversation lasted about fifteen minutes. It wasn’t a deep grilling, but conversation ended with my notice period, my current location, when I could join. The interviewer kept a flat, unreadable expression the whole time, so I was genuinely unsure. Fifty-Fifty, I told myself.</p><p>Then within minutes, the recruiter called: I had cleared. Good news. A second call followed shortly after and this is where it turned. The client, as I was told, felt my answers had been <strong>“NEARLY PERFECT”. </strong>So perfect, infact they suspected I had used AI during the interview. A malpractice flag. On a call where no screen-share was ever requested, no recording was taken, and to be very clear, <strong>NO AI WAS USED.</strong></p><p>I had simply prepared. I have years of real experience in exactly the domain they were hiring for. Answering well wasn’t a trick; it was the entire point.</p><p>I said I was still happy to come in, to do another round in person (which they gave me an option on the second call), to justify in every setting they preferred. The reply, after some back-and-forth, was that the client did not want to take my application further. Not because of a skills gap. Not because of a bad reference. Complete because of an <strong>ASSUMPTION </strong>of being too good to be REAL.</p><h3><strong>Three things about this should worry every hiring team</strong></h3><p><strong>First, preparation is being read as guilt. </strong>The candidates most likely to trigger a “too perfect” suspicion are precisely the ones who studied the company, rehearsed their stories, and know their craft cold. <strong><em>If excellence is now a RED FLAG, we are building a filter that selects against the people we claim to want.</em></strong></p><p><strong>Second, the accusation required an evidence. </strong>There was no artifact: no recording, no flagged tool, no detection report. <strong>“YOU ANSWERED TOO WELL”</strong> is not an evidence; it is an impression.</p><p><strong>Third, there was no way to respond.</strong> I asked, in as measured a way as I could, whether the candidate has any say after an allegation like this. The honest answer was no. There was no appeal, no re-test, no conversation in which I could clear it up. A serious charge, effectively and dishonesty, was made and closed in the same breath.</p><p>Put those together and you get a system with a verdict but no trial. That should make anyone who cares about fair hiring uncomfortable, regardless of which side of the table they sit on.</p><h3>In fairness to the interviewers</h3><p>I don’t think anyone acted with malice, and I want to say that clearly. AI anxiety in interviews is real. Tools that let candidates feed questions to a model in real time genuinely exist, and they are a legitimate concern. Interviewers are under pressure to protect their clients, and detecting this stuff is genuinely hard. I understand the instinct.</p><p>But, “hard to detect” cannot quietly become “assume guilt”. The cost of that shortcut isn’t borne by the company, it is borne by the candidate, who walks away with a rejection and, worse, an unspoken question mark on their integrity they never had a chance to answer.</p><h3>What good process would look like?</h3><p>The fix is not expensive. If a candidate’s answers seem suspiciously strong, the fair response isn’t to quietly drop them, it’s to verify.</p><p>→ Offer a short live, camera-on, screen-shared follow-up.</p><p>→ Ask them to whiteboard a problem in real time.</p><p>→ Probe deeper on very answers that raised the flag.</p><p>A genuinely prepared candidate will sail through it, while someone who as cheating, won’t. <strong><em>Either way, you reach the truth instead of a GUESS.</em></strong></p><p>That single step, a chance to respond, costs a company one conversation. What it saves is the talent you would otherwise loose on a hunch, and never even know you lost.</p><h3>Where I have landed?</h3><p><strong><em>I am not writing this to win one rejection back. </em></strong>I am writing it because I suspect I am not the last person this will happen to, and because the people who can fix it, hiring leaders, talent teams. The firms that run these loops may not realize it’s happening.</p><p>If you build or run a hiring processes: <strong><em>please add a step where an accused candidate can respond. Due process isn’t a courtesy. It’s how you make sure your filter is catching cheaters and not just confident, well-prepared professionals.</em></strong></p><p><strong>AND ON A PERSONAL NOTE: </strong>I am a Cyber Security and IT Controls specialist with over five years of experience across Penetration Testing, VAPT, SOC, GRC, IAM, SOX and ISO 27001 and I am open to new roles. If you are building a team that rewards preparation rather than suspecting it, I would genuinely like to connect and talk.</p><p>Let’s Connect: <a href="https://www.linkedin.com/in/dixit-jain-0604"><strong><em>https://www.linkedin.com/in/dixit-jain-0604</em></strong></a></p><p>Website: <a href="https://raj.businesscontact.uk/"><strong><em>https://raj.businesscontact.uk</em></strong></a></p><p>Email: <a href="/service/mailto:jaindixitkumar@gmail.com"><strong><em>jaindixitkumar@gmail.com</em></strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N7Y7V_mfWt_gNgjndDB0jA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*icoNMGTTVPi-HHSKU09cfw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4DZqhMhSQyZmFz2isco8Q.jpeg" /><figcaption>Real screenshots (contains hidden details)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31dd9a280089" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>