Maybe a good point, but honestly, interviewers barely read resumes, they’re very, very likely not going to read your blog, or remember “hey it’s the person from that blog post I ready 7 weeks ago.”
Maybe a good point, but honestly, interviewers barely read resumes, they’re very, very likely not going to read your blog, or remember “hey it’s the person from that blog post I ready 7 weeks ago.”
> interviewers barely read resumes
I feel like this is the biggest lie ever told in this industry. Do you, as an interviewer, not read resumes?
I read loads of resumes and the truth is more like everyone are terrible communicators. Especially software engineers. Most resumes are badly formatted, badly typeset, full of errors and give me confusing/contradictory details about what your job responsibilities were rather than what you accomplished.
Most peoples' resumes are so low-effort that they're practically unreadable and I'm trying to read between the lines to figure out what you're capable of. I might as well not be reading them because I'm trying to figure out what you've done, what you're good at and what motivates you and nothing you've given me on that paper helps me do that.
One of these days someone is going to figure out how to cross-polinate technology people and sales people in the office to smooth out each others' rough edges. Whoever does is going to revolutionize industry.
It is true for some companies. That said, in my experience, the more it was visible in an interview that the interviewer read my application, my website, my open-source code etc, the more enjoyable working for that company has been for me. I guess it’s a sign people at such a company give a shit. It transfers to other areas than just interviews led by them. At this point, if I see that the interviewer barely skimmed my CV, my expectations, that this job will be good, plummet.
> I feel like this is the biggest lie ever told in this industry.
It's not. I've been in a number of interviews where the interviewer has told me straight up "I didn't read your resume. Mind giving me a second to give it a scan?"
To be fair, as you mention, resumes are horrible tools. They should only be used as a place to start a conversation, so does it really matter if the interviewer reads it in depth before starting the interview?
Others in the loop (sourcer/screener/recruiter at minimum) almost certainly read your resume for you to even make it that far.
It's starting to sound to me like on both sides of this conversation, up-front effort made can be strong positive signal...
I’m a little confused, because first you challenge me, but then come to the exact conclusion that resumes are largely unreadable. I’ll look for something they claim to have done to dig deep on, see if it’s BS or not, but I’m not reading every X by Y% with my jaw on the floor. FWIW I’m generally on the back side of the process, where someone at the front (is supposed to have) vetted the person already.
> where someone at the front (is supposed to have) vetted the person already.
I think that's a mistake, personally. Each interviewer needs to make an independent decision and relying on the judgement of a screener early in the process is giving that person disproportionate weight towards hiring for your team. Usually that resume screener is someone in HR. Would you trust them to decide who your team hires?
Your posts do indicate that maybe there is a larger segment of folks who don't read resumes than I realize...My amount of rigor may only come after being involved in some catastrophically bad hiring decisions. Like someone I made the deciding vote to hire was stalking multiple employees, was a heavy drug user, did zero work of value and ultimately crashed and burned by getting arrested for coming at someone with a knife. For years HR wouldn't let us fire that person because of their protected class and multiple false claims they made against a large number of employees.
If it’s truly only HR and then direct to full interview panel then I agree with you, but I’ve never worked somewhere where a technical person wasn’t involved in screening. Yes recruiters will winnow the inbound, but usually there a technical phone screen, hiring manager screen, or both.
FWIW this is what I assumed to be true when I said what I said.
And yet still that screening almost always has less technical depth than further interviews. It should not carry the most weight in the process, but because of practices like this it does.
Sorry, can't agree with this. The hiring manager's decision carries the most weight yes, but saying it's biased towards the screen is over-generalizing. I'm sure sometimes it is, but as someone who interviewed thousands and hired hundreds over a quarter century career at many organizations large and small, I can tell you unequivocally that technical feedback can and does regularly override my screening signal.
I expect that for a Developer Relations role, someone read the blogs.
That’s a good point, I’ve been a bit burnt out on strictly eng roles that I projected there a bit
Perhaps the blogs of the candidates yes. On the other hand, perhaps OP will find a perfect fit this way.
Absolutely. Especially for late-stage candidates.
People get hired all the time based on their online content. Or, at the very least, they get interviews when they wouldn't otherwise. Don't forget about the luck surface area!
As a hiring manager, I've read blogs. Heck when reviewing a stack of resumes, "has a technical blog" almost certainly moves a candidate to a consider pile and they are probably getting a callback in the very least.