On this episode, we have Alfie Ordoña, Jayz Carrillo, Oscar Oganiza, and Ragde Falcis joining us to discuss "IT, IS, CS Grads: Do Schools and Grades Still Matter?" and What recruiters really look for (and what they ignore).

With bootcamps, certifications, and self-taught developers entering the field, the value of a traditional tech degree is being reexamined. In this episode, we explore how much your school background, course title, or grades still matter when applying for tech roles. Our guests include recruiters and hiring managers who’ll share what they really pay attention to—and what they often skip over.

In your hiring experience, how much weight do you place on degrees or GPA? (Generalization)

While a degree can show a foundational understanding, experience and practical skills often outweigh GPA. Many recruiters prioritize a candidate's ability to solve problems and contribute to a team over academic distinctions.

How do IT, IS, and CS graduates typically differ in skills or readiness? (Generalization)

CS graduates often have a stronger theoretical computer science background, while IT and IS graduates might be more oriented towards systems management or business applications. However, individual portfolio projects and internships often bridge these gaps, making readiness more about practical exposure.

What stands out more to you: a strong resume or a strong portfolio? (Generalization)

A strong portfolio almost always stands out more than just a resume. It provides concrete evidence of a candidate's skills, creativity, and problem-solving abilities, demonstrating what they can actually build and achieve.

Should schools update how they prepare students for today’s tech industry? (Generalization)

Absolutely. Many believe that academic curricula should incorporate more hands-on projects, industry-relevant tools, and soft skills like collaboration and communication to better prepare students for the dynamic tech landscape.

What's one thing recruiters often skip over on a resume or application? (Generalization)

Recruiters often gloss over generic objective statements or long lists of courses taken without corresponding project work. They're looking for impact, achievements, and specific skill sets relevant to the role, rather than general academic history.