> Even at the risk of false negatives, I would actively filter out resumes listing schools like these.
I am occasionally on hiring committees and use a rubric for ranking candidates. The rubric usually has 8-10 yes/no questions that might be best summarized as "Does this applicant's resume and cover letter indicate that they have actually written code deep enough to 'map' to our requirements?" Some of the rubric may be a little more specific to the actual job role, but the main idea is to filter out what I have come to think of as "aspirational" software developers.
I think one nice thing about the rubric approach is that candidates don't score "prestige" points or get "penalty" points for their specific educational background. Honestly, it seems like a lot of students from many institutions (some quite well known for rigor) are mostly about the "credential, not for the learning." The rubric seems to effectively filter out the less skilled or interested without eliminating skilled candidates with less "sterling" credentials.
I am occasionally on hiring committees and use a rubric for ranking candidates. The rubric usually has 8-10 yes/no questions that might be best summarized as "Does this applicant's resume and cover letter indicate that they have actually written code deep enough to 'map' to our requirements?" Some of the rubric may be a little more specific to the actual job role, but the main idea is to filter out what I have come to think of as "aspirational" software developers.
I think one nice thing about the rubric approach is that candidates don't score "prestige" points or get "penalty" points for their specific educational background. Honestly, it seems like a lot of students from many institutions (some quite well known for rigor) are mostly about the "credential, not for the learning." The rubric seems to effectively filter out the less skilled or interested without eliminating skilled candidates with less "sterling" credentials.