The Rise of Skills-Based Hiring: What It Means for College Grads and Employers This Fall

The misconception I would push back on is that skills-based hiring is mainly about measuring objective skills. Hiring was never only about hard skills, and it is even less so for new or recent grads, since their careers are just beginning. Submitting a resume used to carry signals of genuine interest in the role, intrinsic motivation, and a demonstration of effort, but no longer.

This fall, the key problem is trust. AI has flooded recruiters with noise, and the first thing they wonder about any resume is how much of it is real. For high-volume, early-career roles, that noise is overwhelming. It’s common for bots or AI tools to submit job applications, or for multiple candidates to use the same AI tools and submit nearly identical answers to screening questions. At this scale, recruiters cannot possibly phone screen anyone who has a decent sounding resume, so they fall back on referrals or phone screen in batches, meaning most applications never get a second look. Candidates feel ignored, recruiters struggle to find the right person, and the hiring process pleases no one.

A more successful hiring process recovers those lost trust signals. Skills-based hiring for college grads is about showing critical thinking and good judgment in a more credible manner than a resume alone provides. The clearest communication of this concept is what a PhD researcher recently called “trace hiring,” featured by the World Economic Forum. The point is to design a small, authentic interaction that reveals how a candidate works through a real problem, so the strongest signal comes from watching them think in real time. For a new grad with a thin resume, this is the fastest way to rise above the noise and earn a first conversation without a referral.

Setting up an environment where college grads want to share anything beyond a resume isn’t easy. They need to understand what is being asked of them and be clear how anything they produce will be used. Their parents or advisors might scoff at this idea; they never had to do this. But the world has changed, and whether they like it or not, college graduates will be forced to be pioneers in a new hiring process spurred by a vastly disruptive, rapidly evolving technology.

I’ve hired new grads, so I’ve seen both sides.

Skills-based hiring gets misread when employers treat a coding task or portfolio link as the whole proof. For an early-career developer, the missing evidence is often how they work when the requirement is imperfect, the reviewer disagrees, or the business logic has to be explained twice.

This view comes from how we run engineering review. Our code review standard says the goal of review is code that is good enough for the product, and it’s also a teaching stage and a way to transfer business logic through the team. That matters for junior candidates because their first months are full of translation work. They read a ticket, ask what result is expected, connect the change to a user scenario, and then adjust after review. A strong graduate can show that chain. A weak process hides it behind a polished final artifact.

The same thinking shapes our requirements. A ticket has to define the task, the expected result, the verification path, and the materials behind it. During review, critique stays on the code rather than the person, and broad verdicts are replaced with a specific request. Those rules make feedback useful because the candidate learns the product and reviewers can judge how the candidate thinks under correction.

Career services teams can prepare students to show review history, issue writeups, test notes, and short explanations of tradeoffs. Employers should add one ambiguous requirement and a review pass to work samples, then evaluate the response to feedback. Treat the degree and the skills test as signals. The hiring decision improves when the team sees how the person learns inside a real development loop.

One of the biggest misconceptions regarding skills-based hiring is the notion that skill-based hiring implies a relaxation of standards or that it is one more way of accommodating the candidates who do not have necessarily prestigious credentials. In fact, using skills in the hiring process is often more demanding than merely checking the diploma since it requires proof of utility right away, in lieu of the diploma. Based on my experience over the past two decades of building engineering teams throughout the globe, I can state that candidates’ performance in real-life settings is a much better predictor of future success than the name of the school they graduated from.

In our operations we have moved toward the assessment approaches that meet what I refer to as applied agility. Instead of asking theoretical questions, we analyze the applicant’s capability of doing well via a sandbox test with flawed code or a clearly defined business problem. I have seen plenty of applicants from well-recognized universities fail in the troubleshooting process because their education was more about passing the course rather than developing working software. On the contrary, students of less famous programs spent their time on doing something real and thus, have better understanding of the development processes and how to deal with the vagueness of projects.

