<!-- Please use the below as a GUIDE not a Requirement. The more details we have the better the discussion will be --> ### ISSUE TYPE * [ ] Typo <!-- Document Correction Needed --> * [ ] Bug <!-- Functionality broken --> * [x] Feature <!-- Suggestion for new functionality --> ### WHERE / WHAT <!-- Where is the issue? If possible indicate the name of all files affected --> Our technical interview questions are a little light on `technical.html`. It would be good to add this question to our list. ### EXPECTED BEHAVIOR <!-- FOR TYPO: Proposed Corrections for grammar review --> <!-- FOR BUGS: Provide any details to the behavior expected --> <!-- FOR FEAT: Provided details on how the feature should work and the benefits of adding the feature in --> Clicking a link will take you to the question page which will allow you to see a possible response to the question. ### REPRODUCTION STEPS <!-- FOR TYPO: Provide file name and section of typo / document correction --> <!-- FOR BUGS: Provide any steps required to reproduce the issue and screenshots when possible --> <!-- FOR FEAT: Suggested steps / flow to get desired affect --> To create this new question, you should be able to follow the guide in the README [https://github.com/approachable-io/software-interview-prep](https://github.com/approachable-io/software-interview-prep)
ISSUE TYPE
WHERE / WHAT
Our technical interview questions are a little light on
technical.html. It would be good to add this question to our list.EXPECTED BEHAVIOR
Clicking a link will take you to the question page which will allow you to see a possible response to the question.
REPRODUCTION STEPS
To create this new question, you should be able to follow the guide in the README https://github.com/approachable-io/software-interview-prep