✳flâneur — a map of the web's best reading
@chrlschn - Interviews in the Age of AI: Ditch Leetcode - Try Code Reviews Instead
chrlschn.dev · 2,070 words · saved by 1 readers
In the emerging age of AI generated code, is leetcode really the best way to evaluate technical candidates (was it ever)?
Interviews in the Age of AI: Ditch Leetcode - Try Code Reviews Instead Jul 31, 2023 Intro A Medium story first popped in to my feed last year and it got me thinking about the state of how the tech industry interviews and evaluates candidates. https://medium.com/the-coding-diaries/why-experienced-programmers-fail-coding-interviews-b22210ba343 Recently, a friend shared with me his plans to take some time off to study for common leetcode problems to practice as he was planning his applications for FAANG companies. Is that really what one wants to select for when hiring for a new member of an engi
Explore this link on the map →related reading
- How We Hire Engineers When AI Writes Our Code | Tolans.comtolans.com
- If you are good at code review, you will be good at using AI agentsseangoedecke.com
- Using AI to write better code more slowly | Read the Tea Leavesnolanlawson.com
- Best practices for Claude Code - Claude Code Docsanthropic.com
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- HackerEarth | AI Powered Interviews and Assessmenthackerearth.com
- I built an AI code review agent in a few hours, here's what I learnedsourcebot.dev
- Introducing FrontierCode | Cognitioncognition.ai
- My AI Had Already Fixed the Code Before I Saw Itevery.to
- [2203.07814] Competition-Level Code Generation with AlphaCodearxiv.org
- Ask HN: What is a better approach to interviewing? | Hacker Newsnews.ycombinator.com
- [2501.01257] CodeElo: Benchmarking Competition-level Code Generation of LLMs with Human-comparable Elo Ratingsarxiv.org