The First Job Problem

Artemis Connection, a strategic consulting firm that works at the intersection of employers, education systems, nonprofits, and government, interviewed nearly 30 employers across manufacturing, technology, financial services, engineering, and the public sector to answer one question: what does it actually take for a high school student or recent college graduate to get hired into a first job and start building a career?

Our findings reframed the problem. Hiring managers are overloaded and they are managing leaner teams and absorbing AI transitions amidst rising uncertainty about business conditions. In that context, employers are not screening young talent for technical brilliance or the “right” degree. They are screening for observable signals that a young person will reduce, rather than add to, their operational burden.

Across our research, we found employers consistently identified five observable behaviors they  look for, before offering a young person their first role.

None of them technical. All of them observable before a candidate walks into their first role.

Understanding why these five behaviors resonate, how employers assess them, and what they mean for the organizations building pathways for young adults, is critical.

Getting a first job has never been harder for young people.

Graduate unemployment for 22-27 year olds hit 5.7% in early 2026, the highest in over a decade, and above the national rate for five consecutive years. AI is compressing the pathways that used to absorb new entrants: research, analysis, drafting, and basic coding roles are increasingly automated before a young person gets the chance to do them.  Affluent families are responding, Bloomberg reported in April 2026 that parents are spending upwards of $50,000 on private career coaches starting as early as freshman year of high school.

Yet those first roles are where careers traditionally start, skills compound, and professional identity is built.

Employers, meanwhile, are operating under significant pressure: leaner teams, AI transitions, and rising uncertainty about business conditions. In that context, hiring an unproven young person is a risk many are reluctant to take. The youngest talent on the market has not yet had the opportunity to build the evidence that lowers that risk. Artemis sought to understand what that evidence looks like, and whether it can be produced before a young person ever walks into their first role.

The volume of certifications, online courses, and self-reported skill sets has outpaced employers' ability to distinguish meaningful from superficial preparation. For hiring managers already stretched thin, credentials have become one more thing to evaluate without confidence, and one that rarely reduces the perceived risk of hiring someone unproven.

A banking executive made the same point from the other direction: someone who got into the workforce early and built real workplace experience would know more, and be more valuable, than a 21-year-old undergrad who had never worked in a bank branch, regardless of their degree.

Formal qualifications become more relevant as roles become senior and specialized. At entry level, employers are looking for something credentials cannot provide: observable evidence that a young person is ready to work.

When Artemis Connection asked employers what actually moves a hiring decision for an unproven young candidate, the answers were consistent across every industry and employer type. Employers are not screening for technical brilliance. They are screening for observable signals that a young person will reduce, rather than add to, their operational burden. Five behaviors surfaced as the most reliable proxies, none of them technical, all of them observable before a candidate walks into their first role.

Employers do not use rubrics or structured assessments for durable skills when assessing the youngest talent on the market. They use evidence sources that let them observe behavior before committing to a hire, and they weight those sources The strongest proxies from most important to least are:

The distinction between strong and weak evidence is the distinction between demonstrated and inferred. Coursework and credentials ask employers to infer performance. Work experience and structured projects demonstrate it.

Employers don't use rubrics or structured assessments for durable skills. They use evidence sources that let them observe behavior before committing to a hire. The distinction between strong and weak is the distinction between demonstrated and inferred.

Employers say yes to young talent when the logistics, risk, and time burden of managing them doesn't land on their desk.

The implication runs in two directions.

The organizations that get this right treat operations as seriously as strategy. A well-designed program that produces skilled young people will still lose employer partners if the day-to-day coordination creates more work than they signed up for. Programs fail not because employers dislike young talent -- they fail because the operational design creates friction. The difference between a program employers return to and one they quietly exit, is almost always operational.

Organizations working to create career pathways for young people have a clear design mandate: produce evidence employers can act on. Our research points to three program elements that consistently move hiring decisions:

The employer relationship requires the same intentionality. Programs that reduce operational friction, build the relationship before requesting a hiring commitment, and start with small structured cohorts are the ones employers return to. The early-career labor market has no shortage of willing young talent. What it lacks is the program infrastructure to make that talent visible at scale.

That infrastructure is what the organizations doing this well have built. And it is what the rest of the market needs to catch up to.