<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>interviews · Nearbycoder</title><link>https://nearbycoder.com/topics/interviews/</link><description>Published stories about interviews.</description><language>en-us</language><atom:link href="https://nearbycoder.com/feeds/interviews.xml" rel="self" type="application/rss+xml"/><item><title>When AI in an interview fails you</title><description>I used AI heavily in a technical interview, felt great about the build, and still got rejected because the team could not gauge enough of my understanding.</description><link>https://nearbycoder.com/articles/when-ai-in-an-interview-fails-you/</link><guid isPermaLink="true">https://nearbycoder.com/articles/when-ai-in-an-interview-fails-you/</guid><pubDate>Sat, 07 Mar 2026 00:00:00 GMT</pubDate></item><item><title>The 6-hour build and why technical interviewing needs to change</title><description>Building TripHaven in about six hours made one thing clear: interviews should test end-to-end product replication and engineering judgment, not isolated feature trivia.</description><link>https://nearbycoder.com/articles/the-6-hour-build-and-why-technical-interviewing-needs-to-change/</link><guid isPermaLink="true">https://nearbycoder.com/articles/the-6-hour-build-and-why-technical-interviewing-needs-to-change/</guid><pubDate>Mon, 02 Mar 2026 00:00:00 GMT</pubDate></item><item><title>My first technical interview in the AI era</title><description>I walked out of my first technical interview feeling off, and it forced me to rethink interview formats, AI, and pressure.</description><link>https://nearbycoder.com/articles/my-first-technical-interview-in-the-ai-era/</link><guid isPermaLink="true">https://nearbycoder.com/articles/my-first-technical-interview-in-the-ai-era/</guid><pubDate>Thu, 26 Feb 2026 00:00:00 GMT</pubDate></item></channel></rss>