Hubbry Logo
HackathonHackathonMain
Open search
Hackathon
Community hub
Hackathon
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Hackathon
Hackathon
Hackathon
View on Wikipedia
from Wikipedia
A Wikimedia Hackathon in Prague

A hackathon (also known as a hack day, hackfest, datathon or codefest; a portmanteau of hacking and marathon) is an event where people engage in rapid and collaborative engineering over a relatively short period of time such as 24 or 48 hours. They are often run using agile software development practices, such as sprint-like design wherein computer programmers and others involved in software development, including graphic designers, interface designers, product managers, domain experts, and others collaborate intensively on engineering projects, such as software engineering.

The goal of a hackathon is to create functioning software or hardware by the end of the event.[1] Hackathons tend to have a specific focus, which can include the programming language used, the operating system, an application, an API, or the subject and the demographic group of the programmers. In other cases, there is no restriction on the type of software being created or the design of the new system.

In addition to creating functional software or hardware, hackathons can help participants develop skills like problem solving, critical thinking, creativity, team work, communication and time management. Hackathons can also lead to formation of new companies, finding innovative solutions to real-world problems, or building a community around particular technology or cause.

Etymology

[edit]

The word "hackathon" is a portmanteau of the words "hack" and "marathon", where "hack" is used in the sense of exploratory programming, not its alternate meaning as a reference to breaching computer security.

OpenBSD's apparent first use of the term referred to a cryptographic development event held in Calgary on June 4, 1999,[2] where ten developers came together to avoid legal problems caused due to export regulations of cryptographic software from the United States.[citation needed] Since then, a further three to six events per year have occurred around the world to advance development, generally on university campuses.

For Sun Microsystems, the usage referred to an event at the JavaOne conference from June 15 to June 19, 1999; there John Gage challenged attendees to write a program in Java for the new Palm V using the infrared port to communicate with other people who are using Palm and register it on the Internet.

In the mid to late 2000s, hackathons became more widespread. Companies and venture capitalists saw them as a way to develop new software technologies quickly and target new areas for innovation and funding. Some major companies were born from these hackathons, such as GroupMe, which began as a project at a hackathon at the TechCrunch Disrupt 2010 conference; in 2011 it was acquired by Skype for $85 million. The software PhoneGap began as a project at the iPhoneDevCamp (later renamed iOSDevCamp) in 2008;[3] the company whose engineers developed PhoneGap, Nitobi, refocused itself around PhoneGap, and Nitobi was bought by Adobe in 2011 for an undisclosed amount.[4]

Structure

[edit]

Hackathons typically start with communication via a presentation or a web page from the hosting organization that mentions the objectives, terms, and details of the hackathon. Developers register to participate in the hackathon and are qualified after the organization screens their background and skills.

When the hackathon event begins, the participating individuals or teams start their programming work. The administrator of the hackathon is typically able to answer questions and offer help when their issues come up in the event.

Hackathons can last several hours to several days. For hackathons that last 24 hours or longer, especially competitive ones, eating is often informal, with participants often subsisting on food like pizza and energy drinks. Sometimes sleeping is informal as well, with participants sleeping on-site with sleeping bags.

At the end of hackathons, there are usually a series of demonstrations in which each group presents their results. To capture the great ideas and work-in-progress often people post a video of the demonstrations, blog about results with screenshots and details, share links and progress on social media, suggest a place for open source code and generally make it possible for people to share, learn from and possibly build from the ideas generated and initial work completed.

There is sometimes a contest element as well, in which a panel of judges select the winning teams, and prizes are given. At many hackathons, the judges are made up of organisers and sponsors. At BarCamp-style hackathons, that are organised by the development community, such as iOSDevCamp, the judges are usually made up of peers and colleagues in the field. Such prizes are sometimes a substantial amount of money: a social gaming hackathon at the TechCrunch Disrupt conference offered $250,000 in funding to the winners, while a controversial[5] 2013 hackathon run by Salesforce.com had a payout of $1 million to the winners, billed as the largest-ever prize.[6]

Types of hackathons

[edit]

For an application type

[edit]

Some hackathons focus on a particular platform such as mobile apps, a desktop operating system, web development or video game development.

Mobile app hackathons like Over the Air, held at Phoenix Park, Ireland, can see a large amount of corporate sponsorship and interest.[7][8]

Music Hack Day, a hackathon for music-related software and hardware applications, is a popular event, having been held over 30 times around the world since 2009.[9] Also Music Tech Fest, a three-day interdisciplinary festival for music ideas bringing together musicians with hackers, researchers and industry, features a hackathon.[10] Similarly, Science Hack Day, a hackathon for making things with science, has been held over 45 times in over 15 countries around the world since 2010.[11]

Hackathons have been held to develop applications that run on various mobile device operating systems, such as Android,[12] iOS[13] and MeeGo.[14] Hackathons have also been held to develop video-based applications and computer games.[15] Hackathons where video games are developed are sometimes called game jams.

"TV Hackfest" events have been held in both London[16] and San Francisco,[17] focusing mainly on social television and second screen technologies. In TV Hackfests, challenge briefs are typically submitted by content producers and brands, in the form of broadcast industry metadata or video content, while sponsors supply APIs, SDKs and pre-existing open source software code.[18]

Hackathons have also been used in the life sciences to advance the informatics infrastructure that supports research. The Open Bioinformatics Foundation ran two hackathons for its member projects in 2002 and 2003, and since 2010 has held 2-day "codefests" preceding its annual conference.[19] The National Evolutionary Synthesis Center has co-organized and sponsored hackathons for evolutionary bioinformatics since 2006.[20][21] BioHackathon[22] is an annual event that started in 2008 targeted at advancing standards to enable interoperable bioinformatics tools and Web services. Neuroscientists have also used hackathons to bring developers and scientists together to address issues that range from focusing on a specific information system (e.g., Neurosynth Hackathon[23] and the Allen Brain Atlas Hackathon[24]) and providing reserved time for broad scientific inquiry (e.g., Brainhack),[25][26] to using specific challenges that focus hacking activity (e.g., HBM Hackathon).[27]

There has been an emergence of 'datathons' or data-focused hackathons in recent years.[28][29][30] These events challenge data scientists working with others attending to together use creativity and data analysis skills and platforms to build, test and explore solutions and dashboards which analyse huge datasets in a limited amount of time. These are increasingly being used to deliver insights in big public and private datasets in various disciplines including business,[31] healthcare[32][33] news media[34] and for social causes.[35]

Using a specific programming language, API, or framework

[edit]

There have been hackathons devoted to creating applications that use a specific language or framework, like JavaScript,[36] Node.js,[37] HTML5[38] and Ruby on Rails.[39]

Some hackathons focus on applications that make use of the application programming interface, or API, from a single company or data source. Open Hack, an event run publicly by Yahoo! since 2006 (originally known as "Hack Day", then "Open Hack Day"), has focused on usage of the Yahoo! API, in addition to APIs of websites owned by Yahoo!, like Flickr.[40] The company's Open Hack India event in 2012 had over 700 attendees.[41] Google has run similar events for their APIs,[42] as has the travel guide company Lonely Planet.[43]

The website Foursquare notably held a large, global hackathon in 2011, in which over 500 developers at over 30 sites around the world competed to create applications using the Foursquare API.[44] A second Foursquare hackathon, in 2013, had around 200 developers.[45] The IETF organizes Hackathons for each IETF meetings which are focused on IETF Internet Draft and IETF RFC implementation for better inter-operability and improved Internet Standards.[46]

For a cause or purpose

[edit]

