At the CIO and CTO level the interview changes audience. The people deciding are the CEO, the CFO, the other executives and often the board, and most of them will not judge your architecture. They will judge whether technology in your hands grows the business, protects it, and stays inside the money. Lists of CIO and CTO interview questions cover the topics. What they leave out is what each question is testing, and how to answer a CEO who wants the decision, not the diagram.
I have sat in the CTO seat, and in the CEO seat a CTO reports to. I took a company from startup to a Nasdaq IPO as its founder and CEO, presented to the New Relic board as an executive there, and spent a decade as a managing partner at a venture firm, on boards across 35 deals. The questions below are the ones that decide a technology executive's interview. The method behind every answer (find the question under the question, ask one back, answer with one story, close with "did I answer your question?") is in how to prepare for an executive interview.
Key takeaways
- A CIO or CTO interview is a business interview. Answer in revenue, margin, risk and time, with the technology as the how.
- Expect four audiences: the CEO, the CFO, your future peers and the board. Each one is testing something different.
- Every strategy answer needs what you would stop. Boards trust the executive who can say no.
- AI questions are judgment questions: governance, risk and the business case, not the newest tool.
- Ask the questions that tell you whether the seat can succeed: the board's view of technology, the budget split, who owns data and AI.
The questions at a glance
| They ask | What they are really asking |
|---|---|
| How will technology help us grow? | Growth driver, or cost center? |
| What is your technology strategy for the next three years? | Can you connect a plan to the business, and what would you stop? |
| How do you decide what to prioritize? | Will you make the trade-offs visible, or hide them? |
| How would you turn our priorities into a technology portfolio? | Can you sequence the investments with owners, costs and dates? |
| Tell us about a transformation you led. | Have you done this at our size, and what did you personally decide? |
| Tell me about a time you disagreed with the CEO. | Do you have spine, and can you disagree without damage? |
| What should the board see from technology? | Can you report risk and progress in a way a board can act on? |
| How would you govern AI here? | Will you govern AI, or only adopt it? |
| Describe a cyberattack, outage or failure you owned. | What do you tell the board when it goes wrong? |
| What technical debt would you address first? | Can you tell debt that threatens the business from debt that is just old? |
| In a bad quarter, what would you cut and what would you defend? | Do you know which technology spend protects the business? |
| What is the biggest risk you see here? | Did you do the work, and will you tell us the truth? |
| What would your first 90 days look like? | Will you diagnose before you act? |
Growth and strategy
How will technology help us grow?
What they are really asking: do you see technology as a growth driver or as a cost to manage?
Ask back first: "Where does growth have to come from in the next two years: new customers, new products, or margin?"
How to answer: tie one technology decision you made to a business number: revenue, margin, cycle time, retention. Say what the business needed, what you built or bought to get it, and what moved. Then say how the same thinking would apply to the growth path they just described.
What is your technology strategy for the next three years?
What they are really asking: can you connect a plan to the business, and do you know what you would stop?
Ask back first: "What would the board say technology is for here today?"
How to answer: do not present a strategy for a company you have not seen. Describe how you would build one: the business goals first, the current estate and spend, the two or three bets, and the work you would stop or defer to fund them. Then give one strategy you set somewhere else, and what you stopped to make it work.
How do you decide what to prioritize?
What they are really asking: will you make the trade-offs visible to the executive team, or absorb them quietly?
How to answer: describe the rhythm you used with the other executives to rank work, and one decision where something a peer wanted did not get built, and how you handled it. The panel is listening for whether the business could see and own the trade-off.
How would you turn our priorities into a technology portfolio?
What they are really asking: can you turn a list of wants into a sequence the executive team can fund and track? CIO postings now ask for exactly this: priorities converted into a portfolio of investments, each with an outcome, an owner, a cost, its risks and a date.
Ask back first: "How are technology investments decided and tracked today?"
How to answer: a portfolio you built: how many investments, how you ranked them, what you sequenced first and why, what you deferred, and how you reported progress. Then how the executive team used it to make a decision.
Tell us about a transformation you led.
What they are really asking: have you done this at our size, and what did you personally decide?
How to answer: the scope in one sentence (people, budget, systems, years), the business reason, the two or three decisions that mattered, what went wrong and what you changed, and the numbers at the end. Say "I" for your decisions. A CEO hears "we migrated to the cloud" as a team result; "I decided to move the revenue systems last, and here is why" is yours.
The CEO, the CFO and the board
Tell me about a time you disagreed with the CEO.
What they are really asking: do you have spine, and can you disagree without damage?
How to answer: one real disagreement: what was at stake, how you made your case (privately, with data), what was decided, and how you executed the decision even if it was not yours. A candidate who has never disagreed with a CEO is either new to the room or not telling the story.
What should the board see from technology?
What they are really asking: can you report risk and progress in a way a board can act on?
How to answer: a short set of measures that show trend, not a snapshot; the top risks with what you are doing about each; and the decisions you need from them. Then one example of bad news you brought to a board or an executive team early, and what happened. Boards remember the executive who told them first.
How would you govern AI here?
What they are really asking: will you govern AI, or only adopt it, and can you tell the business case from the demo?
Ask back first: "Where are you today: experiments, a few tools in production, or a mandate from the board?"
How to answer: who owns the decision for each use, how you classify risk, where a person stays in the loop, how data and access are controlled, and how you measure whether it paid off. Then one AI initiative you stopped or reshaped, and why. On the question of how AI will change your role, answer with the risk and the business case as well as the capability.
Risk and the money
Describe a cyberattack, outage or failure you owned.
What they are really asking: what do you do, and what do you tell the board, when it goes wrong?
How to answer: what you knew and when, how you protected customers and operations, what you told the CEO and the board and how fast, the recovery, and the permanent fix. Keep the incident short and the decisions long.
What technical debt would you address first?
What they are really asking: can you tell debt that threatens the business from debt that is just old?
How to answer: explain how you sort debt by what it puts at risk (revenue, security, speed, compliance, customers), then give one piece of debt you paid down and the business result, and one you deliberately left alone.
In a bad quarter, what would you cut and what would you defend?
What they are really asking: do you know which technology spend protects the business?
How to answer: your principles (security, reliability, regulatory obligations and what differentiates the company stay; duplication and low-value work go), then a real quarter where you cut, what you cut, and what it did not break.
What is the biggest risk you see here?
What they are really asking: did you do the work, and will you tell us the truth?
How to answer: one specific risk from what you have read and heard in the process, why it matters to the business, and how you would test whether you are right in the first weeks. Then ask whether they see it the same way. This is a qualifying question in disguise.
What would your first 90 days look like?
What they are really asking: will you diagnose before you act, or arrive with the plan from your last company?
Ask back first: "What would make the first 90 days a success for you and for the board?"
How to answer: who you would listen to first (the CEO, the CFO, the business leaders, your own leaders), what you would measure (spend, risk, delivery, the team), and the one visible problem you would fix early. More in the first 90 days as a new executive.
Have an upcoming big interview?
What CIO and CTO postings are telling you
Read the posting for the question under each line. Current CIO and CTO postings share a core, and the CTO ones add the product:
| The posting says | The question under it | The story to bring |
|---|---|---|
| Own the enterprise technology strategy and roadmap | Can you connect technology to the business plan? | a strategy you set and what you stopped to fund it |
| Turn priorities into a sequenced portfolio with outcomes, owners, costs and dates | Can the executive team track what you promise? | a portfolio you ran and how you reported it |
| Advise the executive team in plain language, with decision-ready recommendations | Will you bring us decisions, not diagrams? | a recommendation you made and the decision it produced |
| Reduce technical debt while improving reliability | Can you change the platform without breaking the business? | debt you paid down and what it unlocked |
| Lead data, AI and governance | Do you have judgment about AI and data? | an AI initiative you governed, measured or stopped |
| Own cybersecurity, disaster recovery and business continuity | What happens on our worst day? | an incident or a recovery test, and what you changed |
| Build and mentor the engineering leaders (CTO) | Will the leaders under you get better? | a leader you developed or replaced |
| Set the product and platform roadmap (CTO) | Can you build what the business sells? | a platform you scaled and what it did for revenue |
The CIO interview and the CTO interview are not the same
The titles overlap, and companies use them differently, so find out which seat this is before you prepare. The usual split:
| CIO | CTO | |
|---|---|---|
| Owns | the company's internal technology: systems, data, security, the operating backbone | the technology in the product: the platform, engineering and how it scales |
| Decides | the CEO and CFO, often the COO | the CEO, often the head of product and the board |
| Tests | business partnership, cost, risk, transformation | product delivery, architecture choices, engineering scale and speed |
| Bring | a transformation that changed how the business runs | a platform or product that grew, and the team you built to run it |
Ask in the first conversation which version they mean. "What does this role own that nobody owns today?" usually answers it.
Questions to ask the CEO and the board
- Where do you see technology in the business three years from now?
- What does the board ask about technology today, and what does it not ask that it should?
- What is the split between running the business and changing it in the technology budget?
- Who owns data and AI decisions today?
- What did the last person in this seat struggle with?
- Twelve months from now, what will have happened for you to say hiring me was the right call?
Ask fewer questions and make them specific. One CIO quoted by CIO.com advised against "What's the culture like?" and suggested asking how the company actually puts its stated operating principles into practice.
Questions people ask
What questions does a CEO ask a CTO candidate?
How technology will help the company grow, the strategy for the next few years and what you would stop, a transformation you led, how you disagree with a CEO, how you handle a failure, and what you would do in your first 90 days.
What questions are asked in a CIO interview?
Business alignment, prioritization, budget and vendors, cybersecurity and resilience, transformation, AI governance, and the first 90 days. The panel scores whether your answers are in business terms with evidence.
How do I prepare for a CIO or CTO interview with the board?
Learn the business like an owner, prepare three or four stories with numbers, know what you would stop as well as start, and prepare a short view of what the board should see from technology. Practice the hard questions out loud.
What is the difference between a CIO and a CTO interview?
A CIO interview usually tests how you run the company's internal technology and partner with the business; a CTO interview usually tests how you build and scale the technology in the product. Companies use the titles differently, so ask.
What questions should a CIO or CTO candidate ask?
What the board asks about technology, the budget split between run and change, who owns data and AI, what the last person struggled with, and what would make hiring you the right call a year from now.
Have an upcoming big interview?
See how I can help you prepare for it.
“I’ve often described working with Ken as being shot out of a cannon. The clarity, confidence, and momentum he helps create can fundamentally change the direction of your career.” Karsten Summerall, 5-star Google review