Jump to content

Coding interview

From Wikipedia, the free encyclopedia

A coding interview, technical interview, programming interview or Microsoft interview is a technical problem-based job interview technique to assess applicants for a computer programming or software development position. Modern coding interview techniques were pioneered by Microsoft during the 1990s[1] and adopted by other large technology companies including Amazon, Facebook, and Google.[2][3] Coding interviews test candidates' technical knowledge, coding ability, problem solving skills, and creativity, typically on a whiteboard. Candidates usually have a degree in computer science, information science, computer engineering or electrical engineering, and are asked to solve programming problems, algorithms, or puzzles.[4][5] Coding interviews are typically conducted in-person or virtually.

Innovation

[edit]

Microsoft's interview style was distinctive in that it concerned technical knowledge, problem solving and creativity as opposed to the goal and weaknesses interviews most companies used at the time. Initially based on Bill Gates's obsession with puzzles, many of the puzzles presented during interviews started off being Fermi problems, or sometimes logic problems, and have eventually transitioned over the years into questions relevant to programming.[6] As William Poundstone wrote, "Puzzles test competitive edge as well as intelligence. Like business or football, a logic puzzle divides the world into winners and losers. You either get the answer, or you don't. … Winning has to matter."[6]: 62 

Questions

[edit]

The questions asked during a coding interview are crafted to determine a candidate's problem solving, coding and design abilities. Eccentric questions (such as "Which of the fifty states would you remove?") test a candidate's ability to come to a decision and articulate it.[6]: 67  Candidates answering questions should consider the use of technology in the present and future, and user scenarios. Some questions involve projects that the candidate has worked on in the past.

A coding interview is intended to seek out creative thinkers and those who can adapt their solutions to rapidly changing and dynamic scenarios.[citation needed]

Typical questions that a candidate might be asked to answer during the second-round interview include:[7]

  • Design a GPS navigation unit for a hiker.
  • Design a communication device for Canadian park rangers.
  • Shift all elements of a circular array by k bytes, using no extra memory.

Manhole test

[edit]

Microsoft popularized the question of why manhole covers are typically round (in some countries) when they began asking it as a job interview question.[6] Originally meant as a psychological assessment of how one approaches a question with more than one correct answer, the problem has produced a number of alternative explanations, from the tautological ("Manhole covers are round because manholes are round.")[6] to the philosophical.

By 2012, the practice of asking lateral thinking questions had declined at companies including Microsoft and Google. A study by San Francisco State University associate professor of psychology Chris Wright found that puzzle interview questions annoyed job applicants. "Methods that had a transparent relationship between test content and job duties, such as interviews, work samples, and reference checks were perceived more favorably," Wright wrote in a research paper entitled "Why Are Manhole Covers Round? A Laboratory Study of Reactions to Puzzle Interviews". Poundstone, who had written puzzle interview guides for Microsoft and Google, referred to puzzle questions in 2012 as "a sort of fad" that lost popularity because of a lack of evidence of their effectiveness.[1]

References

[edit]
  1. ^ a b White, Martha C. (October 23, 2012). "No-Brainer: 'Brainteaser' Job Interview Questions Don't Work". Time. Retrieved July 4, 2022.
  2. ^ Applicants blog after Google interview. Archived March 13, 2011, at the Wayback Machine
  3. ^ Job Interviews Get Creative, NPR 2003. Retrieved from the World Wide Web on January 16, 2006.
  4. ^ John Mongan (December 11, 2023), Programming Interviews Exposed: Secrets to Landing Your Next Job (2nd ed.), Wrox, ISBN 978-0-470-12167-2
  5. ^ McDowell, Gayle Laakmann (2015). Cracking the coding interview : 189 programming questions and solutions (6th ed.). Palo Alto, CA. ISBN 978-0-9847828-5-7. OCLC 913477191.{{cite book}}: CS1 maint: location missing publisher (link)
  6. ^ a b c d e Poundstone, William (2003). How Would You Move Mount Fuji. Boston: Little, Brown and Company. pp. 50–90. ISBN 0-316-91916-0.
  7. ^ "Typical Coding Interview Questions". OmniJobs. September 4, 2024.