There have been a number of hackathons devoted to improving government, and specifically to the cause of open government.[47] One such event, in 2011, was hosted by the United States Congress.[48] Starting in 2012, NASA has been annually hosting the International Space Apps Challenge.

In 2014, the British government and HackerNest ran DementiaHack,[49] the world's first hackathon dedicated to improving the lives of people living with dementia and their caregivers.[50][51] The series continues in 2015, adding the Canadian government and Facebook as major sponsors.[52]

The Global Game Jam, the largest video game development hackathon,[53] often includes optional requirements called 'diversifiers'[54] that aim to promote game accessibility and other causes.

VanHacks is an annual hackathon that is part of Vancouver Startup Week.[55] The focus of the hackathon is creating solutions for local non-profit organizations from the Vancouver area over the course of 36 hours. VanHacks was created in 2016 by TTT Studios.[56][57]

Various hackathons have been held to improve city transit systems.[58] Hackathons aimed at improvements to city local services are increasing, with one of the London Councils (Hackney) creating a number of successful local solutions with a two-day Hackney-thon.[59] There have also been a number of hackathons devoted to improving education, including Education Hack Day[60] and on a smaller scale, looking specifically at the challenges of field work based geography education, the Field Studies Council[61] hosted FSCHackday.[62] Random Hacks of Kindness is another popular hackathon, devoted to disaster management and crisis response.[63] ThePort[64] instead is a hackathon devoted to solving humanitarian, social and public interest challenges. It's hosted by CERN with partners from other non-governmental organizations such as ICRC and UNDP.

In March 2020, numerous world-wide initiatives led by entrepreneurs and governmental representatives from European countries resulted in a series of anti-crisis hackathons Hack the Crisis, with first to happen in Estonia,[65] followed up by Poland,[66] Latvia, and Ukraine. Beginning in 2020, the Michal Sela Forum has run hackathons to develop technology to help prevent domestic violence.[67]

As a tribute or a memorial

[edit]

A number of hackathons around the world have been planned in memory of computer programmer and internet activist Aaron Swartz, who died in 2013.[68][69][70][71]

For a demographic group

[edit]

Some hackathons are intended only for programmers within a certain demographic group, like teenagers, college students, or women.[72]

Hackathons at colleges are usually annual or semiannual events that are open to college students at all universities. They are often competitive, with awards provided by the university or programming-related sponsors.[citation needed]

PennApps at the University of Pennsylvania was the first student-run college hackathon; in 2015 it became the largest college hackathon with its 12th iteration hosting over 2000 people and offering over $60k in prizes.[73][74] The University of Mauritius Computer Club and Cyberstorm.mu organized a Hackathon dubbed "Code Wars" focused on implementing an IETF RFC in Lynx in 2017.[75][76]

Bitcamp, held at the University of Maryland, College Park since 2014, is another large hackathon with over 1,000 high school and college students attending each year.[citation needed]

ShamHacks at Missouri University of Science and Technology is held annually as an outreach activity of the campus's Curtis Laws Wilson Library. ShamHacks 2018[77] focused on problem statements to better quality of life factors for US veterans, by pairing with veteran-owned company sponsors.[78]

For internal innovation and motivation

[edit]

Some companies hold internal hackathons to promote new product innovation by the engineering staff. For example, Facebook's Like button was conceived as part of a hackathon.[79]

To connect local tech communities

[edit]

Some hackathons (such as StartupBus, founded in 2010 in Australia) combine the competitive element with a road trip, to connect local tech communities in multiple cities along the bus routes. This is now taking place across North America, Europe, Africa and Australasia.[80]

Code sprints

[edit]
Not to be confused with Scrum (software development) § Sprint.

In some hackathons, all work is on a single application, such as an operating system, programming language, or content management system. Such events are often known as "code sprints", and are especially popular for open source software projects, where such events are sometimes the only opportunity for developers to meet face-to-face.[81]

Code sprints typically last from one week to three weeks and often take place near conferences at which most of the team attend. Unlike other hackathons, these events rarely include a competitive element.

The annual hackathon to work on the operating system OpenBSD, held since 1999, is one such event; it may have originated the word "hackathon".[citation needed]

Datathon

[edit]
See also: Data science competition platform, InnoCentive, Comparison of numerical-analysis software, List of statistical software, Comparison of deep learning software, Machine learning software, List of numerical libraries, List of information graphics software, Data mining software, Open-source Cypherpunk software, and List of data science software

A datathon is a competitive event similar to a hackathon, but with a focus on analyzing and integrating large datasets rather than building software or hardware solutions. Participants work individually, in teams, or as an online event to solve data-driven challenges within a set time frame, often using statistical analysis, numerical analysis, data mining, data visualization, algorithms, deep learning, and machine learning. Datathons are commonly organized by universities, companies, and data science communities. They are widely used in fields such as business analytics, health informatics, fin tech, and policy analysis, and are popular formats for promoting data literacy and recruitment for data science roles. Datathons typically culminate in presentations of findings, where solutions are judged based on accuracy, insight, creativity, and impact. Winners can receive prizes or scholarships.[82][83][84]

Well-known datathons include:

Criticism

[edit]

Over the years hackathons have come under severe criticism, with multiple observers questioning the adequacy of hackathons to deliver impactful technological solutions. A major part of the reserve towards hackathons has to do with the lack of viability and sustainability of solutions they develop,[86][87][88] as clearly shown by recent empirical research. A study examining 11,889 U.S. based events revealed that only seven percent of projects had any activity six months after the hackathon ended.[89] Another global study found that only about five percent of all projects developed during hackathons continued for more than five months.[90] Hackathons have been thus associated with the production of short-lived software products often denominated as vaporware.[91][92] Hackathons have been equally criticized for their failure to contemplate the complexity of issues that they seek to solve, developing technologies that do not address underlying societal and political causes of a problem.[93][94][95] The use of hackathon participants as de facto unpaid laborers by some commercial ventures has been criticized as exploitative.[96][97]

High-profile hackathons have also been the object of controversies. A team at the September 2013 TechCrunch Disrupt Hackathon presented the TitStare app, which allowed users to post and view pictures of men staring at women's cleavage.[98] TechCrunch issued an apology later that day.[99] A November 2013 hackathon run by Salesforce.com, billed as having the largest-ever grand prize at $1 million, was accused of impropriety after it emerged that the winning entrants, a two-person startup called Upshot, had been developing the technology that they demoed for over a year and that one of the two was a former Salesforce employee.[5] Major League Hacking expelled a pair of hackers from the September 2015 hackathon Hack the North at the University of Waterloo for making jokes that were interpreted as bomb threats, leading many hackers to criticize the organization.[100] As a result of the controversy, Victor Vucicevich resigned from the Hack the North organizing team.[101]

Notable events

[edit]
See also: Imagine Cup

See also

[edit]
MediaWiki has documentation related to: Hackathons

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Hackathon

View on Grokipedia
from Grokipedia
A hackathon is an event in which computer programmers and other specialists collaborate intensively to create functional software prototypes or solve technical problems over a condensed timeframe, typically 24 to 48 hours. These gatherings emphasize rapid , with participants forming teams to ideate, , and present working solutions, often judged on , feasibility, and impact. The term "hackathon" derives from the portmanteau of "hack," referring to creative programming, and "marathon," denoting endurance, with its first documented use tracing to the late in open-source communities. It gained prominence following a 1999 cryptographic development sprint organized by developers in , , marking an early formalized instance of such collaborative coding marathons. Over time, hackathons proliferated through tech companies and universities, evolving from internal innovation exercises—such as those at in the early 2000s—to widespread public events fostering cross-disciplinary teamwork. Hackathons drive tangible outcomes, including prototype advancements that have spawned commercial successes like mobile apps and startups, while honing participants' skills in problem-solving and agile development under pressure. Notable examples encompass corporate-hosted challenges yielding internal tools and global competitions addressing real-world issues, though their efficacy depends on clear objectives to avoid superficial outputs amid fatigue and time constraints.

