问HN：在Claude/ChatGPT时代，你们是如何进行技术面试的？
我是一个创始人/开发者，正在寻找更好的技术面试方式，因为目前的状态简直是一场噩梦。
现在，每个标准的带回家作业或HackerRank/LeetCode测试都很容易被大型语言模型（LLMs）解决。因此，公司不小心雇佣了我们称之为“氛围编码者”的候选人，他们在引导AI生成模板代码方面表现出色，但在架构复杂、出现故障或AI微妙地产生幻觉时完全失去反应。
我们正在研究一种新方法，我想与实际进行这些面试的人验证一下工程逻辑。
我们不想试图禁止AI（这是一场注定要失败的战斗），而是希望测试“AI引导”。
我们的想法是：
1. 将候选人放入一个真实且稍显混乱的沙盒代码库中。
2. 让他们使用任何他们想要的AI。
3. 注入一个微妙的架构变化、一个破坏性的依赖关系或一个AI幻觉。
4. 通过遥测（Git差异、CI/CD运行、调试路径）纯粹测量他们如何恢复并修复混乱。
基本上：停止测试语法，开始在AI时代测试架构和调试技能。
在我们花几个月时间构建这个模拟的后端之前，我需要来自经验丰富的领导者的现实检查：
1. 测试候选人“引导”和调试AI生成代码的能力，对你来说是否比传统算法更有意义？
2. 你目前是如何防止这些“仅会提示”的开发者在自己的面试环节中溜走的？
（这里不链接任何内容，因为还没有东西可以出售，只是希望得到对方法论的严厉反馈。）
查看原文
I’m a founder/dev trying to figure out a better way to do technical interviews, because the current state is a nightmare.<p>Right now, every standard take-home or HackerRank/LeetCode test is easily solved by LLMs. As a result, companies are accidentally hiring what we call vibe coders, candidates who are phenomenal at prompting AI to generate boilerplate, but who completely freeze when the architecture gets complex, when things break, or when the AI subtly hallucinates.<p>We are working on a new approach and I want to validate the engineering logic with the people who actually conduct these interviews.<p>Instead of trying to ban AI (which is a losing battle), we want to test for "AI Steering".<p>The idea:
1. Drop the candidate into a real, somewhat messy sandbox codebase.<p>2. Let them use whatever AI they want.<p>3. Inject a subtle architectural shift, a breaking dependency, or an AI hallucination.<p>4. Measure purely through telemetry (Git diffs, CI/CD runs, debugging paths) how they recover and fix the chaos.<p>Basically: Stop testing syntax, start testing architecture and debugging skills in the age of AI.<p>Before we spend months building out the backend for this simulation, I need a reality check from experienced leads:
1. Does testing a candidate's ability to "steer" and debug AI-generated code make more sense to you than traditional algorithms?<p>2. How are you currently preventing these "prompt-only" developers from slipping through your own interview loops?<p>(Not linking anything here because there's nothing to sell yet, just looking for brutal feedback on the methodology.)