How to Get a CTO Job When AI Writes Every CV the Same Way
Photo by Bharathi Kannan on Unsplash
I've been thinking a lot about what AI is doing to our jobs. I've done lots of interviews in my life, and this is the first year I don't really know what exactly I'm looking for in a candidate, no matter what role.
I can only find it in retrospect. When I see it, I know. Knowing it beforehand is very hard.
What surprised me
What stops me has far less to do with technology and coding than I expected. It has far more to do with high-level thinking, language ability, the capacity to summarise and explain, interaction, and empathy.
The first step is the paper
A customer told me that right now it's very difficult, as a buyer, to understand on paper how different companies are doing. Anyone can put together a beautiful slide deck and make it look like they know what they're talking about. You only find out when you meet them.
It's the same with sales, and it's the same with CVs. You still have to pass the first step: someone has to look at a piece of paper and decide whether they want to talk to you. That's hard, because there's a lot of sameness, and honestly, most of the time an AI wrote it. But you can read between the lines whether this person has actually thought about what to put in the CV.
I write with AI too, and this article is no exception. It's still me, the editor. That editorial capability, knowing when something on paper is good and when it isn't, means you have been thinking about it. I've always thought that writing is refined thinking and speaking is refined writing. So if you can think, it shows even when an AI writes for you, because you're the one who decides whether what's on the screen is what you want to convey.
Is there humanity behind it? Does it show your character, your personality? That's the first step.
How do you do that in a CV (which an AI wrote)?
Thinking shows up on paper as clarity. So first of all, you need a very clear opening that describes who you are, clearly and concisely. Always remember that hiring managers don't have a lot of time. They usually review hundreds of CVs at once, in a big, long session, and they might only have a couple of minutes for each, if not less. So they're immediately looking at: who is this person, what do they do, what have they done, and what do they want to do in the future?
When it comes to your work history don't just write that you were responsible for XYZ. That tells me nothing about what you have actually done. Tell me what you achieved, and if you can, give the results, not just the activity. If you gained the company €200,000, or more users in a month or two, that matters more to me than “optimised the pipeline for the ML recommendation”.
Finally (but this could just be my taste) put in the important extracurricular activity you have done. Not that you've been dog sitting, but something that shows what is dearly important to you and has helped you grow. People hire whole people, not automatons who have worked their whole lives and done nothing else. That's the good thing about human beings: we have interests, we have other things we do.
I do triathlon and I say it because I think it tells you a lot about how I think about performance, commitment, long-term thinking, training and preparation, and the way I grow. That doesn't mean everyone has to do triathlon. It can be anything that signals to me that you have a wider, more diverse range of opinions, thinking ability and growth potential than anyone else.
Then meeting in person
And then you meet them, and there is no AI in the room, or at least not yet. That's when it really matters to understand how they think and what experiences they've had.
I remember one that had an impressive CV, on paper, all the titles and all the numbers. Then I dug just a little bit and I found out they'd only been warming the chair. They had not been the one making the decisions. They were a puppet in someone else's hands (often the CEO's). And that's the kind of CTO that really sucks, because as a CTO, or really any executive, you have to make decisions.
Here's how I look for it. I ask people to think of an event or situation from their past and tell me what happened, and how they decided. When someone picks examples that are very thin, it means they have no idea why the decision was taken, or how. If you can't give me an example that shows real experience, you're too thin.
Now the other way around. Someone walks me through the decision, the reasoning, the different alternatives and options they considered, how they rallied people around it, how they consulted this or that opposing faction. They changed their minds three, four, five, six times, and in the end the decision was the best one for everyone in the company, not just for them. Then I can hear, see and feel that they put real effort into making that decision, that they remember it very vividly, and that it meant a lot to them and a lot to the company.
What did you learn when you were wrong?
I also like to ask what people learned when they were wrong. Someone who was never wrong is not really a human being. We all know we're wrong sometimes, and someone who claims otherwise might even be a bit more narcissistic than the average person. But we learn when we make mistakes, or when we see them, and I love to explore how people learn. That learning is the fuel for future growth, and it's also the place where people need to find themselves every once in a while, to remind themselves that they're real and fallible.
And of course you talk about AI
Obviously I can't avoid touching AI in an article or an interview. But first, a personal bit of story: in November 2025 I told a friend I would never trust AI to write a line of code. In January 2026 I was writing code with it. My point is that nobody knows what is going to happen tomorrow with AI, probably not even the guys building it. Whatever the limits are today might not be the limits tomorrow, and that is the interesting part. Hearing different perspectives and ideas about how AI will change our jobs is the most interesting part of the interview for me, and where I learn the most.
When I ask where they think all this is going and they tell me they know, I get suspicious. I'd rather hear what skills they think will be needed, their own and their organisation's. And I'd love to hear someone talk about philosophy or ethics, because it tells me they care about more than the technology.
If you take five things from this
- Open your CV with who you are, what you do, what you have done and what you want next.
- Say what you achieved, with results and not just activities.
- Put in what you do outside work that matters to your growth. People hire whole people.
- Have a decision story ready: the reasoning, the alternatives, who you consulted, how you changed your mind.
- Know what you learned when you were wrong.
- Have a real personal view on AI.
In the end
What I'm really probing for is the capability for introspection, analysis and communication, and an understanding of technology, of course, because we're talking about the CTO position. Not sheer technical prowess, and not just someone who is extremely smart and logical.
Because with AI, we get to experience what it is to really unleash human potential: to connect with other people and build things that were impossible before, at a speed much higher than anything we have experienced in the past.
I'm not a traditional recruiter, and I'm definitely not the big-shot CTO who worked at Google or Netflix. I still don't know exactly what I'm looking for, and I'd like us all to be a bit more conscious of the choices we make when we hire. But writing my way through the tangle of my own thinking is the only way I have to help people in this industry, so here it is.