The most common mistake employers make at this time of year is using the skills assessment final phase only as a final tie-breaker between the candidates who have passed the filter based on the credentials. If employers want to benefit from the assessment then the assessment should be in the center of the recruitment approach, meaning that the degree is background that excludes and limits a pool of applicants with high productivity, technical know-how that they may lack. This fall, the applicants should view their portfolios as real resumes whereas employers should shift their attention toward the applicants’ output rather than their past history.

I would say that one misconception I frequently hear about skills-based hiring is that it means discounting degrees and other credentials entirely. That isn’t the case in my experience. The strongest skills-based hiring strategies are those that integrate assessment of demonstrated skills alongside other qualifications, in a ratio that’s adjusted to match the needs of the specific role being filled.

From a recruitment standpoint, we see the most value come from separating the capability employers are assessing from specific credentials. In other words, it isn’t that degrees and past job titles don’t matter, but instead shifting the perspective so that these aren’t the only means employers use to validate or assess a skill. So for someone who is a recent graduate, for example, then we would still absolutely consider things from their education when evaluating them, though focusing more on hands-on projects, internships, and other demonstrated problem-solving and technical proficiency. On the other hand, for a candidate with over a decade of relevant industry experience, it isn’t a deal-breaker if they don’t also have a degree because we look to those past roles instead as proof of their skills in action.

This distinction is especially important in industries like energy and manufacturing. Many of these roles demand specific capabilities and knowledge of regulatory or safety requirements. They are also currently grappling with significant talent shortages and rely on skills that can be developed in a variety of settings, including both academic and on-the-job scenarios. The takeaway is that it benefits employers to give candidates a meaningful way to demonstrate their skills because it allows you to equally consider all qualified applicants, rather than relying on a stand-in like a degree or past job title that will only apply to a portion of the job seekers who can perform that role well.

When we say “skills-based hiring,” what we really mean is that we are abandoning “experience-based hiring.”

Skills have always been important, and recruiters genuinely believed they were hiring for them. But instead of measuring skills directly, they inferred them from experience.

Two candidates who completed the same degree can have widely different levels of expertise in that subject. Two candidates with the same amount of work experience can have radically different levels of expertise in their field.

Clearly, experience alone is not reliable enough for high-stakes selection decisions. Skills-based hiring reflects the acknowledgment that experience does not guarantee expertise.

Instead, candidates need to showcase their actual skills, not just their history. A skills-based hiring process explicitly evaluates candidates’ skills independently of their experience.

For example, having strong industry knowledge matters more than where you interned because that knowledge will be evaluated directly.

Naturally, if you learned useful skills during your internship, that experience will help. But simply having a padded resume is no longer going to move the needle.

Moving forward, expect to be assessed on what you know, not just what you have done.

The biggest misconception is that skills-based hiring means employers will somehow see your skills on their own, so the resume matters less. It’s the opposite. When a degree and job title stop being the filter, the burden shifts onto the candidate to make their skills legible, and most people aren’t ready for that.

We see this constantly. A grad will have real skills buried in a line like “worked on a team project using Python and SQL.” Skills-based hiring doesn’t rescue that bullet. A reviewer scanning for evidence of actual ability sees a vague group project, not a person who can do the work. The skill was there. It just wasn’t shown.

What shaped this view is watching how differently two resumes land when one names the specific thing the person built and what came of it, and the other lists technologies in a skills section with nothing behind them. Skills-based hiring rewards the first and quietly filters out the second. For grads this fall, the takeaway isn’t “credentials don’t matter anymore.” It’s that you now have to prove the skill, not just claim it.

The degree line came off the job posting and a years-of-experience floor slid into its place. We looked at about 29,000 job descriptions written on Pin, and roughly 69% have no degree language at all, which sounds like good news for a May grad. Then you look at the search box. Around 46% set a minimum years filter, and the median is five years when they set one.