Etymology and Definition

Core Definition

A hackathon is an event in which computer programmers and often participants from other disciplines collaborate intensively over a relatively short period, such as 24 to 48 hours, to build or improve software projects, prototypes, or solutions to designated challenges. The format emphasizes rapid development, where teams form spontaneously, iterate on ideas under time pressure, and present functional outputs, distinguishing it from standard software development cycles that lack such constraints. Core to the hackathon model is its focus on collaborative problem-solving, typically around themes like innovation, social issues, or applications, with provisions for workshops, , and judging to evaluate feasibility, , and impact. Unlike casual coding sessions, hackathons impose deadlines to simulate high-stakes environments, encouraging participants to prioritize minimum viable products over polished code. While originally centered on , modern hackathons frequently incorporate interdisciplinary elements, such as , , or hardware integration, to address multifaceted problems, though the emphasis remains on tangible, demonstrable results within the event's timeframe. This structure promotes skill-building and networking but can lead to uneven outcomes due to varying participant expertise and fatigue from extended sessions.

Term Origin and Evolution

The term "hackathon" originated as a portmanteau of "hack," denoting creative or exploratory programming rather than malicious intrusion, and "marathon," emphasizing sustained, intensive effort. This linguistic fusion captured the essence of collaborative, time-bound coding sessions focused on rapid development and problem-solving. The term was coined by Provos, a key contributor to the operating system project, in reference to a cryptographic development event organized by OpenBSD developers in , , on June 4, 1999. Approximately ten participants gathered to enhance encryption software for the project, marking the earliest documented use of "hackathon" to describe such an assembly; this event addressed technical challenges amid legal constraints on exports at the time. Initially confined to open-source communities like OpenBSD, the term denoted informal, goal-oriented gatherings for advancing specific software initiatives without the competitive elements that later became common. Over the early 2000s, the term's usage proliferated beyond niche circles as software companies adopted similar formats to accelerate , evolving from ad hoc developer meetups to structured events. By the mid-2000s, corporations such as Yahoo and integrated hackathons into their cultures, applying the term to sponsored, prize-driven competitions that encouraged cross-functional teams to solutions, thus broadening its connotation to encompass entrepreneurial and interdisciplinary collaboration rather than solely code refinement. This shift reflected growing recognition of hackathons' utility in generating ideas under time pressure, with the term eventually extending to non-technical domains like design and social impact by the .

Historical Development

Origins in Open-Source Communities

The term "hackathon," a portmanteau of "hack" and "marathon," emerged in the community of the project, where developers sought efficient ways to collaborate on code improvements despite geographical dispersion. In the months preceding June 1999, either project leader or developer Niels Provos coined the word to describe focused, in-person gatherings for intensive programming sessions, distinguishing them from routine online contributions. This innovation addressed the limitations of distributed development in open-source projects, where remote communication via and CVS () often slowed progress on complex tasks like security enhancements. The inaugural hackathon occurred on June 4, 1999, in , , , organized by developers to prioritize cryptographic code development for the operating system, known for its emphasis on security and code auditing. Approximately 10 participants convened for several days, working without the interruptions of daily life to port and refine code, resulting in tangible advancements such as improved modules. Unlike competitive modern events, this gathering lacked prizes or judging; its goal was pure productivity, reflecting open-source ethos of voluntary, merit-based contribution over commercial incentives. OpenBSD's model proved effective, leading to recurring hackathons—typically two to three per year by the early —hosted at various global locations to accommodate international contributors. These events facilitated porting OpenBSD to new architectures, auditing for vulnerabilities, and integrating hardware support, yielding outputs like the first OpenBSD ports to and platforms. The format's success in accelerating development influenced other open-source communities; for instance, the Open Bioinformatics Foundation adopted similar "codefests" by 2002 for projects like BioPerl and BioJava, adapting the intensive collaboration to bioinformatics software. This dissemination underscored hackathons' utility in open-source ecosystems, where rapid iteration and drive quality without hierarchical oversight.

Expansion into Mainstream Events

The adoption of hackathons by major technology companies marked a pivotal shift from their origins in open-source software development to structured tools for internal innovation and product prototyping. In June 2006, Yahoo hosted its first company-wide internal Hack Day at its Sunnyvale campus, inviting all employees to collaborate on experimental projects over a 24-hour period, which built on smaller, team-specific events and emphasized rapid experimentation without formal oversight. This was followed shortly by the inaugural Yahoo! Open Hack Day on September 29-30, 2006, which opened the company's headquarters to external developers, fostering community-driven hacks integrated with Yahoo's APIs and platforms, and setting a precedent for "brand hackathons" that leveraged corporate resources for broader participation. Facebook accelerated this trend with regular internal hackathons starting in 2007, where engineers prototyped features that later entered production, such as the "Like" button and Timeline, demonstrating how these events could yield deployable innovations amid rapid scaling from startup to enterprise size. By the late , venture capitalists and corporations viewed hackathons as efficient mechanisms for accelerating software development and talent scouting, leading to their proliferation beyond tech firms to include events sponsored by non-tech entities like governments and financial institutions seeking digital solutions. This mainstream integration has persisted, with over 80% of Fortune 100 companies now incorporating hackathons to drive , often as recurring internal or sponsored events that prioritize measurable outcomes like viability over pure experimentation. More than half of these corporate hackathons are repeated annually, reflecting their causal role in sustaining competitive edges through and cross-functional problem-solving, though empirical studies note variable long-term code reuse rates from such events.

Post-2020 Adaptations and Trends

The accelerated the adoption of virtual hackathons, transforming traditional in-person events into remote formats to comply with lockdowns and enable continued innovation. In early 2020, organizations rapidly pivoted, with MIT's Hacking Medicine program shifting from fully in-person to 100% virtual healthcare hackathons, enhancing global accessibility and participant scale while maintaining event frequency. Specialized virtual events proliferated, including MIT HealthHACK on May 13, 2020, which convened international teams to develop prototypes addressing challenges like diagnostics and disruptions. initiatives, such as those documented by AWS in August 2020, leveraged virtual formats to crowdsource solutions for virus-related issues, demonstrating hackathons' utility in crisis response without geographic constraints. Following the pandemic's peak, hybrid hackathons emerged as a dominant adaptation by 2023–2024, combining in-person collaboration with online participation to balance immersion and inclusivity. A 2025 analysis of three hybrid events identified logistical hurdles like synchronized scheduling and equitable resource access but concluded they expanded engagement by accommodating varied participant needs. Notable examples include the Princeton Open Hackathon from June 4–14, 2024, hosted in hybrid mode with collaboration, focusing on accelerator programming, and the SIIM Hackathon in 2024, which marked the society's first hybrid iteration for imaging informatics projects. These formats persisted due to their proven ability to sustain post-event project momentum, as evidenced by comparative studies showing hybrid setups fostering equivalent educational outcomes to in-person ones. Integration of has marked a key trend since 2023, with hackathons increasingly centered on AI prototyping to capitalize on rapid technological advances. In August 2025, initiated a $100,000 AI hackathon challenging participants to build prototypes using AI for unstructured data processing, underscoring enterprise focus on practical AI deployment. Corporate internal hackathons have driven AI adoption by prototyping reusable frameworks and identifying trends, with reports indicating productivity gains of 20–45% from generative AI tools in development workflows. By 2025, AI-themed events like those listed by proliferated, emphasizing ethical integration and real-world applications, though concerns over over-reliance on AI for core coding have surfaced in participant feedback. This evolution positions hackathons as accelerators for AI innovation, extending beyond software to interdisciplinary challenges in sectors like healthcare and .

