Skip to content

tedder/interview-code-tests

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Code tests for interviewing software engineering candidates

This is the start of a repository for coding test problems that can be given to software engineering candidates.

Undocumented/half-baked ideas

  • Some sort of problem that is already in a framework but needs modification to add features. More accuriately resembles real-world.
  • Code that checks this repository for licensing information.

Frequently asked questions

Feel free to ask questions or edit answers to the following.

Why use take-home code problems?

Take-home problems are a low-pressure way to see if a candidate can actually write code. It's amazing how many interview candidates aren't capable of writing code. It's also amazing how many companies expect candidates to solve complex problems on a whiteboard without access to a search engine, documentation, and other common software resources.

While these problems are typically limited in scope, they not only show if a candidate can write code but also if they solve a complete problem. In other words, they are more than simply a cute or abstract 10-lines-of-code size of problem, without getting into the complexity of a full system. Most candidates on modern agile/lean engineering teams are expected to own a problem's domain from initial understanding through automated acceptance testing.

When are whiteboard problems effective?

Face-to-face ("whiteboard") style problemsolving is effective to ensure a candidate can identify and pseudocode an algorithm in a reasonable length of time.

Why share our code problems?

(insert text about sharing here)

Sources used

  • Streamtech problem set - this is a great list of problems that can be used. Some of the problems here are based on the Streamtech list.

Other sources and sites

License

All content and code included in this repository is licensed under CC-BY 3.0 (content) and the MIT license (code) found in the root of this repository in LICENSE.txt.

CC-BY 3.0 for content requires attribution. Unless specifically listed in other content, attribution should consist of a link to (http://adhoclabs.co) and a contributor name of "Ad Hoc Labs".

About

Problems used for at-home coding tests.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages