a software engineering interview question I like: computing the median
Summary
The author describes their favorite software engineering interview question: computing the median of an array. They discuss the various angles it offers for evaluating candidates' programming skills, including sorting, edge cases, API design, and statistical understanding.
View Cached Full Text
Cached at: 07/08/26, 04:24 AM
Similar Articles
jwasham/coding-interview-university
A comprehensive, multi-month study plan for software engineering interviews at major tech companies, originally created by John Washam and widely adopted by the developer community.
The four programming questions from my 1994 Microsoft internship interview (2023)
A retrospective blog post from 2023 recounts the four programming questions the author faced during a Microsoft internship interview in 1994, sharing the problems and context.
@vintcessun: Came across an interesting project this morning that changed my perspective on interview prep. I used to think that grinding LeetCode was enough for big tech interviews, but in essence, they test your complete understanding of computer science. This project strings together discrete knowledge points into a systematic study plan, covering everything from Big-O, data structures, algorithms to system design and interview tips, even including how to write a resume.
A popular GitHub project providing a comprehensive multi-month study plan for software engineering interviews, covering CS fundamentals, algorithms, system design, and resume tips.
@freeman1266: In AI-coding interviews, my favorite question is: What makes a prompt truly great?
The author shares the one question he loves to ask most when interviewing for AI-coding roles: what defines an excellent prompt.
@GergelyOrosz: Pretty amusing that Hillel Wayne was sceptical if software engineering is "real" engineering, so interviewed "real" eng…
Gergely Orosz comments on Hillel Wayne's interviews with engineers from other fields, who were surprised to learn about version control — a practice software engineers take for granted.