Event Format and Mechanics

Typical Timeline and Logistics

Organizing a hackathon requires meticulous pre-event preparation to ensure smooth execution. This involves establishing clear rules and guidelines to prevent disputes, defining target audiences for effective marketing and promotion, and accurately estimating resource needs, including securing sponsors, to avoid team burnout or logistical shortfalls. Hackathons generally last 24 to 48 hours, frequently structured over a weekend to accommodate participants' schedules, beginning on Friday evening or Saturday morning and concluding by Sunday afternoon. This format allows for continuous prototyping under time pressure while minimizing disruption to standard work or academic routines. The event timeline typically opens with participant check-in and registration, often starting at 6:00 PM on Friday, followed by an opening ceremony around 7:00 PM that outlines rules, introduces sponsors, and may include initial workshops or team formation for unpaired attendees. Hacking then commences shortly thereafter, extending through the night with provided meals, snacks, and occasional mini-events like lightning talks or networking sessions to sustain energy. Saturday focuses on sustained development, incorporating breaks for catered meals, sessions, and recreational activities to combat fatigue, while Sunday morning signals the end of hacking—usually by noon—transitioning to demonstrations, judging, and announcements by early afternoon. Logistically, organizers prioritize venues with high-capacity capable of supporting hundreds of devices simultaneously, ample power outlets, and sufficient space for teams to collaborate, often at universities, conference centers, or corporate facilities. Food and beverages are essential, with schedules allocating time for multiple meals and hydration stations to maintain productivity during extended sessions; some events provide nap areas or shuttles for off-site . Technical infrastructure includes submission platforms like Devpost for project uploads, and health protocols such as enforcement and basic medical support, particularly for in-person gatherings. Virtual or hybrid variants adapt by using tools like Zoom for ceremonies and for collaboration, though they demand robust internet backups to prevent disruptions.

Team Composition and Roles

Hackathon teams generally comprise 2 to 5 members, with many events capping participation at 4 to promote focused and efficient during the constrained timeframe. This size allows teams to divide tasks effectively without excessive coordination overhead, as larger groups risk diluting contributions and complicating consensus on project direction. Teams often form either prior to the event, through networks of colleagues or prior collaborations, or on-site via sessions where participants pitch skills and interests to assemble complementary groups. Pre-formed teams benefit from established trust and aligned goals, while ad-hoc formations foster serendipitous pairings but require rapid rapport-building to align on objectives within hours. Core roles typically include frontend developers, who handle user-facing interfaces and integrate visual elements; backend developers, responsible for server-side logic, , and integrations; and UX/UI designers, who prototype wireframes and ensure intuitive user experiences. Additional positions frequently encompass project managers to oversee timelines, resolve blockers, and coordinate demos, alongside domain experts providing theme-specific insights, such as industry knowledge or regulatory awareness, to ground prototypes in practical viability. This role specialization mirrors pipelines, enabling parallel workstreams: ideation and upfront, followed by and testing, culminating in a polished pitch. Empirical outcomes from events indicate that balanced teams with technical depth and non-coding support outperform homogeneous coder groups, as diverse inputs enhance and presentation quality.

Judging Criteria and Prizes

Judging in hackathons typically evaluates projects across multiple dimensions to assess both feasibility and broader value, with criteria varying by event but often emphasizing innovation, technical execution, , and potential impact. Organizers like Devpost commonly weight factors such as the quality of the idea ( and ), (technical depth and functionality), ( and ), and potential impact ( and real-world applicability), scored on scales like 1-5 by panels of industry experts, sponsors, or peers. Technical measures the sophistication of code, algorithms, or integrations, while functionality tests whether the (MVP) operates as demonstrated, often verified through live demos or submitted videos limited to 2-3 minutes. Variations exist based on thematic focus; for instance, technology-specific hackathons may prioritize open-source contributions or adherence to platform constraints, as seen in events judging on groundbreaking use of APIs or hardware. Feasibility considers post-hackathon sustainability, including resource needs for scaling, whereas originality penalizes derivative ideas lacking novel twists. Judges, recruited from sponsors or tech professionals, often review submissions asynchronously via platforms like Devpost, aiming for multiple evaluations per project to mitigate bias, with final selections announced during closing ceremonies. This process favors polished presentations that clearly articulate problem-solving, though empirical analyses indicate that high scores correlate more with executable prototypes than conceptual ambition alone. Prizes serve as incentives for participation and talent attraction, commonly structured in tiers for top placements (e.g., 1st, 2nd, 3rd) plus category-specific awards from sponsors. Cash awards predominate, ranging from $1,000 for grand prizes in collegiate events like TreeHacks to pools exceeding $1 million in large-scale competitions such as Bolt's World's Largest Hackathon, distributed across global, regional, and bonus categories. Non-monetary prizes include hardware (e.g., smart glasses, hoodies), software subscriptions, mentorship sessions, or incubation access, as in Microsoft AI hackathons offering $12,000 alongside development opportunities. Sponsor-driven awards, such as sustainability or education prizes, tie to event themes, providing exposure via media or investor pitches rather than direct funding. While prizes boost engagement, data from platforms show only 1-5% of submissions win, underscoring their role as selective motivators rather than guaranteed outcomes.

Variations and Formats

Technology-Specific Hackathons

Technology-specific hackathons focus on narrow technological domains, requiring participants to prototype solutions using predefined tools, frameworks, or paradigms such as , , or . These events differ from general hackathons by mandating adherence to the specified technology stack, which concentrates expertise and resources to accelerate domain-specific advancements. Organizers often supply proprietary APIs, datasets, or hardware to facilitate rapid development within the constraints. Early instances emerged from open-source communities, exemplified by the 1999 OpenBSD hackathon in , , where developers collaborated exclusively on enhancing the operating system's encryption features over several days. This model influenced subsequent technology-centric gatherings, such as Yahoo's 2006 Hack Day, which centered on Yahoo's web technologies to prototype internal innovations. As specialized fields matured, dedicated events proliferated; blockchain hackathons gained traction post-2017 cryptocurrency surge, with platforms like Devpost hosting competitions partnered with and foundations to build decentralized applications. In , events like the Internet of Agents Hackathon and Google Cloud's GKE Turns 10 Hackathon—held in 2025—task teams with applying models or container technologies to real-world problems, often yielding prototypes for scalable AI infrastructure. DoraHacks coordinates multi-domain hackathons for , AI, , and space technologies, including the BUIDL AI 3.0 event, which attracted builders to integrate frontier tools like agentic systems. Internal corporate variants, such as AI-focused hackathons, direct employees toward business challenges using company-specific tech stacks, promoting proprietary solutions over broad experimentation. These hackathons yield higher technical depth but narrower applicability, with success measured by feasibility within the tech's limitations rather than sheer novelty. Participants report enhanced skill specialization, though outputs frequently remain proofs-of-concept due to time constraints and integration hurdles inherent to rigid tech mandates.

Thematic and Purpose-Driven

