Post by Alex K.

Day 3 of spotting scammers during interviews and some thoughts on how to get ahead of them. At this point, I feel like I could write a small book on this. Three days in, and the patterns are becoming very clear. Here’s what I’ve noticed so far They adapt, fast. very fast. Are they reading my posts? Nah, I don’t think so… but it feels like it sometimes. Fake/scam candidates are learning to sound more “human.” They tweak their speech patterns, pause intentionally, and even mimic casual tone. Some have surprisingly good small talk until you ask a real question about how they actually built something. That’s where it all falls apart. The camera test still works, but it’s not enough. Today I focused on asking for examples, not definitions. Instead of: “Tell me about your experience with React Native,” I asked:“Tell me about the hardest issue you fixed in a production mobile app, what was the impact?” Two of them completely crumbled once the answer wasn’t pre-written by Chat or another AI tool. Learnings from today: For recruiters & founders: Add a “context switch test.” Mid-answer, gently change the topic, for example: “Wait, what framework did you say you used again?” If the story falls apart, they’re probably reading or parroting. Real candidates can pivot naturally. The fakes? They drop like flies. For candidates: Just be authentic and be prepared. Don’t memorise your CV. Own it. You know what you’ve done, what you’ve achieved, and what you’re proud of. Write down 2–3 real stories that showcase what you’ve built, what you learned, and what you’d do differently next time. When asked, “What impact have you made?” don’t give a one-sentence answer. Even if your role didn’t have huge scope, talk about how you were proactive, solved a problem, or helped your team. Volunteering, side projects, mentoring, they all count. Genuine experience doesn’t need a script. I’m continuing this as a mini-series “How to Spot the Fakes and How the Real Ones Can Stand Out.” Would you read Part 4?