At 27, You're Told You're Too Old to Start

A 27-year-old graduate finds an entry-level role offering training, mentorship, and a real pathway into an industry.

They click to apply and see it: Maximum age, 26.

No chance to explain why they graduated at 27.

We have started using age as a shortcut for ability. Young enough must mean adaptable and full of potential.

That shortcut ignores reality.

University strikes can disrupt academic calendars and delay graduation, sometimes for years. Admission delays can push back the start of a degree. After graduating, many spend years supporting family before they can afford to pursue structured roles. Others try a different path first, then realize where they want to build a career.

None of that automatically makes someone less capable of learning, collaborating, or taking responsibility at work.

Employers need criteria. Graduate programmes are designed for a specific career stage, and managing thousands of applications is real work. Not every requirement is unfair.

But there is a difference between a requirement that predicts performance and one that simply makes screening easier.

An age limit narrows the pool. It doesn't measure how quickly someone learns or how well they work with others.

When the pool narrows like that, everyone loses. A young professional loses access to structured growth. An employer loses someone who could have contributed meaningfully, without ever knowing.

Recruitment should identify who can do the work, not just who fits the easiest profile to screen.

Before setting an age limit for an entry-level role, it helps to ask three questions:

1. What does this role actually require?Can the candidate demonstrate relevant skills, learn quickly, and work with others?
2. Does this requirement predict success?Does being 26 rather than 27 make someone better at the job, or does it just reduce the number of CVs to review?
3. Whose timeline are we punishing?When delays are caused by strikes, admission bottlenecks, or economic realities outside a candidate's control, are we screening for ability or for privilege?

These questions won't remove the need for eligibility criteria. But they can help ensure each condition serves a clear purpose.

Skills may get someone shortlisted. Age shouldn't be the reason they never get the chance.

Where should employers draw the line between reasonable criteria and overlooking capable talent?