Call for Code: Code for good and win big rewards

Call for Code is IBM’s coding-for-good challenge that asks developers to build real software for real crises, then puts $200,000 and serious deployment muscle behind the winner. I’ve watched this competition since 2018, and the short version is this: it’s still running, it’s still legit, and in 2026 it relaunched as Call for Code AI with a sharper focus on artificial intelligence. If you write code and you’ve ever wanted your work to matter beyond a sprint board, this is the hackathon worth your weekend.

The verdict: Call for Code is the most credible tech-for-social-good competition out there. It’s backed by IBM and The Linux Foundation, winners get deployed through real partners (not just a press release), and the grand prize is announced at a United Nations ceremony. Enter if you want impact, mentorship, and a portfolio project that actually ships. Skip it only if you want a quick cash grab with zero follow-through, because this one expects you to build something real.

What changed in 2026: IBM and David Clark Cause relaunched the program as Call for Code AI. The new format adds rapid-response “Spot Challenges” alongside the annual Global Challenge, and the whole thing now centers on deploying AI against urgent problems like human trafficking, climate displacement, and pandemic preparedness. The original disaster-response mission is still there. The toolkit just grew up around watsonx and frontier AI models.

What is IBM’s Call for Code?

Call for Code is a global competition that challenges developers and engineers to build technology that helps people survive and recover from the world’s hardest problems. Think disaster response, climate resilience, public health, and human rights. You build an app, a device, or a platform, you ship it as open source, and the best solutions get funded and deployed with real partners on the ground.

The campaign was created by David Clark Cause, the initiative founded by David Clark to turn developers into change agents. IBM signed on as founding partner in 2018 and has stayed there ever since. The Linux Foundation handles the open-source side, hosting winning projects so they keep living after the trophy gets handed out.

Here’s the scale, because the numbers are genuinely hard to believe. Over eight years, Call for Code has mobilized more than one million developers and technologists across 190+ countries, and they’ve created over 50,000 applications. That makes it the largest sustained mobilization of developers for social good anywhere. It’s tech-for-social-good at a scale no single company could pull off alone, which is why I keep pointing students and junior devs toward it.

Call for Code is supported by IBM’s Code and Response initiative, a multi-year program dedicated to building and deploying open source technologies that take on the world’s biggest challenges.

Is Call for Code still running in 2026?

Yes. Call for Code is alive and running in 2026, and it’s bigger than it was when I first wrote about it. The program didn’t quietly die the way a lot of corporate hackathons do after a few seasons. Instead, IBM and David Clark Cause rebuilt it. As of 2026 it operates as Call for Code AI, a next-generation platform built to put artificial intelligence directly against global crises.

The 2026 version keeps the annual Global Challenge that the program is known for, but it adds rapid-response Spot Challenges: shorter, focused sprints aimed at specific emergencies as they happen. The themes have widened too. Alongside the original disaster-response roots, current focus areas include human trafficking, climate displacement, and pandemic preparedness. If you’ve built anything with AI and automation, the 2026 toolkit will feel familiar, because IBM watsonx and frontier AI models now sit at the center of it.

I’m calling this out plainly because a lot of older articles online still describe Call for Code as a pure disaster-preparedness contest with a Watson cloud stack. That was accurate in 2019. It’s incomplete in 2026. The mission held, the branding shifted to AI, and the prize structure stayed strong. If anything, the open-source-for-good philosophy got more serious, not less.

Who should enter, and how do you win?

Call for Code is built for working developers, students, data scientists, and designers who can ship a working prototype. You don’t need to be at IBM, you don’t need a sponsor, and you don’t need a polished startup. You need a real problem, a clear solution, and a demo that proves it runs. Teams can have up to five members, and you can join solo and find teammates through the community.

After judging dozens of these submissions in my head against what actually wins, the pattern is consistent. The winners don’t have the flashiest UI. They solve a specific, painful, human problem with technology that a non-engineer can understand in one sentence. Here’s how to give yourself the best shot:

