# technical-interview Published articles for technical-interview. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Strange Theatre of Technical Hiring DevFeed: [The Strange Theatre of Technical Hiring]() Original publisher: [Read original article]() Author: Daniel Glejzner Published: 2026-06-18T18:15:04Z Content type: opinion Language: en Sources: [Daniel Glejzner]() Topics: [engineering-leadership](), [Software Engineering](), [Code Challenge](), [Development]() Tags: [challenges](), [coding](), [developers](), [engineering](), [engineering-leadership](), [hiring](), [interview](), [software](), [software-engineering](), [technical](), [technical-interview]() ### AI overview The article argues that technical hiring often evaluates experienced engineers through narrow, timed coding exercises that may reward speed, recall, confidence under pressure, and familiarity with interview rituals more than the judgment and contextual skills required in software engineering work. ### Source excerpt A senior engineer joins a technical interview... Hi Angular Space community :) It's been a while since I pushed myself to write something. AI is changing the way we consume literally everything online, and I'm still trying to figure out what the best and most compelling way ## How AI Is Changing Coding Interviews in 2026 DevFeed: [How AI Is Changing Coding Interviews in 2026]() Original publisher: [Read original article]() Author: Brian Jenney Published: 2026-04-28T16:21:33Z Content type: opinion Language: en Sources: [Brian Jenney]() Topics: [coding](), [AI Engineering](), [Artificial Intelligence](), [HackerRank](), [LeetCode]() Tags: [2026](), [ai](), [career](), [coding](), [interviews](), [software-engineer](), [technical-interview]() ### AI overview This opinion article argues that coding interviews in 2026 remain disconnected from day-to-day software work, while AI has changed how developers write code. It describes traditional data-structures-and-algorithms assessments and other interview formats developers may encounter. ### Source excerpt Coding interviews have been notoriously tone deaf for years. ## Practical Kotlin Deep Dive: A Book and Course on Kotlin Internals DevFeed: [Practical Kotlin Deep Dive: A Book and Course on Kotlin Internals]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2026-02-18T03:55:53Z Content type: article Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [Kotlin](), [Compiler](), [Code](), [Development]() Tags: [analysis](), [android](), [bytecode](), [compiler](), [internals](), [kotlin](), [kotlin-coroutines](), [programming](), [technical](), [technical-interview]() ### AI overview This article introduces Practical Kotlin Deep Dive, a book and companion course focused on Kotlin internals. It describes coverage of bytecode decompilations, compiler source code, KEEP proposals, code examples, Code Playgrounds, and quiz questions across six chapters. ### Source excerpt Most Kotlin developers can write a data class, launch a coroutine, or use lazy without thinking twice. These features work, the code compiles, and the app runs. But there is a gap between knowing how to use Kotlin and understanding what the compiler actually does with your code. That gap is where performance intuition, debugging skill, and technical interview confidence come from. Practical Kotlin Deep Dive is a book designed to close that gap, covering 70 Kotlin topics across 492 pages with bytecode decompilations, compiler source code references, and KEEP proposal analysis that reveal the machinery behind every feature you use daily. In this article, you'll explore what the book and its companion course cover, walking through each of the six chapters with examples of the insights you'll find inside. You'll see how the book approaches topics differently from typical Kotlin resources, what the "Pro Tips for Mastery" sections reveal about internal mechanisms, and how the interactive course format turns that knowledge into verified understanding through Code Playgrounds and 158 quiz questions. Beyond the syntax: Why internals matter Knowing that lazy caches a value on first access is useful. Knowing that the default lazy implementation uses double checked locking with a synchronized block, and that you can switch to a lock free compareAndSet strategy by passing LazyThreadSafetyMode.PUBLICATION, is the difference between using a feature and making informed decisions about it. The same applies across the language. Understanding that every lambda passed to a higher order function creates a Function object on the heap explains why inline exists. Seeing a data class decompiled into seven generated methods explains what the compiler is doing on your behalf. This is the approach Practical Kotlin Deep Dive takes throughout. Rather than describing what Kotlin features do, it examines how they work internally, what bytecode they produce, what design trade-offs the language desi ## The right way to interview DevFeed: [The right way to interview]() Original publisher: [Read original article]() Published: 2025-05-27T00:00:00Z Content type: opinion Language: en Sources: [Gaurav Sarma's Blog]() Topics: [bug](), [Job]() Tags: [bias](), [bug](), [career](), [experience](), [hiring](), [interview](), [pair](), [technical-interview]() ### AI overview The article argues that technical interviews should primarily use bug-squashing or pair-programming exercises, allowing interviewers to observe how candidates reason, respond to mistakes, challenge hypotheses, and work in practice. It also notes that these interviews require more preparation and may introduce subjective judgment and interviewer bias, while data-structures-and-algorithms questions can provide a more objective signal. ### Source excerpt Original Tweet - https://x. com/sarmag77/status/1938429909338362348 The best kind of interview is the bug squash or pair programmer round where both the interviewer and the candidate team up to solve a common problem... ## Rethinking Technical Interviews for Virtual Hiring and AI-Assisted Candidates DevFeed: [Rethinking Technical Interviews for Virtual Hiring and AI-Assisted Candidates]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-04-17T19:08:54Z Content type: opinion Language: en Sources: [Anna J McDougall]() Topics: [Tech Careers](), [Artificial Intelligence](), [LeetCode](), [Algorithms]() Tags: [ai](), [algorithms](), [artificial-intelligence](), [careers](), [chatgpt](), [engineering-management](), [interview](), [interviewing](), [software-development](), [technical-interview](), [technology]() ### AI overview This opinion article argues that virtual hiring and AI tools have exposed weaknesses in traditional technical interviews. It discusses limitations and equity concerns associated with algorithm assessments and take-home projects, and introduces the McDougall Method at HelloBetter as a proposed response. ### Source excerpt Building the McDougall Method at HelloBetter: A Fairer, More Modern Approach to Technical Interviews As someone obsessed with tech careers, business growth, and engineering management, I am constantly coming up against the boogey-man of technical interviews. In many ways, tech companies are stuck in the thinking of 20-30 years ago: white boards, algorithms, logic puzzles, and tasks that rotated around an in-person interview space. We're in a new era, where 99% of engineering interviews are done virtually and the candidate's workspace is uncontrollable by the interviewing team. We need to adapt to this, not by simply porting previous methods across to an online platform, but by fundamentally rethinking the skills we expect 21st century software engineers to have. Naturally, opinions about what is wrong with technical interviews are prevalent both from employers and (potential) employees. For example, leetcode-style assessments have long been derided as being a bad test of abilities. "Instead," opponents argue, "you should use take-home tests or projects that the candidate can explain back to you". Ah, but you see, not everyone can afford to let their evenings and weekends disappear into these take-home tests or side projects. Due to this inconveniently linear construct called "time", more experienced engineers start having or caring for families, adopting pets, or (lord forbid) doing sports and hobbies. It's also no big secret that the majority of housework and care duties still tend to be shouldered by women. To put your best foot forward as a candidate, you will create the best possible solution, no matter how many hiring managers tell you to "only spend 2-3 hours on a solution". Therefore, take-home or "own project" technical interviews tend to put older candidates and women candidates at a disadvantage. One other problem popping up nowadays is the prevalence of AI tools for engineers to pass technical interviews, ranging from manually entering prompts into ChatGP ## Algorithm-focused technical interviews can overlook application development skills DevFeed: [Algorithm-focused technical interviews can overlook application development skills]() Original publisher: [Read original article]() Author: Mike Published: 2023-07-08T20:12:06Z Content type: opinion Language: en Sources: [Dev Details]() Topics: [Programming](), [Application Development](), [LeetCode](), [Algorithms, Complexity](), [Data structures](), [Development]() Tags: [algorithms](), [challenges](), [complexity](), [interview](), [interviews](), [order](), [technical-interview](), [time]() ### AI overview This opinion article argues that LeetCode-style algorithm interviews can produce false signals because they assess algorithm problem solving and Big-O analysis while overlooking the broader skills needed for application development. It suggests that developing applications is the way to build those skills. ### Source excerpt Interviews that focus on algorithms get false signals and overlook qualified candidates ## In Defense of the Take-Home Coding Challenge DevFeed: [In Defense of the Take-Home Coding Challenge]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2022-01-28T13:02:14Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Code Challenge](), [coding](), [Testing]() Tags: [coding](), [developers](), [technical-interview](), [test]() ### AI overview This commentary examines the role of take-home coding challenges in developer hiring. It argues that, despite concerns about candidate burden and lengthy hiring processes, standardized challenges can provide relevant and comparable work samples, while automated testing tools may lack nuance. ### Source excerpt In defense of the take-home coding challenge ## The Jane Street Interview Process -- 2020 Edition DevFeed: [The Jane Street Interview Process -- 2020 Edition]() Original publisher: [Read original article]() Author: Sam DeFabbia-Kane Published: 2020-07-24T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [Software Engineering](), [coding](), [Algorithms](), [Simulation]() Tags: [algorithms](), [coding](), [covid-19](), [interview](), [interviewing](), [technical-interview]() ### AI overview Jane Street describes its 2020 software engineering interview process for interns, new graduates, and experienced candidates. The process generally includes a technical phone interview and an onsite interview with two to four technical rounds, conducted by video conference during COVID-19. Technical interviews focus on coding and algorithms problems, communication, and collaborative problem-solving. ### Source excerpt We're busy preparing for our software engineering fall hiring season. Over the years we've done our best to make our interview process more transparent to candidates. While many candidates show up knowing something about what our interviews look like, much of the information floating around on the internet is outdated or wrong. These past few months have also changed a lot about the process as we've adapted to working from home and other effects of COVID-19. ## Technical Interview Reform, Part 1: Rethinking the Backend Engineering Interview Take-Home Challenge DevFeed: [Technical Interview Reform, Part 1: Rethinking the Backend Engineering Interview Take-Home Challenge]() Original publisher: [Read original article]() Published: 2020-06-25T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Back end](), [Code](), [coding]() Tags: [backend](), [code-challenge](), [engineering](), [hiring](), [interviewing](), [process](), [technical](), [technical-interview]() ### AI overview SoundCloud explains why it comprehensively rethought its backend engineering take-home challenge. The previous coding exercise often required many hours over several weeks, creating a burden for candidates and causing a significant dropoff in the hiring pipeline. The revised approach is framed as a code tryout intended to assess an essential engineering skill while reducing time costs and limiting bias through an anonymous audition. ### Source excerpt Most SoundCloud backend engineers have good feelings about the old backend engineering take-home challenge. It's commonly been characterized...