Put “Chief Quantum Officer” on a business card in 2023 and people assumed you had wandered off the set of Star Trek. Put it on one in 2026 and they ask which company you work for. The title crossed from punchline to plausible in about three years.
A good share of the CQO appointments you read about are marketing. When a quantum-hardware startup names a physicist its Chief Quantum Officer, it is usually relabeling the head of research it already had. That is fine, but it is not the same event as a bank or a manufacturer deciding quantum needs an owner in the C-suite. Dismiss the title as hype, though, and you miss the real shift underneath it. For a bounded stretch of years, most large organizations will need someone whose actual job is quantum. Bounded matters here, because the role is built to expire. What follows is the case for it, and the case against the inflated version the hype is selling.
The electricity precedent
The closest historical rhyme is electricity. When Edison switched on the Pearl Street Station in 1882 and lit a patch of lower Manhattan, electric power was as baffling to most businesses as it was valuable. Factories and railroads responded by hiring “chief electricity officers” to build and run their own generating plants and to manage the move off steam. The job was real, and then it vanished. Once electricity became a wall socket and every engineer understood it, a dedicated electricity executive made no sense.
Quantum in the mid-2020s sits about where electricity sat in 1900: powerful, real, and still strange enough that most organizations can’t assess it without help. That rhyme is the strongest argument both for the CQO and for its eventual retirement, and the retirement is the more important half of the point. I trace the full lineage in from Chief Electricity Officer to Chief Quantum Officer, including the Chief Internet Officer and the Chief Data Officer, two more transition titles that did their job and then disappeared.
The real reason it’s happening now
So why now, when a useful quantum computer doesn’t exist yet? Two reasons pull in opposite directions, and the more important one gets the least attention.
The opportunity is real and oversold on timing. IBM, IonQ, and Google all publish roadmaps aimed at commercially useful machines this decade, and serious pilots are running in finance, chemistry, and logistics. But a 2028 roadmap target is a plan, not a result, and a headline qubit count means almost nothing without the error rates next to it. Physical qubits outnumber the error-corrected logical ones that actually run algorithms by a factor of a thousand or more. Half of what a competent CQO does in year one is hold that line against their own vendors and their own board.
The threat is the opposite problem: real, and badly undersold on urgency. A cryptanalytically relevant quantum computer (CRQC), the machine that could break the RSA and elliptic-curve cryptography securing most of the internet, does not exist yet, and the public argument over its arrival date has become a distraction. The date is debatable. The rest isn’t. Adversaries are already copying encrypted traffic to store now and decrypt once the hardware catches up, a tactic the field calls harvest-now-decrypt-later. NIST finalized the first post-quantum standards in 2024: ML-KEM, ML-DSA, and SLH-DSA. Regulators have started writing dates into law, with Australia demanding action by 2030 and the United States, the EU, and the United Kingdom aiming at 2035. Cryptographic migration across a large enterprise takes years and touches systems nobody has a clean inventory of. Active harvesting, fixed deadlines, and slow migrations are why quantum belongs on the board agenda in 2026 no matter where you sit on the Q-Day timeline. You don’t get to wait for certainty about the threat, because the calendar is setting the clock, not the physics. The full opportunity-and-threat case is in the case for a Chief Quantum Officer.
What a Chief Quantum Officer actually does
Strip out the relabeling and the job comes down to five things, only one of which is glamorous.
A CQO sets the quantum strategy: which pilots to run, what to spend, when, and how any of it ties back to the business. They run the outside relationships, because no company builds the whole stack itself, which means choosing among hardware vendors, startups, universities, and national programs and deciding what to buy versus build. They handle talent, both the scarce specialists and the quantum literacy of everyone else. On cryptography, the CQO advises the CISO rather than owning the risk: a real read on how close a code-breaking machine is, help building the inventory of vulnerable encryption, and the push for enough crypto-agility to swap algorithms as the standards move. The risk itself stays with the CISO, who has the cryptography teams, the security operations, and the vendor relationships to carry the migration. And they translate, briefing the board, talking the hype down internally, and making quantum legible to people who will never read a physics paper.
My shorthand for the crypto half is that migration time runs inversely to crypto-agility (the more brittle your cryptography, the longer and more painful the move), and that these programs routinely throw off well over a hundred thousand discrete tasks once you count every certificate, library, and protocol. None of that is exotic. It is project management applied to a domain most executives can’t yet see. The hard part is the person. Someone fluent enough in the physics to call a vendor’s bluff and fluent enough in business to brief a board is rare, which is exactly why so many “Chief Quantum Officers” are researchers with a new line on the org chart. I break the role down in detail, first ninety days included, in the Chief Quantum Officer job description.
Who owns it inside the company
The reflexive objection is that this already belongs to the CTO, or the CISO. In a small company, fine, it does. In a large one, quantum is wide enough that bolting it onto an overloaded executive is how it gets dropped. Two structures work: a CQO reporting into the CTO or CIO as a senior specialist, or a CQO sitting as a peer who owns emerging technology while the CTO owns what’s already in production. Either way the cryptographic risk stays with the CISO, who already owns the cryptography teams, the security operations, and the vendor relationships behind it; the CQO advises. Make those boundaries explicit or the role just manufactures turf fights. I work through the reporting lines and the overlap with the rest of the C-suite in CQO vs. CTO vs. CISO.
Who actually has a CQO in 2026
The appointments are real, and the 2026 list has moved well past quantum startups. Purdue made the physicist Michael Manfra its Chief Quantum Officer in January, handing him oversight of the university’s new quantum degrees. Illinois named Dr. Preeti Chalsani as its first state-level CQO to coordinate quantum development across the region. And the example that should give skeptics pause: at Quantum Computing Inc., Dr. Yuping Huang held the CQO title from 2022 and was promoted to chief executive at the end of 2025. A role easy to dismiss as a glorified science-advisor seat became the path to the corner office. Earlier hires at QuantumBasel and BTQ Technologies fit the pattern: the title lands first in quantum-native firms and the public sector, then moves into the enterprise. I keep a current list at who has a Chief Quantum Officer and track the wider signals at Quantum Observer.
Where quantum bites first
Eventually quantum reaches most of the economy, the way the internet did. Near term, the strongest cases share two traits: heavy computation, and high-value data with a long shelf life. Finance is first, exposed on both the math and the cryptography. Pharma and healthcare come next, because simulating molecules is the rare problem quantum hardware is suited to. Logistics and manufacturing want the optimization; energy and materials want the chemistry; defense and government want all of it, plus the national-security stakes. I go sector by sector in which industries need a Chief Quantum Officer first.
The case against, and a smarter way to staff it
I’d be selling something if I pretended the role were right for everyone, so here are the real objections rather than the strawmen. Quantum has been overhyped for a decade, and plenty of executives are correct to be tired of it. Most early quantum work is defensive and won’t show up in revenue, which makes it a hard budget line to defend. The talent shortage is real, and a CQO who can’t field a sharp technical question, or can’t hold a boardroom, gets exposed fast. The field moves quickly enough that any roadmap is provisional. All of that is true. None of it changes the deadline math, but all of it should shape how you staff the role. I give the objections a real hearing in do you need a Chief Quantum Officer?
For a lot of organizations, a permanent C-suite hire is the wrong structure, which is the conclusion most quantum vendors would rather I not push. The whole point of the role is to make itself unnecessary: get the company quantum-safe and quantum-capable, then hand quantum computing to the CTO as ordinary computing and quantum-safe security to the CISO as ordinary security. A job with an expiration date, in a market where the qualified people are close to impossible to hire full-time, is often a better fit for a fractional or interim mandate than a permanent seat. Senior quantum leadership for the transition, with an end date and named successors written in from the start. I make that case in full in the fractional Chief Quantum Officer, which is, in the interest of disclosure, close to the work I do through Applied Quantum.
So give the role to someone now, and don’t carve it in stone. Name the owner, set a horizon, and put in writing who absorbs the work when quantum stops being special. The electricity executives got to clock out once the lights stayed on. A good Chief Quantum Officer should be planning for the same exit from the first day on the job.