A Practical Guide to Running Your First Quantum Circuit on IBM Quantum Experience

If you’ve ever stared at a quantum textbook and thought, “When will I actually get to press a button and see a qubit dance?” the moment is now. IBM’s free cloud platform lets anyone with an internet connection launch a tiny quantum program in minutes. In this post I’ll walk you through the whole process—no PhD required, just curiosity and a willingness to make a few mistakes.

Why Try a Real Quantum Circuit Today?

Quantum computers are still in their infancy, but they are already being used to explore chemistry, optimize logistics, and even generate new materials. Running a circuit on a real device gives you a feel for the noise and quirks that simulators hide. It also shows you how quickly the field is moving from theory to practice. Plus, there’s a certain thrill in watching a measurement result that comes from a machine that literally lives in a cryogenic fridge.

Setting Up Your IBM Quantum Account

Create a Free IBM Cloud Account

  1. Go to the IBM Quantum Experience site (just type “IBM Quantum” into your browser).
  2. Click Sign Up and follow the prompts. You’ll need an email address and a password—nothing more exotic than a typical web sign‑up.
  3. Verify your email. You’ll receive a short message with a link; click it and you’re in.

Install Qiskit (Optional but Helpful)

If you plan to write code locally, install Qiskit, IBM’s open‑source quantum SDK. Open a terminal and run:

pip install qiskit

The command works on Windows, macOS, and Linux. If you prefer not to install anything, you can use the built‑in visual composer on the IBM website.

Building Your First Circuit

Choose a Simple Problem

A classic starter is the Bell state—a pair of qubits that become entangled so that measuring one instantly tells you the result of the other. It’s a neat way to see quantum correlation in action.

Using the Visual Composer

  1. After logging in, click Composer on the dashboard.
  2. Drag a Hadamard gate onto qubit 0. This puts the qubit into a superposition of 0 and 1.
  3. Drag a CNOT gate and connect qubit 0 (control) to qubit 1 (target). This entangles the two qubits.
  4. Add a Measure block to each qubit.
  5. Name your circuit “BellDemo” and hit Save.

Writing the Same Circuit in Code

If you like Python, open a new notebook (Jupyter works great) and type:

from qiskit import QuantumCircuit, Aer, execute

# Create a 2‑qubit circuit
qc = QuantumCircuit(2, 2)

# Apply Hadamard to qubit 0
qc.h(0)

# Apply CNOT with qubit 0 as control, qubit 1 as target
qc.cx(0, 1)

# Measure both qubits
qc.measure([0, 1], [0, 1])

print(qc.draw())

Running the print line shows a simple diagram of the circuit. It looks exactly like the visual composer version, just in text form.

Sending the Circuit to a Real Device

Pick a Backend

IBM offers several quantum processors, each with a different number of qubits and error rate. For a first run, choose the smallest device—often labeled something like ibmq_quito. It has 5 qubits and a relatively low error rate, making it forgiving for beginners.

Submit the Job

If you are using the Composer, click Run and select the device. If you are using code, add a few lines:

from qiskit import IBMQ

# Load your IBM account
IBMQ.save_account('YOUR_IBM_API_TOKEN')
provider = IBMQ.load_account()

# Choose the backend
backend = provider.get_backend('ibmq_quito')

# Execute the circuit
job = execute(qc, backend=backend, shots=1024)
result = job.result()
counts = result.get_counts()
print(counts)

Replace 'YOUR_IBM_API_TOKEN' with the token you find on your IBM Quantum dashboard under My Account. The shots=1024 argument tells the machine to repeat the experiment 1024 times, giving you a statistical picture of the outcomes.

Interpreting the Results

When the job finishes (usually within a few minutes), you’ll see a dictionary like {'00': 512, '11': 511}. This means that about half the time the measurement was 00 and the other half 11. The absence of 01 or 10 tells you the qubits are indeed entangled—measuring one instantly fixes the other.

If you see a few stray counts like 01 or 10, don’t panic. Real quantum hardware is noisy; tiny errors creep in. As you move to larger circuits, error mitigation becomes a bigger topic, but for now you can celebrate that the core pattern is there.

Common Pitfalls and How to Fix Them

ProblemWhy It HappensQuick Fix
Job stays in “queued” for a long timeThe chosen device is busy with other usersTry a different backend or run at off‑peak hours (late night UTC often works)
No results, only an error messageAPI token not set correctly or expiredRegenerate the token on the IBM dashboard and update your code
Unexpected counts like 01Measurement error or stray gatesDouble‑check that you only have the gates you intended; use the visual composer to verify

Next Steps: Play, Learn, Iterate

Now that you have a working circuit, experiment! Swap the Hadamard for a Pauli‑X gate and see how the output changes. Add a third qubit and try a GHZ state. Explore the built‑in tutorials on the IBM site; they walk you through algorithms like Deutsch‑Jozsa and Grover’s search.

Remember, the goal isn’t to build a perfect quantum computer on day one. It’s to get comfortable with the workflow: design, submit, read results, and tweak. Each loop teaches you a little more about how quantum hardware behaves in the real world.

Happy hacking, and may your qubits stay coherent!

Reactions
Do you have any feedback or ideas on how we can improve this page?