↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Finding awesome developers in programming interviews

The post says a strong programming interview should first check what on the resume is actually true, then look for real experience, and finally verify skills with targeted questions and a coding task. It warns that a resume can mislead, and that interviewers should not assume anything without testing it.

It also argues that not all experience has the same value. Personal projects, early programming history, work on small teams, and detailed knowledge of a system can all show more depth. The coding question should match the job, be precisely worded, and be followed by a verbal outline so the interviewer can see whether the candidate is on the right track.

Reading notes
#

  • An interview should begin by checking the concrete claims on the resume.
  • Experience matters, but long tenure alone does not prove depth.
  • Personal projects can indicate more flight time and broader practice.
  • Interviewers should ask about early programming history and the reason someone entered software development.
  • Smaller teams, varied projects, and main-contributor roles can signal denser experience.
  • The interviewer should test several areas of software knowledge, including data structures, multithreading, memory allocation, recursion, and compilation.
  • Basic questions and follow-up questions help show whether knowledge is genuine.
  • The coding question should fit the job and avoid ambiguity.
  • A verbal outline after a few minutes helps confirm whether the candidate understands the problem.
  • The method is based on probability and hypothesis, not perfect certainty.