Panel: Better Hiring Practices for Fun and Profit
summary
Job descriptions list day‑to‑day work and reporting lines, not buzzwords; many teams require a two-step code challenge (unlimited tech take‑home then a dictated task) plus pairing and code‑sample walkthroughs. Use Greenhouse scorecards, forbid cross‑talk until everyone submits, and measure ramp with sprint outputs. Replace “culture fit” with culture add, advertise minimum vacation instead of “unlimited,” and note the Hewlett‑Packard/Harvard Business Review finding that women apply only at 100% match versus men at ~60%.
AI-written summary · about
chapters (16)
- 0:00Welcome and panel intro
- 1:30Worst interview horror stories
- 6:32Effective job descriptions
- 11:16Decoding job descriptions
- 14:52Pitfalls in job postings
- 16:20Assessing technical ability
- 21:59Team skills inventory
- 24:28Skip technical assessments?
- 25:59Standing out in hiring
- 27:47Why diverse hiring matters
- 30:59Gender gap in hiring
- 34:10Education vs experience
- 35:32Progressive hiring practices
- 37:18Measuring remote productivity
- 38:21Normalizing interview feedback
- 39:45Closing remarks
related talks
49mFinding potential in your interview processes
44mHire Better Faster Stronger
35mHiring Software Testers Panel Discussion
45mHiring is Not Hazing
26mBeyond the code: hiring for cultural alignment
36mCracking the hiring process
49mCreating a Workplace to Retain your Tech Talent
27mTech hiring is broken' is broken