Thematic hackathons constrain participant projects to predefined challenges or domains, such as environmental sustainability or , aiming to channel collaborative energy toward targeted societal or sectoral problems rather than open-ended . This format emerged as an from general technology-focused events, emphasizing alignment with organizer goals like or nonprofit missions, often incorporating expert mentors from relevant fields to guide ideation. Purpose-driven variants prioritize measurable outcomes, such as prototypes addressing , with events like the Thomson Reuters Social Impact Hackathon in 2025 pairing 40 nonprofits with employee volunteers to deliver $306,000 in consulting services. Common themes include environmental conservation, where participants develop solutions for , as seen in the Climate Solutions Hackathon organized by the Wilkes Center for Climate Science and Policy, which challenges interdisciplinary teams to propose slide-deck-based innovations within 24 hours. Health-focused hackathons target innovation and wellness, exemplified by the in Climate Hackathon held during Climate Week NYC on September 20, 2025, uniting clinicians, coders, and policymakers to prototype technology-driven responses to intersecting health and environmental crises. Education-themed events, such as tracks in the Horizon AI Hackathon 2025, foster tools for learning equity, drawing from AI and to enhance in underserved regions. These themes ensure projects remain feasible within time limits while promoting domain-specific expertise over broad experimentation. Purpose-driven hackathons often integrate evaluation metrics tied to real-world applicability, such as for social enterprises or alignment with ethical AI principles, distinguishing them from purely competitive formats by prioritizing sustained implementation over prizes. For instance, social impact events like the Pratt Institute's 2025 Social Impact Hackathon convene creatives, nonprofits, and businesses to storytelling and digital solutions for challenges, with outputs intended for post-event deployment. This approach has yielded targeted innovations, though success depends on follow-through resources, as thematic constraints can limit serendipitous breakthroughs but enhance focus on verifiable problem-solving.

Internal, Virtual, and Hybrid Types

Internal hackathons are competitive events sponsored by an exclusively for its employees, typically lasting 24 to 48 hours, where participants form teams to develop prototypes addressing internal challenges or generating new ideas. These events prioritize fostering cross-departmental , identifying talent, and stimulating without external , often resulting in tangible improvements or feature developments. For example, (now Meta) has conducted quarterly internal hackathons since the early 2000s, yielding products like the Timeline feature and HipHop , which enhanced performance by factors of up to 6x in production environments. Similarly, Capital One's internal hackathons have produced tools for fraud detection and customer analytics, demonstrating how such formats break down silos and boost employee engagement. Companies report benefits including heightened camaraderie and problem-solving efficiency, with participation rates often exceeding 20-30% of workforce in large firms. Virtual hackathons operate entirely online, leveraging platforms for code collaboration, video conferencing, and virtual whiteboarding to enable remote team formation and prototyping over 24-72 hours. Their adoption accelerated post- amid restrictions, transforming traditional events into accessible formats that eliminated travel barriers and scaled global participation. HackZurich, Europe's largest hackathon, shifted virtual in and drew over 1,000 participants from diverse locations, producing solutions in areas like sustainable tech via tools such as and Slack. , a firm, began virtual events in 2019 but expanded them in , hosting thousands across time zones and yielding innovations in APIs. Imperva's inaugural virtual hackathon in involved 200+ employees remotely, generating cybersecurity prototypes that advanced to production. These formats reduce costs by 50-70% compared to in-person equivalents while maintaining output quality through asynchronous submissions and live demos. Hybrid hackathons blend in-person and virtual participation, allowing attendees to choose formats while sharing a unified event structure, often with core teams onsite and remote contributors via streaming and . This model, gaining traction since 2021, accommodates hybrid work trends and expands reach, with events like those analyzed in academic studies attracting 20-50% more participants by mitigating geographic and logistical constraints. Advantages include enhanced inclusivity for distributed teams and cost efficiencies from partial physical setups, though organizers face challenges in equitable engagement, such as ensuring remote voices influence judging equally. For instance, hybrid formats in corporate settings like those from Major League Hacking have increased attendance by integrating live venue interactions with access, fostering diverse ideation without full relocation demands. Empirical reviews indicate hybrid events achieve similar innovation rates to pure virtual ones but with higher retention of in-person networking benefits.

Participation Dynamics

Motivations and Preparation Strategies

Participants engage in hackathons primarily to acquire new technical skills, foster professional networks, and experience the challenge of time-bound . Surveys indicate that learning opportunities, such as experimenting with or APIs, consistently rank among the top motivators, often surpassing monetary incentives. Networking with peers, mentors, and industry recruiters follows closely, enabling connections that can lead to job offers or future collaborations. Additional drivers include the potential for recognition through prizes or continuation, as well as intrinsic factors like and creative problem-solving. In domain-specific events, such as or civic hackathons, participants may also cite alignment with professional responsibilities or societal impact as key reasons. Empirical analyses confirm these motivations persist across virtual and in-person formats, with no significant shifts post-event in controlled studies of students. Effective begins with selecting events aligned with personal expertise and goals, followed by forming teams of 3-5 members with complementary roles—typically including coders, designers, and subject-matter experts—to maximize . Pre-event into themes, judging criteria, and permitted resources, such as reviewing past winners or APIs, enhances readiness without violating rules against substantial prior development. Participants often conduct informal rehearsals for ideation and pitching to refine under constraints, though empirical evidence stresses adapting to event-specific logistics like time zones in hybrid setups.

Skill-Building and Networking Outcomes

Hackathons enable rapid skill acquisition in technical domains, such as and problem-solving under deadlines, alongside entrepreneurial competencies like idea validation. demonstrates substantial self-reported enhancements in these areas; after a one-day hackathon, participants' in starting a increased from 16.9% to 66.2%, and their ability to generate viable ideas rose from 50.7% to 84.5%. These improvements in exceeded those from semester-long traditional courses, where analogous gains lacked . Soft skills also advance markedly, including ideation, , resilience, and , as evidenced by a university-wide sustainability hackathon where 18 of 23 participants reported greater awareness and appreciation of such abilities via post-event surveys. Systematic reviews corroborate broader educational benefits, encompassing technical proficiency and novel learning experiences that translate to real-world application. Networking outcomes stem from collaborations with diverse teams, mentors, and judges, often bridging academic and industry spheres. In corporate settings, participants perceive expanded networks and progression, with sustained momentum post-event. Interdisciplinary interactions further bolster by simulating cross-functional environments, though outcomes depend on event structure and participant preparation.

Outputs and Real-World Impact

Notable Successes and Derived Innovations

originated as a prototype developed during the TechCrunch Disrupt Hackathon in on August 24-25, 2010, where founders and Steve Martocci built a group messaging application in under 24 hours. The project won the event's top prize, secured immediate angel funding from investors including Lerer Ventures, and launched publicly shortly thereafter. By August 2011, acquired for an estimated $80 million, enabling the app to scale to millions of users by integrating real-time SMS-based group communication into mainstream mobile services. Carousell emerged from the Startup Weekend Singapore hackathon in August 2012, a 54-hour event where co-founders Quek Siu Rui, Lucas Ngoo, and Marcus Tan prototyped a mobile platform for peer-to-peer classifieds focused on secondhand goods. Their app addressed inefficiencies in local marketplaces by emphasizing simple photo-based listings and social sharing, winning positive feedback that propelled further development. The company achieved unicorn status by 2021 with a valuation exceeding $1 billion, expanding to serve over 10 million monthly users across Southeast Asia through iterative improvements in search algorithms and logistics integrations. Zapier was prototyped over two days at a Startup Weekend hackathon in , around 2011 by co-founders Wade Foster, Bryan Helmig, and Mike Knoop, who created an tool connecting web apps without coding. The demo won the competition, validating demand for no-code workflows and leading to the company's formal launch in 2012 via . Zapier has since facilitated billions of automated tasks annually, powering integrations for over 5,000 apps and generating hundreds of millions in annual revenue by enabling small teams to replicate enterprise-level efficiency. Internally, Twitter's core concept arose from a 2006 hackathon at , a faltering podcasting firm, where proposed short status updates via amid Apple's dominance disrupting their business. This pivot project evolved into Twitter's launch in July 2006, growing to 300 million users by enabling real-time information dissemination that influenced events like the Arab Spring. Hackathons have also yielded derived innovations within established firms, such as Talkdesk's annual events since 2014, which produced features like Workspace—a unified agent interface—and AI Translator for multilingual call handling, enhancing contact center efficiency for enterprise clients. Similarly, Facebook's 2007 hackathon birthed tools like friend tagging in comments and early chat prototypes, which scaled to support billions of daily interactions by prioritizing rapid experimentation over polished code. These outcomes demonstrate hackathons' role in accelerating feature development through time-bound constraints, though success depends on post-event resourcing rather than ideation alone.

