4 ms·
Part of your job as a hiring manager is to find the great candidates that other hiring managers are missing. I've worked with people who are incredibly effecti
by simonw 3y ago
Part of your job as a hiring manager is to find the great candidates that other hiring managers are missing.
I've worked with people who are incredibly effective engineers but are bad at promoting themselves through their resumes and who interview poorly.
Figuring out how to not to overlook those people is a great way to build an outstanding team.
- BrandonWatson 3y agoI have long said with my customers that the #1 job of the interview loop is to answer the following question: can this candidate do this job at this company and likely exceed expectations? It's surprising how many companies are bad at the interviewing process. How bad they are at the eval process (resume and interviews). It's still giving vitamin and not painkiller vibes though. I have been working in this space for the last few years as an indie hacker solopreneur. I'm currently working through customer discovery on this exact problem (eval candidates more effectively) and if you (or a delegate) could make time, I would really appreciate it.
- lamroger 3y agoI love the eval parallel...
- FireBeyond 3y ago> It's surprising how many companies are bad at the interviewing process. Some companies have such unrealistic expectations too. Here's one from a company that I bailed out of. Would have been an interesting company, I think, but not world-changing. This is literally how they described their process: Phase 1: Initial conversations - 30 minute recruiter screen - 60 minute resume deep dive Phase 2: Interviews - 15 minute hiring manager screen - 2 x 45 minute engineering - 60 minute overview of your past projects, including presentation Phase 3: Further interviews - 30 minute second interview with hiring manager - 30 minute values interview - 30 minute leadership interview - "additional interviews as required for position"
- EchoChamberMan 3y ago"60 minute overview of your past projects, including presentation" is so completely insane - is this a thesis defense for a phd, or a job application?
- ohthatsnotright 3y agoI bailed out of a similar set: - 30 minute recruiter call/discussion - 50 minute l33t code - 50 minute systems design - 30 minute in-depth presentation to a committee - 4-6x 45 minute group interviews covering l33tcode and system design as well as my presentation By the time I would have been done with this it would have taken basically a day of real time not to mention prep work for the presentation and every other interview. The pay was good but not life changing.
- jimbob45 3y agoPart of the problem is that people skills are essential to being a good engineer. Those with strong technical skills but weak interpersonal skills can still be great if they’re paired with a boss that can obscure their inability to communicate with others. But it’s difficult to know as a hiring manager if the tech boss you’re hiring for will have that ability. It’s almost gambling and hiring managers hate gambling more than anything.
- flappyeagle 3y agoWhat does it mean to be bad at promoting themselves in their resume? It’s just a list of companies and dates.
- Ensorceled 3y agoYour resume is just a list of companies and dates? Who the heck has been telling you to write resumes like that?
- flappyeagle 3y agoWhat do you expect to see on a resume? No companies? No dates?
- simonw 3y agoFor me personally I want to know about the projects that you accomplished - both at those companies and outside of them.
- flappyeagle 3y agoWhy? You have no possible way to contextual these things I built an internal workflow engine at a law firm. It worked really well for the use case. I can spend all my time convincing you how cool of a project this was but what I should have done is buy Jira.
- simonw 3y agoThen that should be on your resume. Knowing that you built an internal workflow engine is much more interesting to me than knowing you were a "senior software engineer". It gives me something to ask you questions about in an interview - I don't need to see the proprietary code to have an interesting conversation about how you designed it and what you learned from the process.
- JoshTriplett 3y ago