Beyond the CV: What We Look for in Data & AI Candidates

Ask a candidate about their most successful project and you will usually hear the clean version. Ask where the plan failed, who noticed first and what they told the client, and the conversation changes.  

We use both questions at Elitmind. The first gives us context about experience. The second tells us how someone works when the familiar plan no longer fits the situation.

A CV remains an important part of the process. It shows the scale of previous responsibilities, the technologies a person has used and the choices they have already had to make. Yet recruitment for Data & AI consulting needs a wider view. Our consultants work with changing technology, incomplete information and clients whose real problem may take time to surface. A list of tools cannot predict how someone will respond to that combination.

‍

What does a CV actually show about a Data & AI Candidate?

We read CVs carefully. Technical depth matters in enterprise work, and certain roles require experience that cannot be replaced by enthusiasm alone.

An architect needs to understand the consequences of an architecture decision. An engineer must be able to build work that other people can maintain. A consultant who speaks with senior stakeholders needs enough command of the subject to challenge an assumption without bluffing.

The document still compresses a career into headings and dates. It rewards recognisable job titles and orderly progression, even though many strong careers develop through side moves, difficult assignments or a project that changed someone’s direction.

This is one reason we avoid treating the technology section as a scorecard. It describes a candidate’s current range. It says less about how quickly that range can expand.

‍

What questions does Elitmind ask about Candidate’s Past Projects?

‍

During an interview, we want to understand what happened inside the projects listed on the page.

Who defined the problem? Which decision belonged to the candidate? What changed after the first plan met the client’s reality?

A project can look impressive in a summary while giving one person very little responsibility. A smaller assignment may have required far more judgement.

We pay attention to the way candidates describe other people. Shared credit usually tells us something useful about collaboration. So does the ability to explain a disagreement without turning a former colleague into the villain of the story.

Mistakes are useful territory too. A polished account in which every decision was correct gives us little to work with. An honest example of a missed risk, followed by a concrete change in practice, shows self-awareness and the ability to learn from feedback.

‍

How does Elitmind evaluate a Candidate’s Potential?

‍

We assess potential through evidence, not declarations. A candidate enters an unfamiliar case and we watch how they ask questions that improve the brief.

They explain what they know, state what they would need to verify and make a sensible first decision without pretending that uncertainty has disappeared.

We also look at ownership. In project work, ownership means more than completing an assigned task. It includes raising a risk early, asking for support before the deadline is already lost and staying involved until the issue has a workable next step.

Learning agility matters because the Data & AI field moves quickly. We are interested in how someone learned the last unfamiliar technology, which sources they trusted and how they tested whether they understood it well enough to use in a client setting.

No reliable formula converts curiosity into a hiring score. Structure can make interviews fairer and more consistent. Judgement remains part of the decision.

‍

How do Elitmind’s values show up in interviews?

‍

Project stories give us the clearest evidence of how someone relates to Elitmind’s values.

• One Team appears when a person improves the work around them, shares knowledge and knows when another specialist should join the discussion.
• Getting Things Done is visible in the way they handle a blocked task or a decision nobody has claimed.
• Customer First Mindset shows up when they connect a technical proposal to the client’s operating reality.
• Raising the Bar is harder to hear in a statement about ambition. We look for a change the candidate made after feedback, a standard they introduced or a moment when they challenged their own preferred approach.

‍

These examples are imperfect. Interview performance can favour people who tell stories fluently, while quieter candidates may need more precise questions to show the same capability. A good process has to account for that

‍

How does Elitmind handle candidate communication and feedback?

‍

We give every candidate a clear timeline and honest feedback, whether the answer is yes or no. We speak openly about the role, the project context and the parts of consulting that can be demanding, before a candidate has to decide.

A candidate should know whether the work involves client conversations, shifting priorities or a steep learning curve before making a decision.

Clear communication also matters when the answer is no.

People invest time in preparation and interviews. They deserve an outcome, a realistic timeline and feedback that explains the decision where we can provide it.

This standard is simple to describe and harder to maintain when hiring managers are busy or a project changes at short notice. Those situations do not remove the responsibility; they show whether the process has enough discipline behind it.

‍

Does Elitmind hire candidates without an open role matching their profile?

‍

Yes ,we've hired people before we had the right role for them. When someone shows strong potential but doesn't match the open vacancy, we sometimes consider a different scope or a later opportunity.Another team may need the strengths that the original vacancy would barely use.

There are limits.

A promising profile cannot replace a skill that the current project needs immediately, and we cannot create a suitable role for every person we would like to work with.

The hardest decisions involve candidates who show strong long-term potential while missing a foundation the role needs now. We make those calls individually, because pretending every gap can be solved during onboarding would be unfair to the candidate and the project.

‍

Curious how you'd fit in?

I'm always happy to talk with people who ask good questions, learn fast and aren't afraid to say "this didn't work."

Check our open Data & AI roles and let's start a real conversation.

‍

‍