The Next Legacy of Hiring May Not Be Another Workflow

We went to TechHR India 2026 prepared to explain a problem.

For two days at People Matters TechHR India 2026 in Delhi, we spoke with CHROs, talent acquisition leaders, technology leaders, founders and people building across different parts of HR.

We expected many of our conversations to begin with the problem we have been thinking about at Aikiyam:

Resumes tell only part of the story.

AI is making it easier to create polished applications at scale.

Recruiters have more information to process, but not necessarily more confidence in what to trust.

And senior interviewers still spend a significant part of their time reconstructing a candidate's context before they can actually evaluate them.

We expected to make that case. Most of the time, we didn't have to.

Leaders were already talking about resume floods. AI-generated applications. The difficulty of knowing what is real. Interviewers spending valuable time figuring out what somebody actually did.

These were not problems we had to persuade people to believe.

They were already living with them.

That changed the nature of many of our conversations.

The question was no longer:

It was increasingly:

And that is probably the most important thing we brought back from TechHR.

Three observations, in particular, made us think more deeply about where hiring may be heading.

1. The problem is common across roles and industries

Many of the newer assessment and AI-led hiring tools seem to start with software engineering.

But something kept happening at TechHR.

We would explain the problem using an engineering example, and leaders from finance, manufacturing, retail, logistics and global capability centres would ask:

That was interesting.

Because the evidence required to understand a software architect is clearly not the same as the evidence required to understand a finance manager, plant leader or operations professional.

The work is different.

The decisions are different.

The outcomes are different.

But the underlying problem is remarkably similar.

A professional may have spent years making decisions, solving difficult problems, managing trade-offs, influencing people and growing through different responsibilities.

Then the hiring process compresses all of that into a resume.

A few pages.

A few bullets.

A few keywords.

The professional has accumulated years of context.

The hiring system receives a document.

That is not an engineering problem.

It is a hiring problem.

2. Trust is becoming part of the buying decision

Another theme appeared in a very different way.

Whenever a conversation moved from “this is interesting” to “how would we actually use this?”, questions about privacy, security and data handling appeared very quickly.

Not at the end.

At the beginning.

One CHRO of a large enterprise explained it simply.

Before his team could seriously evaluate something like Aikiyam, the technology organisation would first need to be comfortable with how candidate data was being handled.

Only then would the business conversation proceed.

That stayed with us.

HR technology has traditionally been discussed primarily in terms of capability.

Does it reduce recruiter effort?

Does it automate a workflow?

Does it improve productivity?

Does it integrate into the systems we already use?

Those questions still matter.

But another question is moving ahead of them:

And increasingly, that question is not being answered by HR alone.

Technology, information security, legal and privacy teams are becoming part of the buying decision much earlier.

This matters especially as AI systems begin working with richer professional information.

Because the more context a system understands about a person, the greater its responsibility becomes.

Trust cannot be something that gets added after the product works. It has to be part of how the product is built.

3. The same problem exists inside the company

The third observation came from the conversations that went beyond recruitment.

When we spoke about the longer-term idea behind Aikiyam — that what we understand about a professional should not disappear after every hiring process — several leaders immediately connected it to a problem they already live with.

Their own employees.

Consider the simplest version first.

An internal opportunity opens. A company may have employed someone for five years — projects delivered, crises handled, colleagues mentored, knowledge accumulated that no external applicant could possibly have.

Yet when the role opens, the organisation often struggles to answer a basic question:

Who inside the company can actually do this?

The information exists. But it is scattered. Some sits with managers. Some is buried in performance systems. Some is in project tools. Much of it lives only in people's memories.

So the employee is represented, once again, by a role, a title, a skills tag, and whatever their current manager happens to remember.

Now consider the harder version.

A new kind of work appears — say, a compliance requirement the company did not have two years ago. There is no obvious internal candidate, because nobody was ever hired for it.

But somewhere in the organisation, someone may have navigated exactly this kind of problem — in a previous role, on a project that never made it onto their job description, in work they did long before this need existed.

A system that only remembers what each person was interviewed for cannot find them.

Because it never captured that part of who they are.

This is the difference that matters.

Most systems remember an employee for the role they were hired into. What organisations increasingly need is an understanding of what a person has actually done — across their whole career, not just the slice that matched a job description.

The person has the experience.

The system has fragments of it.

That is remarkably similar to what happens in external hiring.

External hiring is where the pain is easiest to see. But the deeper problem is the same, inside the company and outside it: how do we understand what someone has actually done — and how does that understanding grow rather than reset?

Hiring may be moving from workflow to evidence

Put these observations together and something starts to become visible.

For years, a large part of HR technology has focused on making the workflow faster — finding, scheduling, assessing, tracking, offering.

Those systems solved real problems, and they will continue to matter.

AI is now making many of those workflows dramatically faster.

But speed creates its own consequence.

When applications become easier to generate, screening has to become smarter.

When candidate communication becomes automated, authenticity becomes harder to judge.

When summaries become instant, we still need to ask whether the underlying evidence deserves our confidence.

The bottleneck moves.

The next problem may not be:

It may be:

That distinction matters.

What hiring teams need is enough context before the interview for human judgement to be spent on the questions that actually matter.

We have started describing this internally in a simple way:

An interviewer should not have to spend the first twenty minutes reconstructing what the candidate worked on.

They should be able to start with:

That is a very different use of human judgement.

But evidence is more than what we capture

Hiring is not a deterministic exercise.

Better evidence does not create certainty.

The goal therefore is to build a system that can think, learn and adapt.

The more interesting opportunity is to build systems that remember:

Every hire produces new evidence. But most hiring systems do very little with it. The hiring process ends when the position is filled.

The learning opportunity begins at exactly that point.

When those outcomes connect back to the evidence available before the decision, something changes. The system starts asking better questions. The next Signal Profile is sharper than the last. Evidence stops being a snapshot and becomes something that compounds.

That is what we mean by a system that thinks, learns and adapts.

Not a system that promises certainty.

A system that helps the next decision begin with more understanding than the previous one.

This is where our own worldview is becoming clearer

TechHR did not fundamentally change what we believe at Aikiyam. It made some parts of it clearer.

We believe the future of hiring will require better evidence before decisions and better learning after outcomes.

We believe resumes will continue to be useful, but that understanding a professional requires looking at the work behind the claims.

We believe uncertainty should remain visible rather than being hidden behind a score.

We believe human judgement should remain firmly in human hands.

We believe what we understand about a professional should grow over time rather than reset with every hiring process.

And if richer professional evidence is going to persist, we believe the professional must have visibility and meaningful control over how they are represented.

Because persistence without trust becomes surveillance.

That is not the future we want to build.

Much of hiring technology so far has helped us find candidates and process them more efficiently.

Perhaps the next chapter will be about understanding them — and making sure that understanding does not disappear.

That is the direction we are building toward at Aikiyam.