1. Pick a narrow, real problem. “Help rural villages detect unsafe drinking water” beats “a platform for global sustainability.” Saaf Water won in 2021 by doing exactly the first thing.
2. Show it working. A clean demo video on YouTube or Vimeo that shows the solution running beats a deck full of mockups every single time.
3. Use the sponsor’s stack on purpose. Recent winners lean into IBM watsonx and watsonx.ai because the judging rewards solutions that can actually be deployed through IBM’s partners.
4. Write a credible roadmap. Judges fund things that can scale past the hackathon. Show what month three looks like, not just demo day.
5. License it open source. Submissions ship under the Apache 2.0 license. Embrace that, because the whole point is open source for good that other people can build on.

If you’re a student, the program has historically run a dedicated university track with its own winner, so you’re not competing head-to-head against ten-year industry veterans. That’s a real advantage, and it’s part of why I push students who want better learning outcomes to enter rather than wait until they feel “ready.”

Past Call for Code winners and themes

The best way to understand what wins is to look at what actually won. Here’s the grand-prize winner for every Call for Code Global Challenge, with the problem each one tackled. Notice the steady drift from disaster hardware toward AI-driven solutions, which tells you exactly where the 2026 program is headed.

A few things jump out when you sit with this list. First, the problems are getting more specific over time, not more grand. Second, AI moved from a nice-to-have in 2019 to the spine of nearly every recent winner, which is the whole reason the 2026 relaunch is named Call for Code AI. Third, students win. Augustana University took 2022 with GardenMate, and Georgia Tech and Michigan students took 2024 with GoBang. You do not need a corporate badge to win this thing.

Prizes and why developers join

The grand prize is $200,000, and it’s awarded at a United Nations ceremony in New York. That UN stage matters more than the cash for a lot of teams, because it puts your project in front of people who fund and deploy this kind of work. The winner also gets implementation support through IBM’s Code and Response initiative, mentorship from IBM engineers, and introductions to potential investors. Runner-up teams receive smaller cash prizes plus an invitation to the global event and ongoing Linux Foundation support.

The money is the headline, but it’s honestly not the reason I tell people to enter. Here’s what you actually walk away with, win or lose:

1. A shipped portfolio project that solves a real problem, which beats any side project nobody uses.
2. Association with IBM, The Linux Foundation, and the UN, which carries weight on a resume and in interviews.
3. Real mentorship from engineers who deploy production systems for a living.
4. A network of developers who care about the same problems you do.
5. Genuine global impact, since winning code gets deployed, not shelved.

That last point is the one I keep coming back to. Most hackathons end with a demo and a pizza box. Call for Code ends with your code in the field. If you’ve spent years shipping features that move a metric by two percent, building something that helps people survive a flood or find clean water is a different kind of satisfying. It’s also, frankly, a great way to boost your own creativity by working on problems you’d never touch at a day job.

How to participate, step by step

Getting in is simpler than it looks. The friction is mostly in your head, not in the signup form. Here’s the path from “I should do this” to a submitted entry.

1. Sign up. Register at the IBM Call for Code developer page. The full rules, deadlines, and starter kits live there.
2. Form your team. Up to five people. If you’re flying solo, use the community channels to find people with complementary skills.
3. Pick a challenge. Choose the annual Global Challenge or jump on a rapid-response Spot Challenge if one is live.
4. Build the solution. Use the starter kits and IBM watsonx tooling. Keep it focused and make sure it runs.
5. Submit your entry. You’ll provide a short solution name, a brief description, a longer write-up, a product roadmap, and a demo video. Each team submits one application, licensed under Apache 2.0.

One honest caution: don’t treat this like a 24-hour hackathon. The strongest entries spend weeks refining a real prototype, and the judging rewards depth over polish. If you want a structured way to skill up before you enter, especially on the cloud side, working through an AWS certification path or IBM’s own watsonx tutorials will make the build phase far less painful.

So that’s the real picture of Call for Code in 2026. It’s still here, it’s bigger, and it’s now AI-first. If you’re a developer who wants your work to mean something, sign up, find a problem that keeps you up at night, and build the thing. The worst case is you ship a project you’re proud of. The best case is your code ends up changing lives, announced from a UN stage.