Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A Better Technical Interview 💚 #11

Closed
samjonester opened this issue Jan 11, 2017 · 1 comment
Closed

A Better Technical Interview 💚 #11

samjonester opened this issue Jan 11, 2017 · 1 comment

Comments

@samjonester
Copy link

Your name and twitter handle:
Sam Jones @samjonester

Your talk idea, described briefly:

Technical interviews are scary! They often involve pairing, but not the way we do it in real life. Let's discuss a better way to handle technical interviews than playing buzzword bingo and solving algorithms as fast as we can!

This talk presents a better approach to technical interviewing:

  • Focus on how to break down problems.
  • Prioritize workflow rather than completion.
  • Treat it as a chance to see how a candidate learns and teaches in an unfamiliar setting.
  • Give positive feedback about what to learn for the next time. Candidates should either be hired or not yet hired.
  • Make sure the candidate leaves having learned something from the interview! Don't waste their time even if they're a "not yet".

Approx length - must be less than 15 minutes to be considered:
10-15 min

Type of talk (creative, passion, technical):
Passion / Softtalk / Noob-love

@pixelyunicorn
Copy link
Member

Thanks for your talk submission! We only have time for one more talk at our Jan 24th meetup, is there a preference on which talk you wanted to give?

I (personally) prefer "A Better Technical Interview" to balance out the technical nature of the rest of the 3 other scheduled talks, but that decision is completely up to you.

@pixelyunicorn pixelyunicorn added this to the January 2017 milestone Jan 13, 2017
pixelyunicorn pushed a commit to TacoJS/tacojs.github.io that referenced this issue Jan 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants