Can Skills-First Hiring Bring More Women Into AI?
Skills-first hiring is often proposed as a way to widen AI talent pools. Here is where it can help women enter AI roles and where it falls short.
By Amara Okafor, Women in AI Editorial Fellow ยท 2 September 2026
Artificial intelligence is changing faster than most job architectures. That makes rigid hiring criteria unusually risky.
A company that insists every candidate must already have held an identical AI job title may exclude people who can do the work but built their experience through software engineering, data, product, research, analytics, risk or another adjacent discipline.
For women, who are already underrepresented in AI talent pools, that matters.
What skills-first hiring means
Skills-first hiring shifts attention from proxies such as degree subject, prestige of employer or exact previous title toward evidence that a candidate can perform the work.
That evidence might include technical assessments, portfolios, shipped products, research, open-source contributions, domain expertise or practical case exercises.
LinkedIn's Skills-Based Hiring research estimated that adopting skills-first approaches could modestly increase women's representation in AI talent pools while also expanding the overall number of people employers can consider.
Why AI is well suited to this approach
Many current AI responsibilities did not map neatly onto established roles a few years ago.
A software engineer may now spend much of her time building retrieval pipelines. A compliance professional may become the internal lead for AI governance. A product manager may develop deep expertise in evaluating generative AI applications. None of those career histories necessarily contains the exact title an employer is searching for.
Skills-first hiring gives companies a better chance of recognising this adjacent experience.
It can also help career changers
Women returning after career breaks or moving from another sector can be disproportionately disadvantaged by filters based on continuous, linear experience.
AI offers opportunities to combine existing domain knowledge with new technical capability. A healthcare professional who understands clinical workflows and AI evaluation may be more useful to a health technology company than a generalist candidate with a more conventional CV.
But skills-first hiring is not enough
Changing the first screen does not automatically change who gets promoted, sponsored or assigned to high-impact work.
If a company hires a broader group but its senior leadership remains homogeneous, or if important AI projects consistently go to the same networks, representation may improve at entry level without changing the distribution of influence.
There is also a design question: assessments themselves can reproduce bias if they reward familiarity with a narrow style of interview rather than the skills needed for the job.
A better hiring process
For AI roles, employers can improve recruitment by:
defining the actual capabilities required for the first year of the role; removing degree requirements that are not necessary; accepting adjacent technical and domain experience; using work samples that resemble real tasks; separating must-have skills from skills that can be learned on the job; measuring who progresses through each stage of the process.
The result is not lower standards. Done well, it is a more precise definition of standards.
The wider lesson is that AI hiring needs to catch up with AI work. When roles evolve quickly, employers who recruit for yesterday's titles risk missing tomorrow's strongest candidates.
How to apply this research
The useful question is not only what the market is doing, but what the evidence should change for a reader making a decision. Separate structural trends from short-term announcements, compare claims with primary sources where possible and look for the constraints that determine whether adoption can scale.
For organisations, that usually means connecting technology capability with economics, governance, talent, infrastructure and the operating process around deployment. A technically impressive system can still fail to create value if it cannot be integrated, evaluated or trusted inside the organisation using it.
A practical decision framework
When evaluating this topic, consider five dimensions:
Strategic relevance: does it affect an important customer, workflow or competitive advantage? Technical evidence: what has actually been demonstrated rather than promised? Operating readiness: does the organisation have data, integration, skills and ownership? Risk and governance: what could fail and how would the organisation know? Economics: what is the fully loaded cost and what outcome would justify it?
Using the same framework repeatedly makes it easier to compare technologies, vendors and initiatives without being pulled toward whichever announcement is newest.
What to watch next
The AI market is changing quickly enough that static conclusions should be treated cautiously. Watch for evidence of repeatable production deployments, changes in regulation or standards, shifts in enterprise budgets and signs that buyers are consolidating around fewer tools.
We update authority coverage when new primary evidence materially changes the conclusion rather than simply adding another announcement to the page.
Research and update methodology
This guide is designed as decision support rather than a static directory. We prioritise primary sources, official organiser information and first-party research where available, then use reputable secondary analysis to explain market context. Event dates, venues, speakers and sponsorship inventory can change, so forward-looking details should always be confirmed with the organiser before travel or contracting.
We also separate three different kinds of evidence. Confirmed facts are information published by an organiser, regulator, company or other primary source. Market analysis is our interpretation of how those facts affect attendees, sponsors or buyers. Recommendations are judgement calls based on audience fit, operating relevance and the likely value of access. Keeping those categories separate matters because a conference can be large without being useful for a specific reader.
When comparing events, we favour practical signals: who attends, which functions are represented, how much of the programme shows real implementation, whether speakers can discuss outcomes and constraints, and whether networking or sponsorship access is structured enough to create meaningful conversations.
For 2027 coverage, we update pages when material new evidence changes the conclusion. We do not treat an old date, an announced speaker or a historical event format as permanently valid. Readers should therefore use these guides to build a shortlist and then verify the final operational details directly with the relevant organiser.
Practical checklist
Before acting on this research, write down the outcome you are trying to achieve, the evidence you would need to change your view and the people who need to be involved in the decision. Then compare the available options on the same basis rather than allowing each vendor, event or framework to define its own success criteria.
A useful checklist is: audience or customer fit, quality of evidence, operating requirements, governance implications, full cost, expected outcome and the next decision point. That structure keeps the analysis connected to action and makes later review much easier.
Finally, record what would make the recommendation outdated. In a fast-moving AI market, an explicit update trigger is more useful than pretending a guide can remain current indefinitely.