-
Joe Mastey - Hiring Developers, with Science! [32:31] Takeaway: Validity - tests a known construct. Reliability - how closely grouped results are. Usability - how easy it is to use. You can only have 2 of them. Test your interviews on your existing team. Have a scoring rubric for the interview to minimise variance and bias. Don't debrief as a group until you have written down feedback. Interviewers will come to the same conclusion so they don't look stupid. Share all feedback at once.
-
Sam Barnes - People are Weird, I’m Weird[29:34] Takeaway: Don't lie to candidates. Find out what they don't like and be honest if that is the environment you have.
-
Cate Huston - Applied humaning for technical interviews [32:20] Takeaway: In a power based situation, the quality of the relationship is owned by the person with the power. Much of what we do as developers is not coding - we should test for those things in the interview. Remove conclusions in feedback you can't support with evidence. Remember interviewing is stressful and people are doing their best. Interviewer needs to be good at time management.
-
Kate Heddleston - Onboarding and the Cost of Team Debt Takeaway: Each person who is not fully onboarded, integrated or managed leads to team debt. If team debt gets too high, then the team may need to stop work to get properly trained. Onboarding is finished when reliable independence is achieved. Reiterating processes when someone new joins helps realign existing members as well as new ones.
-
Patrick Kua - Onboarding Strategies Takeaway: Good series of strategies for onboarding new team members. Maintaining a list of technical debt that is shared with new team members. Catalogues of patterns in use. Preparation email of tech stack, tools, patterns etc.
-
Jeff Dwyer - Onboarding Engineers: How to Tackle the First 30 Days Takeaway: Think hard about task selection. Small wins early on. Pair them up with a coding mentor. Set the tone in PRs about how you review code. Spend time pairing with them.
💲 - paid for content