[Remote] Beyond the Brain Teaser: Technical Interviewing with RESPECT

"How would you move Mount Fuji?"  

Great question, but does an engineer need to know the answer in order to write great code?  No?  I don't think so either.

The technical interview is one of the most controversial, challenging, and stressful parts of an engineer's career. The more senior the engineering position, the  less relevant the brain teasers, algorithm quizzes, and puzzles that make up these interviews are to the evaluation of a potential candidate. And although this interview style first became famous at large tech corporations like Microsoft and Google, it has propagated across the industry to the point that courses are springing up in college campuses and bootcamps showing candidates exactly how to "crack" these interviews.

In the past, I’ve worked at a number of companies as a lead developer and in that role I spent a lot of time interviewing folks for technical positions. We weren’t allowed to choose our own process and had to follow the company’s rules. In that time I learned a lot about what works, and what doesn't work, for judging technical aptitude in an interview setting.

In this presentation I will talk about the difficulties of technical interviewing from both the interviewee and interviewer's point of view, and provide several helpful tools using the acronym RESPECT to improve the interviewing experience across the board.

** 日本語版もあります。

 
 

Outline/Structure of the Talk

  1. Introduction
  2. A Sample Problem
  3. My First Technical Interview and Other Stories
  4. Benefits and Drawbacks of Technical Interviewing
  5. The RESPECT Process and How To Apply It Without "Lowering The Bar"
    1. (R)eal Solutions 
    2. (E)xperience
    3. (S)afety 
    4. (P)otential
    5. (E)arned Trust
    6. (C)onversation
    7. (T)ime

Learning Outcome

After attending this talk, attendees will have a grasp on a new way of approaching evaluation of technical candidates and be able to apply the principles discussed during their own candidate interview cycles.

Target Audience

Engineers, Managers, HR Professionals

Prerequisites for Attendees

No Prerequisites

schedule Submitted 1 month ago

Public Feedback

  • Yasunobu Kawaguchi
    By Yasunobu Kawaguchi  ~  4 weeks ago

    プロポーザルの投稿ありがとうございます。
    トピックのカテゴリーをよりわかりやすく再構成しました。
    本プロポーザルのトピックにも反映しております。
    Thank you for submitting proposals.
    We have reorganized the topic categories to make them easier to understand.
    This is also reflected in the topics of this proposal.

    • ...

  • Woohyeok Aaron Kim
    keyboard_arrow_down

    Woohyeok Aaron Kim - Roll your Product with Kaizen Culture(Let's 'Tech' the initiative (Renewed for 2021))

    45 Mins
    Talk
    Advanced

    Jeff Sutherland氏、Martin Fowler氏、Taichi Ohno氏。世界の業務プロセスに変革を導いた彼らは共通的に「カイゼン」について強調しました。

    彼らの本を読みエンジニアとしての道を歩んできた私たちにとって、「カイゼン」は第一の価値として認識されていると思います。

    皆さんは、今日より良い明日のために何に力を入れてますか?毎日が忙しすぎて、何かを改善するどころかストレスだけ溜まってたりはしてないでしょうか。

    楽天のランキングサービスグループは開発と運用、いわばDevOpsを実践していますが、そのプロセスに対しいくつか問題を抱えていました。開発の段階で発生するボトルネック、効率的だとは言えない運用環境。

    何よりも問題だったのは、こういったボトルネックにおいて改善の文化が定着しにくいということでした。せっかく良いアイデアを思いついても、そのボトルネックから発生するコストの問題で後回しにするしかなく、そうなればなるほどチームの改善力はどんどん下がっていきました。

    私たちランキングチームは2つの解決策を決め、それを同時に進め相乗効果を発生させることでこの状況を乗り越えようとしました。

    ランキングチームが挑戦したトライアルそしてテクニカルな変更によるチームカルチャーの変化。またその後1年間の運用ストーリーまで!

    より安全で良いサービスの提供のために、日々工夫を重ねているあなたのために、私たちのお話を特別に公開します。

  • Michael Migliacio
    keyboard_arrow_down

    Michael Migliacio - [Remote] Leading Engineers To Water: The Art, Science, and Culture of Technical Coaching

    45 Mins
    Talk
    Beginner

    Software engineering may be difficult, but fostering a working environment that enables skilled engineers to perform their best can sometimes seem downright impossible. Every day, many engineering teams are battling a messy whirlwind of forces like unmovable deadlines, imposter syndrome, psychological safety issues, personnel/leadership conflicts, fierce technological preferences, and more. With teams more distributed all over the world than ever before, cultural differences can exacerbate many of these difficulties.

    In this presentation, I’ll discuss tips, tricks, and techniques that technical leaders and managers alike can utilize to better coach engineering teams, including concepts like the definition of empathy (and, more importantly, what doesn’t count), the trust-influence relationship model, introducing new technologies in a meaningful and consumable way, and a 5-step process to provide teams confidence to own their new solutions moving forward.

    ** 日本語版もあります。

help