Predominant Failure Rates and Reasons

Empirical analyses of hackathon repositories on platforms like reveal that the vast majority of projects fail to sustain development beyond the event itself. A study examining 1,000 hackathon-linked repositories found that only 7% exhibited any commit activity six months post-event, with projects averaging just 3.1 distinct commit dates overall, indicating rapid abandonment in 93% of cases. Similar patterns emerge in other datasets, where code creation during the hackathon constitutes a small fraction of total repository content, suggesting most initiatives remain prototypes without iterative refinement. Primary reasons for these failures stem from the event's compressed timeline and ad-hoc nature, which prioritize over robust architecture. Technical debt accumulates from shortcuts, such as untested code and overlooked issues, rendering prototypes unsuitable for production without substantial rework. Temporary teams often dissolve post-event due to participants' return to primary commitments, lacking mechanisms for ongoing or skill alignment. Additional causal factors include insufficient post-event infrastructure, such as absent pipelines or integration pathways into sponsoring organizations, which leave projects without resources for validation or deployment. Problem misalignment exacerbates this, as loosely defined challenges yield ideas disconnected from viable markets or operational needs, diminishing incentives for continuation. In corporate contexts, hinges on explicit efforts to "find a home" for projects within existing workflows, a step omitted in most cases. These dynamics underscore hackathons' role as ideation sparks rather than reliable innovation pipelines, with low continuation rates reflecting structural rather than incidental shortcomings.

Broader Economic and Innovation Effects

Hackathons facilitate economic value creation by accelerating prototype development into startups, particularly through utilization that enables nascent entrepreneurs to identify market opportunities and secure initial . For instance, participants in hackathons have transformed prototypes into scalable services, contributing to digital and government-citizen value addition via new offerings. This process lowers for , as collaborative, time-bound events reduce upfront capital needs compared to traditional venture incubation. Corporations derive economic benefits from hackathons as a low-cost alternative to conventional R&D, idea generation to external or internal talent pools while minimizing resource commitments. Empirical analyses show these events attract entrepreneurial participants, enabling rapid experimentation that feeds into product roadmaps and yields measurable returns through talent retention and prototyping efficiencies. In sectors like healthcare, hackathon outputs have progressed to clinical trials and formalized plans, providing pathways for and sustained generation. On innovation fronts, hackathons drive systemic advancements by bridging academia-industry gaps, fostering cross-disciplinary solutions that enhance and policies. Systematic reviews of outcomes reveal consistent patterns of skill enhancement, network expansion, and viability, though long-term success depends on post-event support structures to convert ephemeral ideas into enduring technologies. These effects amplify in hybrid formats, where virtual participation expands reach and diversifies inputs, potentially amplifying economic multipliers through broader talent . However, causal links to macroeconomic growth remain indirect, primarily manifesting via localized boosts rather than aggregate GDP contributions, as evidenced by limited longitudinal data on scaled implementations.

Criticisms and Debates

Labor Exploitation and Corporate Gain

Critics argue that many corporate-sponsored hackathons function as mechanisms for extracting unpaid labor from participants, particularly aspiring developers and students, while providing minimal reciprocal value beyond nominal prizes or resume fodder. In external hackathons, participants often devote 24-48 hours of intensive coding and ideation without compensation, producing prototypes that sponsors—typically tech firms—can evaluate for potential integration into their products or services, effectively innovation at zero direct labor cost. A 2018 sociological analysis described this dynamic as "co-optation," where highly skilled "builders" contribute speculative work that corporations appropriate, fostering "fictional expectations" of broad benefits while participants bear the full risk of unremunerated effort. This arrangement yields asymmetric gains for sponsoring entities, which leverage hackathons for talent scouting, branding, and low-risk idea generation without incurring traditional R&D expenses. For instance, companies like and have historically sponsored events yielding thousands of project submissions annually, from which they selectively recruit or adapt concepts, while the majority of entrants receive no tangible return beyond potential networking. Such practices reproduce among participants, who self-exploit through voluntary in hopes of future , mirroring patterns where enthusiasm masks structural imbalances. Empirical observations from hackathon ethnographies indicate that sponsor booths and judging panels prioritize projects aligning with corporate agendas, further directing unpaid output toward proprietary advantage. Proponents of this model counter that voluntary participation and skill-building opportunities justify the structure, yet detractors highlight how power imbalances—evident in sponsor control over themes, judging, and IP waivers—undermine claims of mutual benefit. In cases where rules assign project ownership to entrants, corporations still gain indirect value through first-mover evaluation rights and recruitment pipelines, often converting free labor into competitive edges without equivalent investment in participant welfare. This critique extends to broader economic effects, where hackathons sustain a of democratized while concentrating gains among established firms, as evidenced by persistent low rates for non-sponsored projects.

Efficacy in Driving Sustained Innovation

Empirical analyses of hackathon outcomes reveal limited in driving sustained , as most projects exhibit low persistence beyond the event. A study of repositories from various hackathons found that only 7% of projects showed any activity six months after completion, with an average of 3.097 distinct commit dates per project, indicating rapid abandonment due to challenges like dissolution and resource constraints. Similarly, quantitative assessments highlight that short-term continuation—often tied to winning prizes or technical experimentation—does not reliably predict long-term viability, which instead depends on skill diversity, expansion intentions, and post-event . In academic and scientific hackathons, outputs more commonly seed collaborations than yield finished innovations. For instance, projects from specialized hackathons have produced elements like maintained codebases on , draft papers, and pre-submission inquiries, but seldom result in complete products without subsequent self-funding and maturation. These events establish footholds for interdisciplinary partnerships, yet the absence of built-in scaling mechanisms limits transformation into enduring advancements, with continuation hinging on external factors such as grant acquisition. Corporate settings offer marginally better prospects through structured follow-up, including incubation programs or operational integration, which can elevate select prototypes to production— as seen in cases where 4 out of numerous ideas advanced in one organization's annual event. However, even here, verifiable long-term remains rare; while isolated successes, such as startups originating from hackathon prototypes, demonstrate potential, they constitute exceptions amid predominant attrition rates. Overall, hackathons excel at catalyzing ideation and application but require deliberate post-event in , , and alignment to overcome inherent barriers to sustained impact.

Inclusivity Barriers and Diversity Claims

