Offered

No more context needed beside what title says really, at first thought to build a voice agent to conduct the interview on my behalf, just for fun, still might do something like that in the future. " Might as well have my AI agent write a reply on why I am not keen to an AI interview, apologies team :) Hello X X team, Thank you for moving me forward for the x x role. I value x mission — which is why I want to be direct: I will not complete the AI interview and would like to proceed via a human-led alternative. I’m sharing my reasons in detail because they also reflect how I evaluate the culture of a company I may join. 1) Culture signal & resourcing Requiring an AI to conduct the first real “conversation” signals that the company either lacks the resources or the willingness to meet candidates live. That may be efficient, but it sets an expectation about day-to-day reality: if we can’t spare 15–20 minutes for a person-to-person chat at the outset, what does that say about how people are prioritised internally? 2) Job security & intent Using an AI gatekeeper for a role defined by nuance, trust, and human judgment telegraphs a clear message to candidates: the moment you can swap a human for a tool, you probably will. I’m looking for an environment where human-led onboarding and relationship-building aren’t treated as “nice-to-haves” that can be automated away. This is about job security but also about principle: onboarding isn’t just tasks; it’s trust, context, and empathy. 3) Dehumanisation & experience quality One-way, model-scored interviews optimise for data capture, not dialogue. They strip away clarifying questions, rapport, and the ability to co-reason through problems — exactly the behaviours that matter in onboarding operations. Reducing a candidate’s story to token streams and confidence scores is dehumanising and, frankly, the opposite of how I operate and what I’m actively moving away from in my career. 4) Signal vs. noise (fairness and accuracy) LLM/STT pipelines still struggle with accents, pacing, neurodivergent communication, network latency, and room acoustics. Without a two-way conversation, small misreads snowball into poor assessments. If a candidate needs to challenge a premise or ask for context, the AI cannot interpret that as collaboration; it often penalises it. That’s not a fair signal for a role that requires collaborative problem-solving across time zones and cultures. 5) Privacy, consent, and retention I’m cautious about voice and biometric data being stored, processed by third parties, and potentially reused to train future systems. I don’t know where the data lives, who exactly has access, or how long it’s retained — and I’m not comfortable handing over that risk for an interview step when a simple conversation or written Q&A would suffice. 6) Efficiency isn’t the same as effectiveness A 30-minute, one-way AI interview is not more effective than a 15–20 minute human conversation, a short case prompt, or a written Q&A. It generates “data exhaust,” but not necessarily better hiring decisions. For a role that’s measured on time-to-value, first-week outcomes, and stakeholder satisfaction, a short human exchange is the more predictive, respectful tool. 7) Candidate experience as a proxy for employee experience First impressions matter. If the hiring experience is impersonal by design, it’s reasonable to infer the employee experience tilts similarly — prioritising data collection over human touch. That’s exactly what I’m intentionally moving away from. If the AI interview is a mandatory gate, I’ll respectfully withdraw my application at this stage. If there’s flexibility, I’m keen to proceed — I believe my background in onboarding operations, process design, and cross-border enablement would be a strong fit, and I’m happy to demonstrate that through any other alternatives. Thank you for understanding, and I look forward to your reply. Kind regards, GPT 5 trained by x "