Summary
Peter Chapman, CEO of IonQ, is interviewed by Yuval Boger. Peter and Yuval discuss IonQ’s plans to scale their computers and deliver business value, the best application-development partners for quantum customers, IonQ’s new quantum manufacturing facility, his hiring philosophy, and much more.
Key takeaways
- IonQ treats scaling trapped-ion systems as a manufacturing problem, standardizing fabrication and assembly rather than building each machine like a one-off lab experiment.
- Chapman argues IonQ should not try to build every customer application itself, and instead points customers toward software partners who already understand the target industry.
- His hiring approach favors people who can operate across hardware, software, and operations as the company grows, rather than narrow specialists tied to one function.
- Delivering business value depends as much on manufacturing discipline and partner ecosystems as it does on raw qubit count.
Get the full transcript on the Quantum Computing Report site
Transcript
Yuval Boger: Hello, Peter, and thank you for joining me today.
Peter Chapman: Oh, Yuval, thanks for having me.
Yuval: So who are you and what do you do?
Peter: My name's Peter Chapman. I'm the president and CEO of IonQ. A little bit of my background: I've been in the high-tech business for, I guess, 45 years or so now.
I started in the mid-'70s. The very first computer I learned to program on was a PDP-11. So it has been an interesting journey going from the PDP-11 to today's quantum computers in that timeframe.
Yuval: Absolutely, and as a kid, I worked on the PDP-11 as well, so we share that in common.
What made you jump into quantum computing?
Peter: Gee, that's a complicated question. You know, I guess a little bit of ego. When I looked on Wikipedia, that section hadn't been filled out yet. And so I thought to myself, "Well, I'll come and work in quantum computing."
And we're at that place where, you know, I'm sure 25 years from now it will be very full with a bunch of names, and I just wanted to be part of filling out Wikipedia and hopefully be part of the story for quantum computing.
Yuval: Customers usually talk about larger computers and error correction, you know, scaling up existing technologies.
And I've had different guests on the podcast, and everyone is trying to convince me that their technology is the best way to go, whether it's superconducting or trapped ions and so on. How do you answer that question? What are your plans for scaling up the machine?
Peter: That's a great question. First, I'm quite sure that every CEO does exactly that, and I've heard it many times.
And this is not unlike, to be honest, the 1980s in silicon, when everyone was battling each other. Companies were debating whether yield was most important, or transistor count, gate speeds, manufacturing costs. All sorts of different things were being used at that time.
So today the question is how do you get to scale, and when do you need to scale? Because error correction is definitely something that will be needed, but the longer you can hold off on getting to error correction, the better, because error correction is going to have a tax. You're suddenly going to have to consume lots of qubits to be able to do error correction.
So in the NISQ era, the era that we're in right now with these noisy systems, what we're trying to do is eke out enough performance to get to quantum advantage. And that's all about reducing the noise in the system, the error rate, and improving the average two-qubit gate fidelities.
And I want to be careful there too, because what really matters is the average two-qubit gate fidelity, not your best two-qubit gate fidelity. One pair of qubits that does really well does not make an algorithm. You need all of them to do fairly well. So we talk about average two-qubit gate fidelities, and it has this other nice benefit, which is that the amount of error correction you need is a function of the error that you're trying to overcome.
So our goal is to get to roughly 99.99 in native gate fidelities without having to go to error correction, and after that, to push the boundaries using error correction. And that makes us different. Ion traps today have the best gate fidelities in the business.
Yuval: And with regards to scaling, how large do you think a computer needs to get before it delivers enough business value to a sufficiently large segment of customers?
Peter: So there's an academic question, which is: when do you get to a point where you can do things that classical computers can't do? That's one, and for us it's not as interesting. The real question for us is, can our quantum computers and a quantum algorithm provide business value?
And what we're already starting to see, in particular in machine learning, is that even using our existing quantum machines, we can come up with algorithms to run on our hardware that beat the best classical algorithms, even though the hardware is not yet better than the best classical supercomputers.
But I think if you're a customer, you don't care. The academic question doesn't really matter. The question is, do we have a better mousetrap?
Yuval: And to deliver customer value, you need software beyond the hardware. Now, some companies out there have more of a full-stack offering, an army of consultants, a big ecosystem, hardware, and so on.
How do you compete in that market, and what's your view on full stack versus just hardware?
Peter: Sure. So with full stack, there's a full stack up to the application layer. That part of it we excel at. We have an operating system that runs on top of our hardware, and a set of compilers and tools that people might not even know are being used today when they use our quantum computers.
Then above that are the Qiskit layers and the libraries that sit above. IonQ is very unique in that all of our competitors' frameworks run on top of IonQ hardware. I think IonQ is the only place you can go where you can run every one of our competitors' tool sets on top of IonQ hardware, and that's unique.
I mean, you can't get Q# to run on some of these other platforms, as an example, but you can run every one of our competitors' frameworks on ours. So we made a decision not to compete in the language area for now, but instead to make sure that our hardware works well with all the existing software out there.
And people have been anxious to make sure their software works with IonQ hardware, because today you can do things on IonQ hardware that you can't even get close to on the nearest competition.
Yuval: And how about the services layer? I mean, you mentioned machine learning. Machine learning is generic. You'd have to make it specific to a particular customer's problem.
How do you go about doing that?
Peter: Some of it comes from the fact that we have complete software compatibility with all the software platforms out there, so if there's a breakthrough in Qiskit or something, that will work well on our hardware. We also work with the three cloud providers, so whatever it is they're doing, we get the advantage of that.
And we have companies like Accenture that are doing applications, and we work closely with them. In addition, in-house we have a small but growing applications team, and they have been working directly with customers as well.
Yuval: I spoke with one of the industry analysts recently, and he told me there's some concern for customers about working with hardware or quantum software vendors, because they need application-specific expertise.
So if I have a supply chain problem, maybe I should go to a supply chain company, which may or may not use quantum, and not to a quantum software or hardware company. How do you see that?
Peter: Well, it is true. When we looked at this, we ourselves said we can't be experts in everything.
So you do have to figure out what it is you're going to specialize in. We made the conscious decision to focus IonQ's applications efforts on machine learning and chemistry. There are many other areas one could focus on, but at least today, what I would say is you need to have quantum expertise, and you also need some domain expertise to be able to work on these problems.
There's even a little more nuance to this. As I mentioned, I go back to the 1970s. I remember getting my first Apple II with a 6502 processor, and my dad and I were going to do our first video game. My dad was an astrophysicist, and so we decided to do a game called Rock Belter Hounds. It was a space game about the inner solar system.
So we plotted out these ovals on the Apple II that used floating point to represent the planets, and it took hours to generate that oval on an old 6502. Then we replaced all the floating-point math with integer lookups and integer math instead, and it went like this.
And that's kind of where we are with quantum today. The machines themselves are not at a place where you can just throw away lots of qubits. You need to be smart about the algorithms, to take advantage of the hardware and really get down to the iron. It's an unfortunate statement, but it is currently the truth.
What I would say, too, is that we've seen it time and time again: people bring applications that might not run the first time, and then we sit down with them to optimize their algorithms to do a better job of taking advantage of the hardware's capabilities, just the same way we did back on an Apple II some 40 years ago.
So I think it's really important that people who are working on applications work with a hardware vendor, hopefully IonQ, to optimize their particular applications to really get the best performance.
Yuval: One last question on applications.
You've worked with quite a few customers.
Peter: Which—
Yuval: Which case studies are you most proud of?
Peter: Ooh, well, let's see. I'm excited that we've been working with Accenture on a chemistry model for breaking down PFAS, the forever molecules. I like that one simply because it looks like PFAS is a large problem, and we might be able to contribute to the solution.
And that impacts everyone, so that's cool. On a personal basis, I really like the ML stuff, because it's also my background. It's really fascinating to see the advancements going on in ML. We have already shown that we can create ML models, both on the quantum computer and for classical hardware, where the black boxes actually capture more of the signal than you can classically, which is very cool.
The other piece is that we've now seen, in a few examples, that with the features being submitted, we can beat the best classical algorithms with a thousandfold smaller feature set. And that's really interesting. You look at things like ChatGPT; it's super expensive for them to create that model.
So it suggests that maybe with quantum computers, in the future you'll be able to create those kinds of complex models, which today only the world's largest corporations can create, and suddenly everyone will be able to do that, with a much smaller data set. That's really cool as well.
We're kind of democratizing big ML.
Yuval: Do customers worry about power consumption? Is that one of the reasons they might opt to use quantum computers?
Peter: Yeah, we joke, and it's a little bit of an exaggeration, that we run off a standard wall socket. I think it takes a couple of wall sockets to actually run the thing.
But in terms of order of magnitude, the reason we don't build bigger supercomputers today is not because you can't. It's easy to put more Intel processors into a supercomputer. It's that it consumes the power of a small city. So who can afford to run them?
If we're going to get more computational power, we can't have the power consumption be linear, and that is certainly one of the promises. Somebody told me, and I don't know if it's true or not, that some of the largest supercomputers are starting to consume the power of the Hoover Dam.
And if that's true, that's horrific. And clearly there are a lot of statistics showing that a not insignificant portion of the electrical grid in the United States is now powering data centers.
So just in terms of climate change, we might be able to help simply by replacing lots of data centers with quantum computers that consume a lot less electricity.
Yuval: We're recording this episode the week that you announced a manufacturing center. Why do you need a manufacturing center?
What are you manufacturing there, and how many, if I may ask?
Peter: Yes, we announced the opening of a new 65,000-square-foot center in Seattle. The reason we're doing it is that we need to expand our manufacturing operation to meet the future demand we're projecting.
So one is demand. We've run out of space in College Park to build more quantum computers, so we need to expand in that sense. But the other thing is that the group in Seattle is going to be working on the productization of the quantum computers. Many quantum computers today are very fragile, bespoke systems that are lovingly created by physicists, as we joke, with screwdrivers out back.
But for all quantum computers to get to scale, and it doesn't matter if it's ours or superconducting or anything else, sooner or later you can't put more qubits on a chip, so you're going to have to go across multiple QPUs and network them together. That also means you need to be able to reduce the cost of the quantum computer to get to scale. It's the same thing we've done with Moore's Law and classical computers, right?
Today's supercomputer is made up of 20 million processors, so we should be thinking about how we're going to get to a place where there's a data center with thousands of quantum computers, all networked together, all working as one like a supercomputer. And if the cost of those individual units is really expensive, then quantum computing will be like CERN.
A country will be able to afford one. But IonQ's vision is that we want to have thousands of quantum computers. Maybe I'll start to coin the phrase "a quantum computer on every desk," to borrow from Microsoft. So the Seattle team is going to be working on a rack-mounted quantum computer with a much smaller footprint than what we have today.
And also starting to take into consideration things like serviceability. You don't want to be at a place where, if a power supply goes down, you have to rip apart the whole machine. So we're starting to think about those kinds of things, and to start stamping out much larger numbers of quantum computers.
Right now we're working on networking quantum computers, not for communication but for computation, to do entanglement across QPUs. To get that working, you need a lot of quantum computers. How many should you test to say that you've got networking? Hopefully more than two, right? Four?
Ten? I don't know, 100? So to really test that out, you need to build a lot more quantum computers, and that's what this is all about.
Yuval: I want to ask you a hypothetical question, probably the only hypothetical I could ask the CEO of a public company. If you could have dinner with one of the quantum greats, dead or alive, who would that person be?
Peter: Ooh. Well, first, I've had dinner with lots of quantum greats, which has been very interesting. I'm going to go with Feynman himself. My dad went to his lectures, and I was too young at the time. I wish I had had the opportunity to go to his lectures.
That would've been awesome.
Yuval: As we get close to the end of our conversation today, I wanted to ask you about executive hires. What type of people are you hiring at IonQ, and looking to hire as you think about the future?
Peter: We've been very lucky to have a great team today.
If you look, we've picked up people from the best companies and managed to lure away executives from exciting companies like Blue Origin, Google, Facebook, and all the rest. Generally, I have a philosophy similar to where Bill Gates was in the 1990s.
Microsoft was king of the hill in the 1990s, and somebody asked Bill, "Well, what is your secret to success?" And he said, "I hire people, and I trust them to go do the work that I've tasked them with, and I try not to micromanage them. And if I get to a point where I'm micromanaging, we probably have a problem."
So I'm looking to hire people who can take a piece of our business and run with it totally independently, without a lot of oversight on my part. And I've been lucky so far in putting together a team that gets exactly that.
Yuval: And my last question today: what would your advice be to customers on what to do and what not to do when thinking about quantum computers?
Peter: Oh, that's a great question. The question is, when will quantum computers and their applications start to be better than what you have today? You have to make a prediction. You yourself have to predict when you think that will actually be.
Some companies are out there saying quantum computing is 10 or 15 years away, because they don't plan to have hardware for a decade or more. IonQ has produced a roadmap showing that a mere two years from now, we will have 64 algorithmic qubits, meaning you should be able to create applications with roughly 3,600 gates, and we expect that with that number of qubits at that fidelity, you'll be able to exceed what you can do on today's classical machines.
When I was working for Ray Kurzweil, we had a research team that was always working on predicting the future for his books. There were several people doing that, but we also used that information in determining where we would invest our software resources to create applications.
We wanted to do optical character recognition on a cell phone, but the cell phones weren't good enough. The focal length of the camera, the processor, the memory, and the resolution of the camera all had to be much better than what was commercially available.
So we made a prediction that two years hence, somebody would come out with a cell phone that had the hardware we needed. And we said to ourselves, "It'll take two years to create that software, so the time to start working on that application is now." That's what we did, and sure enough, to the trade show, to the month, to the day, Nokia, and this was a while ago, came out with the exact phone we predicted. Our software was ready to go, and that application won Best Mobile Application of the Year at Mobile World Congress.
We were ready for the hardware when it came. So what I would say to customers today is, look at IonQ's roadmap. We've done a very good job of hitting the technical milestones we published several years ago, and we're on track to hit 64 algorithmic qubits roughly two years from now.
It will take two years for people to create production-ready applications. If I were selling classical services and I came to a CEO and said, "Hey, we want to redo your manufacturing system with a classical application," it wouldn't surprise any CEO that it would take two years to write that classical application. We're now within that timeframe.
So if you believe IonQ's roadmap, and we've got a good track record and data behind it now, you're actually already behind, because it's going to take two years plus. This isn't classical. It involves more than just creating a standard application.
You're going to have to find the algorithms. You can't go out to GitHub and download a bunch of algorithms like you can for a classical application. Your team is going to have to create those algorithms. So what I would say now is that large Fortune 1000 companies are already at risk of being behind.
And as time goes by, that will become more critical.
Yuval: Well, our time together went by quickly. Peter, thank you so much for joining me today.
Peter: Oh, thank you for having me. It's been a pleasure.