Hackathons exhibit persistent demographic imbalances, with female participation typically ranging from 20% to 24% in major events organized by groups like Major League Hacking (MLH), compared to 73% male attendees as of data. Underrepresented ethnic minorities face similar underrepresentation, though comprehensive longitudinal statistics remain limited; studies indicate that participants from these groups are less likely to sustain programming engagement 10 weeks post-event relative to majority demographics. These patterns mirror broader field disparities, such as those reported in the Computing Research Association's Taulbee surveys, suggesting hackathons amplify rather than originate field-wide imbalances driven by enrollment and interest gaps. Identified barriers to inclusivity include self-doubt and lower among women in mixed-gender settings, leading to reduced intrinsic motivation compared to male peers. Additional factors encompass , scarcity of , and environmental anxieties in high-stakes, competitive formats that demand and public presentation. For ethnic minorities, barriers involve similar perseverance challenges post-event, potentially exacerbated by favoring homogeneous teams. However, empirical analyses emphasize preparation disparities and prior experience as causal contributors over overt exclusion, with women's lower participation often tracing to foundational skill gaps rather than event-specific . Diversity initiatives, such as women-focused hackathons, aim to mitigate these barriers by fostering safer spaces and building confidence, with some reporting short-term boosts in female engagement. Yet critiques highlight risks of segregation, where such events may reinforce perceptions that women require insulated environments to succeed, potentially hindering integration into general hackathons and broader tech ecosystems. Gender-neutral approaches, prioritizing skill-building without explicit quotas, have been proposed as alternatives to avoid alienating male participants or fostering resentment, though evidence on long-term efficacy remains mixed. Claims of transformative inclusivity often outpace verifiable outcomes; while participation rates have risen modestly—e.g., an 18% increase in female representation in select communities by 2021—sustained retention and innovation contributions from diverse groups show limited gains, with many initiatives criticized as performative rather than structural reform. Peer-reviewed evaluations underscore that without addressing upstream factors like educational pipelines, hackathon diversity efforts yield marginal impacts on field-wide representation.

