https://github.com/tedder/interview-code-tests
Problems used for at-home coding tests.
https://github.com/tedder/interview-code-tests
Last synced: 5 months ago
JSON representation
Problems used for at-home coding tests.
- Host: GitHub
- URL: https://github.com/tedder/interview-code-tests
- Owner: tedder
- License: other
- Created: 2015-02-25T17:10:22.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2017-05-02T22:57:39.000Z (about 9 years ago)
- Last Synced: 2025-03-04T09:27:40.934Z (over 1 year ago)
- Language: HTML
- Size: 14.6 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
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](http://web.archive.org/web/20130502164931/http://www.streamtech.nl/site/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
* [Geekinterview.com Interview Questions](http://www.geekinterview.com/Interview-Questions) (over 25k questions with answers!)
* [github: donnemartin: interactive coding challenges](https://github.com/donnemartin/interactive-coding-challenges)
# License
All content and code included in this repository is licensed under [CC-BY 3.0](http://creativecommons.org/licenses/by/3.0/) (content) and the [MIT license](http://opensource.org/licenses/mit-license.php) (code) found in the root of this repository in [LICENSE.txt](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".