The misconception worth killing is that skills-based hiring took the gate away. It moved. If you’re advising grads this fall, skip the transferable-skills speech and get them describing an internship as months of applied work with a number attached, since that’s the field being filtered on before a human opens a resume. Employers can fix their half by deleting the years floor on entry-level reqs, since those are usually template defaults rather than a real requirement.

The misconception that I would like to dispel is that skills-based hiring means just listing more skills. Rather, it raises the bar for proof, making applications more substantive while reducing the room for vagueness. One can list SEO, analytics, and lifecycle expertise on a LinkedIn profile in a matter of seconds, but an employer still needs to verify that this knowledge translates into a specific judgment or action. I have seen too many applications that sound impressive but fail the interview’s practical tests. At the same time, an employer can make the error of asking candidates to demonstrate 14 skills, with the outcome being similar to a grocery receipt. One needs to identify whether a candidate can demonstrate a particular skill to a sufficient degree within the context of the position’s constraints or limitations.

The perspective was formed by my experience in the talent space, where I encountered cases of misrepresentation and misunderstanding of the required skills. A 45-minute work sample, a portfolio with brief annotations, and one page of supporting explanations can say much more about the candidate than two pages of talking points and skills lists because the context clarifies if they understand the limitations and trade-offs, can explain their work, and know what they do not know. This approach also considers that AI can “polish” the application, making it sound better than it is, but it does not replace the actual work. However, one should not ask candidates to do unnecessary work as part of a trial either. In my opinion, the best practice for skills-based hiring is to request something short and focused on a specific task.

The misconception I’d challenge is that skills-based hiring means employers are lowering the bar or moving away from experience altogether. In reality, it’s often about looking more closely at what someone can actually do, rather than relying too heavily on job titles, degrees or a linear career history.

From a recruitment perspective, we’re increasingly seeing employers place more value on transferable skills such as communication, commercial awareness, problem-solving, adaptability and the ability to learn quickly. That can be particularly important for graduates, who may not have years of directly relevant experience but can still demonstrate the behaviours and capabilities needed to succeed.

The experience that’s shaped my view is seeing strong candidates get overlooked when hiring decisions focus too narrowly on whether they’ve done the exact job before. Some of the best hires aren’t necessarily the people who tick every box on paper; they’re the people who can demonstrate the right underlying skills and have the potential to grow into the role.

For employers this fall, I think the opportunity is to get better at defining the skills that genuinely matter for success, rather than simply translating an old job description into a list of requirements. And for graduates, it’s a reminder that internships and part-time jobs aren’t their only evidence of capability. University projects, societies, volunteering, freelance work and other experiences can all demonstrate valuable skills when they’re articulated properly.

I think one misconception is that you can’t really measure skills, especially soft skills, because they’re too subjective. Like, how do you know if someone can adapt to a changing role? How do you know if someone can learn a tool they don’t know from scratch and do it fast?

I think you can actually get evidence of those skills from someone’s past experience. And for college graduates, that doesn’t necessarily have to be a previous job. It can be their projects, internships, school projects, or even something they built on their own. You can look at what they had to learn, how they handled changes, what problems they had to solve, and what they were actually able to produce.

So I don’t think skills-based hiring means you just have to take someone’s word for it that they’re adaptable or a fast learner. You can still look for evidence. It just might look different for a college graduate compared to someone who’s already been working for 10 years.

Another is the belief that skills-based hiring implies that qualifications no longer matter. This is not true; instead, it simply means that employers are attaching more importance to competency while also taking qualifications into account as part of the applicant’s background information.

During my work as a technical recruiter, I have noticed that candidates who have shown great competency through projects, internships, open-source work, and problem-solving skills have beaten other candidates with excellent qualifications but no proof of putting their knowledge into practice.

You might think checking skills during a rush cuts down on your options, but that wasn’t our experience at Instawork. When we added quick skills checks, our fill rates actually went up. We saw way fewer no-shows and bad fits when things got busy. If you are worried about losing good people, try a simple test. It stops the mismatches without slowing you down.

