First off, I'm glad that Turing has such an awesome resource as Ian Douglas to help with tech interview prep. Admittedly I was not looking forward to the process, but I'm still glad I had a relatively "safe" oppurtunity to do so (to say nothing of the excellent and thorough feedback I recieved as well). Going into the interview, I predicted that I would do decently well asnwering the "conceptual" technical questions and struggle with the code challenge, which was pretty much what actually happened in the end. I was reminded that I can be somewhat long-winded when people ask me open-ended questions, and that I need to work on getting my "how did you get into development" pitch focused and clear. In a few spots I totally gave the right answer and then backtracked and said I didn't actually know, which was both suprising to hear in the review and made me think I should be more confident in my answers if I think I can at least partially answer. Main takeaway from the session was that practice will be key to moving forward. To this end, I have been spending an hour a day working through code challenges and documenting my problem-solving process, reviwing old "checks for understanding" PRs, and working on a spreadsheet of questions (both behavioral and technical) to prepare to be asked by employers.
Last active
April 19, 2017 00:46
-
-
Save mollybrown/5633b7e7b5b251e1ff2e6c435a547e80 to your computer and use it in GitHub Desktop.
Interview Prep Refelction
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment