Find all the best dev content at https://daily.dev/fireship

With the rise of remote work and AI, the tech world has also seen a rise in cheating on the software engineering technical interview. Let's look into modern techniques people use to cheat during coding interviews and the consequences of when you get caught. 

#programming #tech #thecodereport 

💬 Chat with Me on Discord

https://discord.gg/fireship

🔗 Resources

Caught Cheating with Claude https://twitter.com/TheGregYang/status/1843129139366437109
Interview Cheating Test https://interviewing.io/blog/how-hard-is-it-to-cheat-with-chatgpt-in-technical-interviews
How to not fail the technical interview https://youtu.be/1t1_a1BZ04o
Claude AI Updates https://youtu.be/DVRg0daTads?si=R7je4fG03JXZZzA7

🔥 Get More Content - Upgrade to PRO

Upgrade at https://fireship.io/pro
Use code YT25 for 25% off PRO access 

🎨 My Editor Settings

- Atom One Dark 
- vscode-icons
- Fira Code Font

🔖 Topics Covered

- How do people cheat on technical interviews?
- Trends in the tech job markets
- Tips for swe interviews
- How to pass software technical interview
- What happens if you cheat on technical interview?

Fireship is a YouTube channel created by Jeff Delaney that offers quick tutorials and explanations on web development, programming, and tech trends. Known for the “100 Seconds of Code” and “The Code Report” series, the channel breaks down complex topics in a short, engaging format, covering everything from JavaScript frameworks to emerging technologies.

Fireship

The post discusses the rise of cheating in technical interviews, driven by remote work and advanced AI tools. It outlines various cheating techniques, such as using hidden laptops, leaked interview questions, and AI tools like ChatGPT. The potential consequences of cheating, including rejection, being blacklisted, and damaging one's professional reputation, are highlighted. The post emphasizes the importance of honesty and the risks involved in cheating.

Cheaters are breaking the technical interview... how?

Do people really do this? Aren’t they afraid they’ll get hired for a job they can’t do? I’m sure no one here would even consider it… 😜

Goodhart’s law strikes again! (When a measure becomes a target, it ceases to be a good measure)

I discovered daily.dev from watching this video a minute ago 😅

Good developers always cheat the system. That is why they are good developers, to bypass any restrictions that is put upon them.
Long time ago calculators was cheating, later looking up code at Stack Overflow was cheating, code completion was regarded as cheating.
Sometimes a solution why a project is broken, is to bypass all guides and rules, to put a solution in place that can carry the weight of the code and over time clean up the mess. Years of broken projects fixed in just a few days fix.

I can see this being a really helpful tool to maybe wake some people up! The questions asking in interviews are dumb and things you have to study for but never really do in a real project. So I don’t blame them for using a tool like this the interview process is very broken. I never used it but as a engineer of 25 years I know I can build almost anything in most modern languages today. Sure It might take me a few weeks to learn your language and libraries but the actually work would be easy. So using this to pass a interview would be a huge help. If it was wrong it would get me close enough for sure and being a engineer for so many years I could easily explain as I go. I see it as a way to fight back from companies that think they need to interview like this to get good engineers. Good for them. There are much better ways to interview people. Also why do you need to verify I can write code? I been doing it for 25 years with multiple 4-5 year stents with even a 11 year stent at a company. You are just wasting everyone time interviewing like this. If I had a say on how we interview I would let people use these tools, they are going to have them at the job as well! Then we can stop focusing on you missed a semi colon or I know some obscure thing about this language that you don’t and ask the question can this person build stuff that will help our customers and are they a good fit for our team.