I think the more important overarching point is that most candidates aren't prolific github people like you, and likewise most companies are not going to cater their interviewing practices to woo your preferred flavor of interview style.
Most candidates don't have code samples laying around (e.g. they only write proprietary code for work), so asking for some is a non-starter in a lot of cases.
Another point worth of reflecting, your accomplishments in OSS say nothing of interviewing expertise, they are completely different skillsets. Companies may not hire in the order of 50k people a year, but interviewer calibration in a large org is absolutely a problem that isn't easily solved by just following the opinion of some random 6-digit salary SWE.
As someone who's interviewed in the order of a few hundred senior SWEs, I think there are good and bad ways to go about any interview format, including leetcode-style.
Complaining about how companies don't just throw away their interview practices in favor of [insert pet format here] doesn't really help, since it isn't really actionable.
We talk about the perils of full software rewrites, I think similar concerns exist for hiring as well.
Anecdotes are not data etc, but in my experience (hiring senior SWEs for a big tech co) less than 1 in 20 candidates have a link to github or side project listed in their resume. Distribution-wise, they seem to appear more frequently w/ younger candidates.
Most candidates don't have code samples laying around (e.g. they only write proprietary code for work), so asking for some is a non-starter in a lot of cases.
Another point worth of reflecting, your accomplishments in OSS say nothing of interviewing expertise, they are completely different skillsets. Companies may not hire in the order of 50k people a year, but interviewer calibration in a large org is absolutely a problem that isn't easily solved by just following the opinion of some random 6-digit salary SWE.
As someone who's interviewed in the order of a few hundred senior SWEs, I think there are good and bad ways to go about any interview format, including leetcode-style.
Complaining about how companies don't just throw away their interview practices in favor of [insert pet format here] doesn't really help, since it isn't really actionable.
We talk about the perils of full software rewrites, I think similar concerns exist for hiring as well.
reply