Well, I don't know about that. I can only speaking to the developer side of things, but an unfortunate reality is that realistically, no one is looking at your GitHub in the interview pipeline,...
Reduced to its simplest form, LinkedIn is a digital resume. A profile consists of your past work experience, education, skills, and references. The posts, comments, and messages are like a cover letter. But we’ve long decided that there are better ways to showcase your ability than a list of the places you’ve worked, the school you went to, and a hastily drafted plea for work. Resumes are old scrolls of a bygone era. If LinkedIn is a site meant to demonstrate you’re an expert, it’s competing against all the places you can do this better.
Developers have GitHub, designers use Dribbble, and Academics maintain their ResearchGate or Google Scholar profiles.
Well, I don't know about that. I can only speaking to the developer side of things, but an unfortunate reality is that realistically, no one is looking at your GitHub in the interview pipeline, but some people might look at your linkedin, and your PDF resume is still the absolute king.
For one thing, a GitHub profile isn't something you can just scan to get a feel for. If I had 20 minutes, I could definitely glean something from it - but first, I'm not the one filtering candidates (engineers usually just get filtered candidates to perform technical interviews on, and usually with like zero context, so if you ever wonder why they're asking about something that's obviously on your resume, that's why), that's what the recruiting team (note: not technical) does, and second, those recruiters look at your resume for an average of 5-10 seconds before making a first judgement, not 20 minutes.
In that way, Linkedin is mildly more relevant, because at least it is standardized and organized, so your Linkedin profile represents essentially your full work history. Resumes should be 1 page and be readable (i.e normal font size, normal spacing), so inevitably it does not cover everything - just the highlights.
Although for every other feature of Linkedin I certainly see the surrealness the blogpost talks about. That's why Linkedin is my favorite bathroom social media - I just go on it and observe the weirdness while I do my business. I would absolutely recommend that no one take anything on that site seriously.
Well, I don't know about that. I can only speaking to the developer side of things, but an unfortunate reality is that realistically, no one is looking at your GitHub in the interview pipeline, but some people might look at your linkedin, and your PDF resume is still the absolute king.
For one thing, a GitHub profile isn't something you can just scan to get a feel for. If I had 20 minutes, I could definitely glean something from it - but first, I'm not the one filtering candidates (engineers usually just get filtered candidates to perform technical interviews on, and usually with like zero context, so if you ever wonder why they're asking about something that's obviously on your resume, that's why), that's what the recruiting team (note: not technical) does, and second, those recruiters look at your resume for an average of 5-10 seconds before making a first judgement, not 20 minutes.
In that way, Linkedin is mildly more relevant, because at least it is standardized and organized, so your Linkedin profile represents essentially your full work history. Resumes should be 1 page and be readable (i.e normal font size, normal spacing), so inevitably it does not cover everything - just the highlights.
Although for every other feature of Linkedin I certainly see the surrealness the blogpost talks about. That's why Linkedin is my favorite bathroom social media - I just go on it and observe the weirdness while I do my business. I would absolutely recommend that no one take anything on that site seriously.