WHITEBOARD:
Interview Practice
Jovena Whatmoor
WHITEBOARD TIPS
• It’s a conversation, not a test
• Listen
• Ask questions
• It’s okay to ask for a 2-min pause to think
• Manage your time, practice for speed
• Leave space on the board for adjustments or notes
• Talk through the whole exercise
• Sometimes there’s more than one “right answer” - talk
through different approaches
• It’s more than getting to the right answer
WHAT THEY’RE EVALUATING
1. Problem solving skills
2. Communication skills
3. Ability to articulate questions
4. Willingness to take in feedback
5. If you understand your limitations
6. Depth of technical understanding
WHITEBOARD APROACH
1. Repeat the question, write it down
2. Ask clarifying questions
3. Sketch out high-level approach
4. Begin writing the coding solution, talking it
through – This is a conversation!
5. Ask for feedback
6. Run tests, including edge cases
7. Make adjustments if tests fail
8. Optimize
HOW TO FAIL
• Faking it, instead of asking questions / coming
across like you think you know more than you do
• Refusing to take input or not asking clarifying
questions when prompted
• Go straight to the answer skipping the problem
solving and explanation steps
• Quietly working without explaining
• Trying to get it perfect in your head before writing on
the board
• No testing, no thinking of edge cases, no optimizing
AGENDA TONIGHT
• Choose an exercise
• We’ll group you
• Take turns sketching solutions (swapping
roles of interviewer, candidate, evaluator)
• Expectations: Interview skills not JS skills
• We’ll come through to check-in and regroup
people as needed
• Wrap-up group discussion – what did you
learn
THANKS FOR COMING
FACILITATOR
@clutchtalent
www. clutchtalent.com
STAY IN TOUCH!
github.com/nyjavascript
@nyjavascript
meetup.com/ny-javascript
nyjavascript.slack.com
www.nyjavascript.com

Whiteboard Interview Practice NY JavaScript

  • 1.
  • 2.
    WHITEBOARD TIPS • It’sa conversation, not a test • Listen • Ask questions • It’s okay to ask for a 2-min pause to think • Manage your time, practice for speed • Leave space on the board for adjustments or notes • Talk through the whole exercise • Sometimes there’s more than one “right answer” - talk through different approaches • It’s more than getting to the right answer
  • 3.
    WHAT THEY’RE EVALUATING 1.Problem solving skills 2. Communication skills 3. Ability to articulate questions 4. Willingness to take in feedback 5. If you understand your limitations 6. Depth of technical understanding
  • 4.
    WHITEBOARD APROACH 1. Repeatthe question, write it down 2. Ask clarifying questions 3. Sketch out high-level approach 4. Begin writing the coding solution, talking it through – This is a conversation! 5. Ask for feedback 6. Run tests, including edge cases 7. Make adjustments if tests fail 8. Optimize
  • 5.
    HOW TO FAIL •Faking it, instead of asking questions / coming across like you think you know more than you do • Refusing to take input or not asking clarifying questions when prompted • Go straight to the answer skipping the problem solving and explanation steps • Quietly working without explaining • Trying to get it perfect in your head before writing on the board • No testing, no thinking of edge cases, no optimizing
  • 6.
    AGENDA TONIGHT • Choosean exercise • We’ll group you • Take turns sketching solutions (swapping roles of interviewer, candidate, evaluator) • Expectations: Interview skills not JS skills • We’ll come through to check-in and regroup people as needed • Wrap-up group discussion – what did you learn
  • 7.
    THANKS FOR COMING FACILITATOR @clutchtalent www.clutchtalent.com STAY IN TOUCH! github.com/nyjavascript @nyjavascript meetup.com/ny-javascript nyjavascript.slack.com www.nyjavascript.com