A metaphorical package.json for holding wholesome tech interviews

package.json

{
"name": "Holding wholesome tech interviews",
"version": "1.0.0",
"description": "A centralized table of contents for a set of personal articles, published on the Medium platform, on the topic of making tech interviews more meaningful, pleasant & constructive.", 
"author": "Dragos Filipovici",
"license": "All rights reserved",
"custom-dependencies": "time, energy, kindness, patience, passion",
"custom-scripts": {
  "explore": "view the main thread of the articles, in the comment bellow"
}

I. The overall format

Article link: Chapter 1/7: the format

In a nutshell: More than just technical interrogations

Sections:

• rethinking the format
• taking notes from the best
• on-the-spot + long-term wins on both sides
• [a preview of] requirements, for the interviewer side
• and more wins ahead

II. Initiating the interview

Article link: Chapter 2/7: the init()

In a nutshell: Defuse the discussion from the get-go

Sections:

no more `forms`

what does your work day sound like

not just small talk, but a discreet foundation to build up from

mark (and later explore) past achievements

lead the convo, transparently

beginnings matter

III. Conducting the interview

Article link: Chapter 3/7: the main

In a nutshell: Leadership during five common interview scenarios

Sections:

• Of course the technical init() extends the interview init()
• The cost of an extremely efficient interview tempo
• All scenarios + Scenario A: the candidate has God Mode enabled
• Scenario B: they can’t cover some of the questions at all
  - being pro
  - assisting
  - rewards & surprises
  - enticing & coaching
  - sharing & being open
• Scenario C: they don’t provide the absolute exact answer that we are waiting for, but they are close
• Scenario D: they don’t understand a question or a topic
• Scenario E. even though a topic was not known or fully known, we sense interest and excitement for that topic

IV. Being mindful of the needs of both sides

Main idea: Benefits of modelling an interview’s information, from different perspectives

Article link: Chapter 4/7: our requirements

In a nutshell: a clear mental model of an interview’s information can grant us more flexibility steering the discussion and making it a natural one, and also help set up the foundation for another essential item.

Sections:

• +2 more tools to our [batman] belt
• .the solution, .the-root-of-the-problem {
• the interviewer requirements
• the interviewer requirements/non technical
• the interviewer requirements/technical
• the job opening requirements
• traversing technical requirements: challenge
• traversing technical requirements: solution

Article link: Chapter 5/7: their requirements

In a nutshell: including also the candidate’s requirements directly into that clear mental model of our interview can help us dedicate equal attention to this often overlooked yet essential area.

Sections:

• requirements sit not only with the hiring side
• initiating
• exploring what the candidate needs
  • 1. what they would love to continue doing, and what they would prefer to gradually or directly cut out,
  • 2. instead of the dreaded “where do you see yourself in the next 5 years”,
  • 3. their openness towards mentoring
  • 4. what they expect out of
  • 5. the way they function best, and what they require to function optimally
  • 6. explore any strong passions, for any of the discussed notions
• bonus branch! noticing passion

Article link: Chapter 6/7: their questions

In a nutshell: skipping or rushing a candidate’s questions will keep our interview more time-boxed, but will also keep their risk of switching companies higher. We explore ways to avoid that.

Sections:

• reversing the interview
• rushing the reverse interview
• #1. prioritise this higher, by acknowledging its potential impact, and extending the total interview duration
• #2. prioritise this higher, by better formalising it
• #3. fallback option: plan a separate call
• #4. fallback option: use email
• #5. magic
• #6. don’t dismiss the temporarily unanswerables, call for backup
• even more potential surprises
• effortAndGoodEnergy() { return effort, and good energy; }

V. The rewards of a genuine smile

Article link: Chapter 7/7: the ^^

In a nutshell: what’s not a picture but still worth > a 1000 words (per second)? The calm and energy from a friendly, genuine smile.

Sections:

• the what
• our social APIs
• the why
• the how
• Parting thoughts
  • #0. Way ahead of you, kid!
  • #1. Fair warning: bandwith
  • #2. Fair warning: non linear thread
  • #3. Fair warning: unplanned positive effects