Join the ASU London Spark Challenge: How Arizona State University Builds Student Community Through Innovation
When more than 20 students gathered at ASU London for a 36-hour hackathon in September, the official goal was to produce AI-driven solutions around a theme of ‘inclusive excellence by design.’ By the time Team Minions accepted the £2,000 first-place prize and confetti fell inside the Tait Building, something less measurable had happened. Strangers from three academic disciplines and multiple countries had become a support network they expect to rely on for the rest of their degrees.
The ASU London Spark Challenge, hosted on the historic Clerkenwell campus of City St George’s, University of London, offers a clear lesson for anyone considering Arizona State University’s UK campus. Innovation events like this do more than generate prototypes. They create the student community that carries people through demanding semesters, complicated group projects, and the everyday uncertainties of studying abroad in a new country.
A Hackathon Designed to Turn Classmates Into Collaborators
Universities build community in many ways: student clubs, orientation weeks, shared housing, and campus traditions. The Spark Challenge took a more direct route. Instead of starting with social mixers, ASU London placed students on teams, handed them a demanding creative brief, and let intense collaboration do the bonding.
The approach reflects a broader principle at Arizona State University, one of the largest public universities in the USA: students connect fastest when they build something together under real constraints. A 36-hour deadline, an unfamiliar AI tool, and a panel of experienced judges create exactly the conditions where teammates stop being classmates and start being trusted collaborators.
Explore what ASU London offers and see how its programs combine an Arizona State University degree with a full London campus experience.
How the 36-Hour ASU London Spark Challenge Works
The format was simple to explain and difficult to execute. Students majoring in computer science, engineering, and business were assigned to four teams and given two days to answer a single challenge brief. The theme, inclusive excellence by design, asked participants to treat accessibility and fairness as core product requirements rather than last-minute additions.
Here is how the event unfolded:
- Team formation: Organizers mixed students from different majors and countries, ensuring each team combined technical and business perspectives.
- Build window: Teams spent roughly 36 hours researching, designing, and prototyping their solutions using the required AI development tools.
- Final pitches: Each team delivered a five-minute presentation to a jury, then answered questions under pressure.
- Awards: The first-place team earned £2,000, second place received £1,000, and two third-place teams each collected £250.
The setting added its own weight. The Tait Building, part of the nearly 300-year-old Clerkenwell campus, gave students a workspace steeped in London history while they worked with some of the newest tools in software development. That contrast — centuries-old architecture housing cutting-edge technology — captures what makes studying at ASU London distinctive.
Working with Kiro, an AI-Powered Development Environment
Every team was asked to build with Kiro, an AI-powered development environment and agentic tool. For readers unfamiliar with the category, agentic AI systems go beyond autocomplete. They can plan tasks, generate and refine code, and manage parts of the development workflow with limited manual input, which allows small teams to move from idea to working prototype far faster than traditional methods allow.
For students, the implications are significant. AI-assisted development lowers the technical barrier to producing a functioning demo, which shifts the real competition toward problem selection, design judgment, and communication. The Spark Challenge results confirmed this: the teams that stood out were not necessarily the ones with the most ambitious code, but the ones that clearly defined a problem and showed the logic behind their solution.
Stoobler: A Student Organization App Born From Real Frustration
The winning entry, Stoobler, came from Team Minions: Ava Livermore, Asmita Madireddy, Luca Tomeo, and Rayna Patel. Their app addresses a problem nearly every student will recognize. Group projects scatter work across too many platforms — one app for the calendar, another for group chats, a third for notes, a fourth for slide decks — and important details slip through the cracks.
Livermore described the pain point plainly. Tracking every app and making sure each teammate has the nitty-gritty details is annoying and inefficient. Stoobler consolidates calendars, chats, notes, and presentations into a single organized view, so a project group can see everything it needs in one place.
The takeaway for aspiring builders is valuable. The strongest student projects rarely come from chasing complicated technology for its own sake. They come from documenting a specific, recurring frustration and solving it cleanly. If you are preparing for a hackathon or a capstone project, start by listing the tasks that genuinely annoy you, then ask whether existing tools fail at any of them.
What the Judges Noticed, and Why It Matters to Students
The jury brought senior perspective from across Arizona State University. It included Michelle Pfund, senior associate dean for education at the W. P. Carey School of Business; Jenny Wong, an instructor in the Ira A. Fulton Schools of Engineering; and John Rome, deputy chief information officer for ASU’s Enterprise Technology unit. Their feedback amounts to a free masterclass in what experienced evaluators look for.
Documentation Tells the Story of Your Thinking
Wong, who described herself as a stickler for documentation, praised Team Minions for its detailed code records and structured activities. Her core message deserves to be memorized by every student: it is not about getting it right the first time; you have to get it right the last time. A first prototype is simply an early iteration in a long development cycle, and clear documentation shows evaluators the logic of your intention — which often matters more than a flawless demo.
Presenting Under Pressure Is a Skill You Build Early
Rome focused on the pitching itself. Standing in front of an audience in your first attempts can feel, in his words, grievously injurious, but that discomfort becomes a durable strength. Everything students practiced in those 36 hours — framing a problem, defending design choices, answering unscripted questions — compounds over a four-year degree and into a career. Students who volunteer for presentations early tend to carry that confidence into interviews, client work, and leadership roles.
Subscribe to ASU News to follow more student stories, research updates, and events from ASU London and every Arizona State University campus.
Why Interdisciplinary Teams Consistently Produce Better Ideas
Pfund highlighted what made this event unusual: participants came from three different disciplines and multiple countries, yet they came together remarkably well. That observation points to a truth about modern product development. Professional software teams are cross-functional by design, pairing engineers who understand feasibility with business minds who understand users, pricing, and market fit.
Students sometimes avoid mixed teams because communication feels harder across disciplines. The Spark Challenge showed the opposite logic at work. A business student’s frustration with juggling five group-project apps became the seed of the winning product precisely because engineers and computer scientists were at the same table to build it. When you form your next team, prioritize complementary skills and shared standards over friendship alone, and set expectations for documentation and communication on day one.
Have questions about studying at ASU London? Write to the admissions team and get answers about programs, housing, and student life in London.
Five Lessons Students Can Apply to Their Next Hackathon
Whether you compete in London, Tempe, or anywhere else, the Spark Challenge offers a repeatable playbook:
- Anchor your project in a real problem. Stoobler won because every judge recognized the frustration it addressed. Specificity beats ambition.
- Document as you build. Notes, activity logs, and readable code let judges see your reasoning, not just your output. It also helps your team recover when something breaks at 3 a.m.
- Design the story, not just the demo. A five-minute pitch is a product in itself. Decide in advance what single idea you want the jury to remember.
- Plan to iterate. Judges rewarded the mindset of continuous improvement. Show where the prototype goes next, and you demonstrate maturity beyond your codebase.
- Treat teammates as long-term partners. The students who bonded fastest built trust through small acts: sharing knowledge, dividing tasks fairly, and listening before deciding.
Have you competed in a hackathon or student challenge? Share your experiences and advice in the comments below to help the next group of participants.
A Student Community Built to Last
By Friday afternoon, the conversation among participants centered less on products and more on friendships. Livermore described an instant connection with her teammates and called them her heart and soul for the duration of the event. Other students said they expect the relationships formed during those 36 hours to last through their remaining three years at ASU London.
The full results tell the story of a competitive but supportive field. Team Kirons — George French, Nadia Ali, Peter King, Zachary Alexander-Abt, and Shelby Connell, a graduate of Scottsdale’s Chaparral High School — earned second place. Team Kasper and Team Noise and Bias in Business tied for third. And if any of these students hit obstacles in future semesters, they now know their Spark Challenge community has their back.
For incoming students, particularly those relocating to another country, that kind of network is not a nice-to-have. It is the difference between surviving a semester abroad and genuinely thriving in it. Shared challenge creates shared identity faster than any orientation session can.
Take the Next Step Toward Studying at ASU London
The Spark Challenge anchored a full opening week at ASU London that included ribbon-cutting celebrations, student showcases in fashion and chocolate design, event management visits to revered London sports venues, and festivities around the Union Jack Classic. Together, these events sketch a picture of what student life looks like on the new campus: academically serious, internationally connected, and built around doing real work in a global city.
If that environment matches your goals, take three concrete steps. Review the degree programs available through ASU London and how they connect to Arizona State University’s schools, including the Ira A. Fulton Schools of Engineering and the W. P. Carey School of Business. Talk to current students or recent participants about the reality of the transition. Then prepare an application that shows how you collaborate, because teams like Team Minions proved that the ability to work across cultures and disciplines is the skill employers remember.
Submit your application to Arizona State University and start building your own student community — in the USA, in London, or wherever your degree takes you.
Community, as the Spark Challenge demonstrated, is not something students wait to receive. It is something they build — one sprint, one prototype, and one teammate at a time.