The misconception to drop is that skills-based hiring means a long list of tools on the resume. Employers didn’t replace “degree required” with “somebody who knows Python as well as ChatGPT.” What they actually replaced it with is: show me you can do the work under real conditions—the practical aspect of what you can actually do for me.

As part of the Dallas Data Science Academy, I watched strong graduates really stall because their materials read like a course catalog. And I watched nontraditional candidates move because one project showed messy data, a wrong first approach, and a decision they could actually defend. The career services folks who only add skill words are preparing people for a posting, not for a hiring manager.

That evidence has changed my view, and it’s pretty simple and repeated. The candidates who get callbacks can walk through a problem they owned, not a stack they studied.

The misconception worth rethinking is that skills-based hiring makes the process lighter for the employer. Taking a degree requirement out of an advert takes a minute. Deciding what you will assess instead, agreeing what a strong answer looks like and getting managers to apply it the same way takes considerably longer.

Where that second part gets skipped, the qualification filter is quietly replaced by manager instinct, which is harder to see and harder to challenge. The shortlist narrows again for reasons nobody has written down, and the organisation believes it has widened access when it has moved the gate.

For graduates and the people advising them, the practical read is that these processes are getting longer at the assessment stage. Career services teams built a lot of support around the CV and the covering letter, and the weight has moved to structured exercises that are harder to rehearse.

The degree didn’t leave skills-based hiring. It moved further back in the process.

I trained as an architect in Milan and spent years teaching before starting a design school in India. Semester after semester, I watched students with genuinely strong work not clear shortlists at firms that described themselves as portfolio-forward. The credential surfaced at the final cut, not the gate. That’s the shift employers, graduates, and career services teams all tend to miss: it moved from filter to tiebreaker. Build the skills. The degree is still deciding the close calls.

The biggest myth I see about skills-based hiring is that applicants do not need a degree. That is not what most clients on our platform are doing. Instead, they are changing what they look at first. Some clients look at proven skills before considering a degree, rather than using a degree as a requirement to get through the door.

What we started to notice was that rather than placing the resume as the first step of the evaluation process, our clients began to place skills evaluations and even a portfolio before the review of the resume. Surprisingly, our clients began to evaluate applicants who lacked a four-year degree but had certifications or project-based work for the same positions they would evaluate traditional applicants.

For people with degrees, this means your degree is still important, but it may not carry as much weight as it did before. For career services, the focus is more on providing clients the opportunity to be able to fill out their skills and not just their education. For employers, this means job postings should focus more on naming the applicable skills, and not just the degree.

From my seat driving AI strategy at a 700-employee financial services company, one misconception about skills-based hiring is that AI has made technical skills less valuable. In practice, AI tool fluency makes it more important to distinguish AI fluency from technical understanding.

To be sure, AI is making technical output easier to produce. That shift, in turn, increases the value of people who understand what a system is doing, why it works, where it can fail, and how to connect it to a real business problem.

I was reminded of this earlier this year during a conversation with computer science majors at the AI3 Summit near Indianapolis. They told me they were wrestling with whether AI coding assistants would render their technical training obsolete.

Searching for your first job is hard enough without worrying that your skills have already become obsolete. The encouragement I shared with those seniors needs to be heard more widely: the rest of the business will continue to depend on technical experts. We can help identify the business need, shape the strategy, and even prototype solutions. But the moment you cannot explain why something works, you limit the value you can provide with what you build. We need people with deep technical expertise to build systems that are safe, scalable, and sustainable.

That said, technical skills alone are no longer enough in today’s workplace. Companies are hungry for employees who can translate business needs into technical solutions. Early-career professionals should study the business—understanding its users, processes, vision, and goals—to maximize the value they provide. Career services professionals can help students articulate the decisions, trade-offs, failures, and lessons behind their projects. This blend of skills broadens their potential for what they can build and the decisions they can make.