References

  1. https://www.merriam-webster.com/dictionary/hackathon
  2. https://www.techtarget.com/searchcio/definition/hackathon
  3. https://www.coursera.org/articles/what-is-a-hackathon
  4. https://hackernoon.com/the-history-of-hackathons-a-digital-evolution
  5. https://content.techgig.com/codegladiators2021/a-brief-history-of-hackathon/articleshow/75291637.cms
  6. https://www.brightidea.com/guide/hackathon/what-is-a-hackathon/
  7. https://www.hackerearth.com/blog/6-hackathon-ideas-turned-million-dollar-startups
  8. https://www.idtech.com/blog/what-is-a-hackathon
  9. https://tips.hackathon.com/article/what-is-a-hackathon
  10. https://www.indeed.com/career-advice/career-development/what-is-hackathon
  11. https://fliplet.com/blog/what-is-a-hackathon-ultimate-guide/
  12. https://medium.com/oneiota/the-history-of-the-hackathon-52551433af31
  13. https://datahub.io/blog/from-coding-marathons-to-corporate-strategy-the-evolution-of-hackathons
  14. https://firstlinesoftware.com/blog/why-hackathons/
  15. https://hacktribe.co/the-evolution-of-hackathons-past-present-and-future
  16. https://www.slideshare.net/slideshow/the-history-of-hackathons/23756832
  17. https://www.openbsd.org/hackathons.html
  18. https://www.provos.org/p/hackathon/
  19. https://www.govtech.com/data/Who-Invented-the-Hackathon.html
  20. http://jeremy.zawodny.com/blog/archives/006924.html
  21. https://techcrunch.com/2006/08/25/announcing-yahoo-open-developer-hack-day/
  22. https://techcrunch.com/2006/09/22/more-details-on-yahoo-hack-day/
  23. https://thenextweb.com/news/facebook-shares-the-history-of-its-hackathon
  24. https://inspireip.com/facebook-like-button/
  25. https://www.forbes.com/sites/benjaminlaker/2023/08/05/empowering-society-through-digital-innovation-the-hackathon-trend/
  26. https://www.hackerearth.com/blog/6-reasons-companies-conduct-hackathon
  27. https://www.forbes.com/sites/michellegreenwald/2021/09/01/how-covid-19-changed-mits-global-hackathon-program-and-others-for-the-better-forever/
  28. https://news.mit.edu/2020/virtual-hackathon-unites-international-community-tackle-covid-19-0513
  29. https://aws.amazon.com/blogs/publicsector/hacking-covid-19-hackathons-challenges-pandemic/
  30. https://arxiv.org/html/2508.07301v1
  31. https://researchcomputing.princeton.edu/events/2024/2024-princeton-open-hackathon-hybrid-event
  32. https://siim.org/learning-events/events/hackathon/
  33. https://www.mdpi.com/2078-2489/16/6/488
  34. https://www.aidataanalytics.network/data-science-ai/news-trends/google-launches-100000-bigquery-ai-hackathon-to-unlock-the-power-of-data
  35. https://info.devpost.com/blog/internal-hackathons-drive-ai-transformation
  36. https://qpulse.tech/autonomous-hackathons-agents-prototyping-100-ideas-in-a-week/
  37. https://www.digitalocean.com/resources/articles/ai-hackathon-events
  38. https://www.mdpi.com/2504-2289/8/12/188
  39. https://www.nutanix.com/theforecastbynutanix/business/hackathons-drive-growth-in-ai-applications
  40. https://www.hackerearth.com/community-hackathons/resources/e-books/guide-to-organize-hackathon/
  41. https://angelhack.com/blog/how-to-organize-a-hackathon/
  42. https://guide.mlh.io/general-information/finding-the-date-and-purpose
  43. https://www.researchgate.net/figure/The-typical-hackathon-process-in-terms-of-the-activities-phases-and-supporting-elements_fig1_308417811
  44. https://business-docs.co.uk/scenario/what-is-a-good-hackathon-schedule/?srsltid=AfmBOopTPtiFOzusBlH2jRWyZX95Er08y1z5wtykxJ0sz8zi3OTjEQyX
  45. https://hackathon-planning-kit.org/files/hackerearth.pdf
  46. https://guide.mlh.io/general-information/hackathon-scheduling/detailed-run-of-show
  47. https://medium.com/nwplusubc/timeline-of-a-hackathon-9cdcd1825bd4
  48. https://www.nyc.gov/html/hackathon/html/logistics.html
  49. https://guide.mlh.io/general-information/judging-and-submissions/rules-for-your-hackathon
  50. https://corporate.hackathon.com/articles/innovation-hackathon-guide-everything-you-need-to-know
  51. https://tips.hackathon.com/article/the-essential-quick-tips-for-forming-a-winning-hackathon-team
  52. https://entrepreneurquarterly.com/5-roles-every-hackathon-team-needs/
  53. https://www.geeksforgeeks.org/blogs/5-must-have-skills-youll-need-in-your-hackathon-team/
  54. https://info.devpost.com/blog/understanding-hackathon-submission-and-judging-criteria
  55. https://taikai.network/en/blog/hackathon-judging
  56. https://help.devpost.com/article/64-judging-public-voting
  57. https://guide.mlh.io/general-information/judging-and-submissions/judging-plan
  58. https://unstop.com/blog/how-to-judge-a-hackathon
  59. https://www.aectech.us/guidelines-judging
  60. https://help.devpost.com/article/103-how-to-judge-an-online-hackathon
  61. https://info.devpost.com/blog/hackathon-judging-tips
  62. https://worldslargesthackathon.devpost.com/details/prizes
  63. https://treehacks-2025.devpost.com/
  64. https://bolt.new/blog/hackathon-prizes-global-glory-regional-highlights-bonus-wins
  65. https://www.microsoft.com/en-us/education/blog/2024/05/meet-the-winners-of-the-microsoft-ai-classroom-hackathon/
  66. https://www.brightidea.com/guide/hackathon/planning-a-hackathon/awards-for-hackathon-participants-and-winners/
  67. https://news.mlh.io/top-10-prize-winning-hackathon-projects-for-the-avanade-best-sustainability-hack-challenge-10-24-2023
  68. https://pristineagency.eu/blog/what-are-good-hackathon-prizes
  69. https://dorahacks.io/hackathon
  70. https://info.devpost.com/blog/8-types-of-internal-hackathons
  71. https://www.hackathonparty.com/blog/exploring-the-origin-of-hackathons-a-journey-through-time
  72. https://devpost.com/c/blockchain
  73. https://dorahacks.io/
  74. https://corporate.hackathon.com/articles/15-hackathon-ideas-for-blockchain
  75. https://www.airmeet.com/hub/blog/38-amazing-hackathon-project-ideas-to-implement-in-2025/
  76. https://hackathon.guide/
  77. https://angelhack.com/blog/hackathon-examples/
  78. https://www.thomsonreuters.com/en-us/posts/our-purpose/thomson-reuters-social-impact-hackathon/
  79. https://wilkescenter.utah.edu/hack/
  80. https://www.climateweeknyc.org/events/health-climate-hackathon
  81. https://www.coe.miami.edu/events/horizon-ai-hackathon/index.html
  82. https://www.qmarkets.net/resources/article/hackathon-examples/
  83. https://www.pratt.edu/events/social-impact-hackathon-2/
  84. https://corporate.hackathon.com/articles/12-hackathon-ideas-for-healthcare
  85. https://www.brightidea.com/guide/hackathon/types-of-hackathons/
  86. https://techcrunch.com/2024/05/19/why-companies-are-turning-to-internal-hackathons/
  87. https://www.gravitywell.co.uk/insights/internal-company-hackathons-5-successful-examples/
  88. https://www.hackerearth.com/blog/virtual-hackathons
  89. https://info.devpost.com/blog/how-to-organize-virtual-hackathons
  90. https://www.digitalsamba.com/blog/the-rise-of-virtual-hackathons
  91. https://info.devpost.com/customer-stories/finastra-devpost-customer-story
  92. https://www.imperva.com/blog/virtual-hackathon-generates-next-generation-of-imperva-innovation/
  93. https://angelhack.com/blog/what-is-a-hackathon/
  94. https://www.qmarkets.net/resources/article/online-hackathons-or-offline/
  95. https://news.mlh.io/hackathons-in-a-hybrid-world-07-28-2022
  96. https://hackathon-planning-kit.org/files/Medina-ICSOB-2023.pdf
  97. http://reports-archive.adm.cs.cmu.edu/anon/2021/CMU-CS-21-145.pdf
  98. https://www.scielo.br/j/bar/a/wnWXvG6Pc5STTgX46kC38QG/?format=pdf&lang=en
  99. https://inria.hal.science/hal-02446024/document
  100. https://arxiv.org/pdf/2402.05339
  101. https://herbsleb.org/web-pubs/pdfs/trainer-howto-2016.pdf
  102. https://arxiv.org/html/2008.08025v3
  103. https://www.mdpi.com/2076-3387/10/3/73
  104. https://www.sciencedirect.com/science/article/pii/S2666374023000821
  105. https://www.researchgate.net/publication/365866145_Educational_benefits_of_hackathon_A_systematic_literature_review
  106. https://dl.acm.org/doi/10.1145/3274398
  107. https://techcrunch.com/2010/08/25/groupme-born-at-techcrunch-disrupt-secures-funding-and-launches/
  108. https://techcrunch.com/2012/05/11/from-disrupt-ny-to-a-43-million-skype-acquisition-groupme-tells-all/
  109. https://disruptsf2019.devpost.com/
  110. https://enterprise.nus.edu.sg/startup-story/carousell/
  111. https://news.nus.edu.sg/carousell-hits-us1-billion-the-story-of-asias-latest-unicorn/
  112. https://blog.carousell.com/carousell-pro-tips/featured-spotlight/carousell-early-years/
  113. https://research.contrary.com/company/zapier
  114. https://www.businessinsider.com/how-twitter-was-founded-2011-4
  115. https://www.talkdesk.com/blog/inside-talkdesk-hackathon-10-years-innovation/
  116. https://www.cloudfest.com/blog/what-is-a-hackathon-event-and-how-to-organize-one/
  117. https://dl.acm.org/doi/10.1145/3408877.3432435
  118. https://pmc.ncbi.nlm.nih.gov/articles/PMC9489595/
  119. https://www.genspark.ai/spark/the-hackathon-reality-check-why-93-of-projects-never-see-real-users/8d4ed14c-6e27-4b44-b3d5-7eba31a658b0
  120. http://www.scielo.org.za/scielo.php?script=sci_arttext&pid=S2077-72132023000100004
  121. https://hackernoon.com/hackathons-are-broken-heres-how-we-fix-them
  122. https://sloanreview.mit.edu/article/avoid-these-five-pitfalls-at-your-next-hackathon/
  123. https://www.tandfonline.com/doi/abs/10.1080/07370024.2020.1760869
  124. https://www.sciencedirect.com/science/article/abs/pii/S0268401222000032
  125. https://www.mdpi.com/2199-8531/8/3/111
  126. https://www.sciencedirect.com/science/article/pii/S2405844023020753
  127. https://journals.sagepub.com/doi/10.1177/09504222251323946
  128. https://www.cultureamp.com/blog/how-companies-have-hacked-the-hackathon
  129. https://pmc.ncbi.nlm.nih.gov/articles/PMC5293858/
  130. https://www.researchgate.net/publication/343985487_What_Do_We_Know_About_Hackathon_Outcomes_and_How_to_Support_Them_-_A_Systematic_Literature_Review
  131. https://onlinelibrary.wiley.com/doi/10.1111/radm.12751
  132. https://papers.academic-conferences.org/index.php/ecie/article/view/3823
  133. https://www.wired.com/story/sociologists-examine-hackathons-and-see-exploitation/
  134. https://academicworks.cuny.edu/cgi/viewcontent.cgi?article=1575&context=gc_pubs
  135. https://www.hackerearth.com/blog/good-bad-overrated
  136. https://www.sciencedirect.com/science/article/abs/pii/S0016718518302586
  137. https://dl.acm.org/doi/10.1145/3415216
  138. https://pmc.ncbi.nlm.nih.gov/articles/PMC4511834/
  139. https://news.nationwide.com/from-brainstorm-to-breakthrough-how-a-hackathon-sparked-115-bold-ai-ideas/
  140. https://taikai.network/en/blog/5-companies-born-from-hackathons
  141. https://www.researchgate.net/publication/344747255_What_Happens_to_All_These_Hackathon_Projects_-_Identifying_Factors_to_Promote_Hackathon_Project_Continuation
  142. https://news.mlh.io/mlh-hackathon-demographics-09-03-2019
  143. https://www.linkedin.com/pulse/how-hackathons-instrumental-boosting-your-diversity-hiring-initiatives-339mc
  144. https://dl.acm.org/doi/fullHtml/10.1145/3564721.3564727
  145. https://peer.asee.org/an-investigation-into-gender-diverse-populations-in-hackathon-environments.pdf
  146. https://ieeexplore.ieee.org/iel7/9853504/9853554/09853588.pdf
  147. https://www.researchgate.net/publication/347319211_Female_Participation_in_Hackathons_A_Case_Study_About_Gender_Issues_in_Application_Development_Marathons
  148. https://www.sciencedirect.com/science/article/abs/pii/S027753952400147X
  149. https://dl.acm.org/doi/fullHtml/10.1145/3433168
  150. https://dl.acm.org/doi/abs/10.1109/MC.2024.3502248
  151. https://dl.acm.org/doi/abs/10.1145/3524501.3527603
  152. https://medium.com/techtogether/the-racial-and-gender-gap-in-hackathon-attendance-93899fec9804
  153. https://medium.com/%40schessa/your-d-i-themed-hackathon-is-large-scale-tokenism-fccfa44b3c6a
Add your contribution
Related Hubs
User Avatar
No comments yet.