[{"data":1,"prerenderedAt":588},["ShallowReactive",2],{"blog-como-organizamos-una-hackathon-en-35-dias-es-with-drafts":3,"blog-translated-como-organizamos-una-hackathon-en-35-dias-with-drafts":277},{"id":4,"title":5,"author":6,"body":7,"coverBackground":260,"date":261,"dateModified":261,"description":262,"extension":263,"image":264,"locale":265,"meta":266,"navigation":267,"path":268,"readingTime":269,"seo":270,"status":271,"stem":272,"tags":273,"union":275,"__hash__":276},"blog_es\u002Fes\u002Fblog\u002Fcomo-organizamos-una-hackathon-en-35-dias.md","¿Cómo organizamos una hackathon en 35 días?","Felipe Torres, Sergio Azócar",{"type":8,"value":9,"toc":249},"minimark",[10,15,19,22,25,28,35,39,42,49,55,61,67,71,74,93,96,100,103,106,109,113,116,148,151,172,176,179,185,191,197,203,209,213,216,222,228,234,240,243],[11,12,14],"h2",{"id":13},"por-qué-hacer-una-hackathon","Por qué hacer una hackathon",[16,17,18],"p",{},"La idea de organizar una hackathon nació de una convicción simple: las mejores comunidades se construyen haciendo cosas juntos, no solo hablando de ellas.",[16,20,21],{},"En SkywardAI llevábamos meses trabajando con agentes de IA y viendo cómo esta tecnología estaba transformando la forma en que se construye software. Pero en Chile, la conversación sobre agentes de IA seguía siendo mayoritariamente teórica. Había charlas, newsletters y threads en redes sociales, pero pocas instancias donde la gente pudiera sentarse a construir algo real.",[16,23,24],{},"Queríamos cambiar eso. Queríamos crear un espacio donde desarrolladores, diseñadores y personas curiosas por la IA pudieran experimentar, romper cosas y aprender haciendo. Y queríamos hacerlo rápido, antes de que la ventana de entusiasmo se cerrara.",[16,26,27],{},"Así que nos dimos 35 días para organizar la primera hackathon de agentes de IA en Chile.",[16,29,30],{},[31,32],"img",{"alt":33,"src":34},"La hackathon en que nos conocimos","\u002Fblog\u002Fhackathon\u002Fconocimos.webp",[11,36,38],{"id":37},"cumplir-con-lo-básico","Cumplir con lo básico",[16,40,41],{},"Antes de pensar en temas creativos o dinámicas innovadoras, nos enfocamos en lo fundamental: que la experiencia básica funcionara bien.",[16,43,44,48],{},[45,46,47],"strong",{},"Lugar y logística."," Conseguimos un espacio que pudiera albergar a más de 100 personas cómodamente, con buena conectividad, espacio para que los equipos trabajaran en paralelo y áreas comunes para networking. Parece obvio, pero un wifi inestable o un espacio incómodo pueden arruinar cualquier hackathon.",[16,50,51,54],{},[45,52,53],{},"Comida y energía."," Aseguramos alimentación durante todo el evento. Cuando la gente está construyendo algo contra el reloj, lo último que necesita es preocuparse por dónde almorzar. Café, snacks y comida estuvieron disponibles de forma continua.",[16,56,57,60],{},[45,58,59],{},"Comunicación clara."," Desde el día uno de inscripciones hasta el cierre del evento, mantuvimos un canal de comunicación directo con los participantes. Cada actualización, cambio de horario o información logística se comunicó de forma proactiva. La incertidumbre mata la motivación.",[16,62,63],{},[31,64],{"alt":65,"src":66},"No estaba fácil","\u002Fblog\u002Fhackathon\u002Fno-estaba-facil.webp",[11,68,70],{"id":69},"reglas-simples","Reglas simples",[16,72,73],{},"Definimos reglas claras y simples para el evento:",[75,76,77,81,84,87,90],"ul",{},[78,79,80],"li",{},"Los equipos podían tener entre 2 y 5 personas.",[78,82,83],{},"Los proyectos debían involucrar al menos un agente de IA funcional.",[78,85,86],{},"Se podía usar cualquier stack tecnológico, framework o modelo de lenguaje.",[78,88,89],{},"El código debía escribirse durante la hackathon (no proyectos preexistentes).",[78,91,92],{},"La presentación final tenía un límite estricto de tiempo.",[16,94,95],{},"La simplicidad en las reglas fue intencional. Cuando las restricciones son claras, la creatividad se libera. Los equipos no perdieron tiempo interpretando bases complicadas; se dedicaron directamente a construir.",[11,97,99],{"id":98},"alianzas-estratégicas","Alianzas estratégicas",[16,101,102],{},"Organizar una hackathon de esta escala requiere más que un equipo interno motivado. Desde el principio buscamos alianzas con empresas y organizaciones que compartieran nuestra visión.",[16,104,105],{},"Los sponsors no solo aportaron recursos económicos para los premios y la logística, sino que varios proporcionaron acceso a APIs, créditos de computación y mentores técnicos que estuvieron disponibles durante todo el evento. Esto elevó significativamente la calidad de los proyectos.",[16,107,108],{},"La clave fue buscar partners que genuinamente quisieran apoyar a la comunidad, no solo poner su logo en un banner. Cada alianza tenía que aportar valor real a los participantes.",[11,110,112],{"id":111},"resultados","Resultados",[16,114,115],{},"Los números superaron nuestras expectativas:",[75,117,118,124,130,136,142],{},[78,119,120,123],{},[45,121,122],{},"194 personas inscritas"," en solo 3 semanas de convocatoria.",[78,125,126,129],{},[45,127,128],{},"104 hackers"," participaron presencialmente el día del evento.",[78,131,132,135],{},[45,133,134],{},"20 equipos"," formados y compitiendo.",[78,137,138,141],{},[45,139,140],{},"Más de $60,000 USD en premios"," distribuidos entre los ganadores.",[78,143,144,147],{},[45,145,146],{},"12 horas continuas"," de desarrollo, desde la mañana hasta la presentación final.",[16,149,150],{},"Pero más allá de los números, lo que nos impactó fue la calidad de los proyectos. En 12 horas, los equipos construyeron agentes de IA funcionales para casos de uso que iban desde asistentes legales hasta herramientas de análisis financiero automatizado. Varios proyectos tenían potencial real de convertirse en productos.",[16,152,153,157,160,163,166,169],{},[31,154],{"alt":155,"src":156},"Hackathon evento","\u002Fblog\u002Fhackathon\u002Fevento-1.webp",[31,158],{"alt":155,"src":159},"\u002Fblog\u002Fhackathon\u002Fevento-2.webp",[31,161],{"alt":155,"src":162},"\u002Fblog\u002Fhackathon\u002Fevento-3.webp",[31,164],{"alt":155,"src":165},"\u002Fblog\u002Fhackathon\u002Fevento-4.webp",[31,167],{"alt":155,"src":168},"\u002Fblog\u002Fhackathon\u002Fevento-5.webp",[31,170],{"alt":155,"src":171},"\u002Fblog\u002Fhackathon\u002Fevento-6.webp",[11,173,175],{"id":174},"recomendaciones-clave","Recomendaciones clave",[16,177,178],{},"Para quienes estén pensando en organizar su propia hackathon, estas son las lecciones que nos habría gustado saber antes:",[16,180,181,184],{},[45,182,183],{},"1. Empieza por la experiencia del participante, no por la tuya."," Cada decisión logística debe responder a la pregunta: \"¿Esto hace que sea más fácil o más difícil para alguien construir algo increíble hoy?\" Si la respuesta es \"más difícil\", elimínalo.",[16,186,187,190],{},[45,188,189],{},"2. Sobre-comunica."," Los participantes llegan con niveles muy distintos de experiencia en hackathons. Lo que para ti es obvio, para alguien puede ser completamente nuevo. Comunica los horarios, las reglas, los criterios de evaluación y la logística más de lo que crees necesario.",[16,192,193,196],{},[45,194,195],{},"3. Los mentores hacen la diferencia."," Tener personas experimentadas disponibles durante el evento para resolver dudas técnicas, ayudar con la arquitectura o simplemente dar feedback sobre una idea puede ser la diferencia entre un equipo que se frustra y abandona y uno que logra presentar algo funcional.",[16,198,199,202],{},[45,200,201],{},"4. El tiempo de presentación es sagrado."," Respeta los límites de tiempo de las presentaciones finales de forma estricta. Esto nivela la cancha entre equipos y obliga a todos a comunicar su proyecto de forma concisa y clara.",[16,204,205,208],{},[45,206,207],{},"5. Celebra el proceso, no solo al ganador."," Los premios son importantes, pero la experiencia de construir algo en equipo bajo presión es lo que la gente recuerda. Reconoce el esfuerzo de todos los participantes, no solo de los que suben al podio.",[11,210,212],{"id":211},"lecciones-centrales","Lecciones centrales",[16,214,215],{},"Organizar una hackathon en 35 días fue caótico, intenso y profundamente gratificante. Estas son las tres lecciones que nos quedaron:",[16,217,218,221],{},[45,219,220],{},"La comunidad responde cuando le das un espacio real."," No necesitas meses de planificación para convocar a gente apasionada. Necesitas una propuesta clara, logística que funcione y un genuino interés en que las personas tengan una buena experiencia.",[16,223,224,227],{},[45,225,226],{},"La velocidad es una ventaja, no un riesgo."," Los 35 días de plazo nos obligaron a tomar decisiones rápidas, priorizar lo esencial y no perdernos en detalles que no importaban. Paradójicamente, la restricción de tiempo mejoró la calidad del evento.",[16,229,230,233],{},[45,231,232],{},"Lo importante es lo que pasa después."," La hackathon fue un punto de partida, no un fin en sí mismo. Las conexiones que se formaron, los proyectos que siguieron desarrollándose y la energía que se generó en la comunidad son el verdadero retorno de la inversión.",[16,235,236],{},[31,237],{"alt":238,"src":239},"Nada es imposible","\u002Fblog\u002Fhackathon\u002Fnada-es-imposible.gif",[16,241,242],{},"Ya estamos pensando en la siguiente.",[16,244,245],{},[31,246],{"alt":247,"src":248},"Tú podrías ser el 5 o 6","\u002Fblog\u002Fhackathon\u002Fequipo.webp",{"title":250,"searchDepth":251,"depth":251,"links":252},"",2,[253,254,255,256,257,258,259],{"id":13,"depth":251,"text":14},{"id":37,"depth":251,"text":38},{"id":69,"depth":251,"text":70},{"id":98,"depth":251,"text":99},{"id":111,"depth":251,"text":112},{"id":174,"depth":251,"text":175},{"id":211,"depth":251,"text":212},"secondary","2025-11-24","SkywardAI organizó su primera hackathon de agentes de IA en Chile. 194 inscritos, 104 hackers, 20 equipos y más de $60,000 USD en premios en solo 35 días de planificación.","md",null,"es",{},true,"\u002Fes\u002Fblog\u002Fcomo-organizamos-una-hackathon-en-35-dias",5,{"title":5,"description":262},"published","es\u002Fblog\u002Fcomo-organizamos-una-hackathon-en-35-dias",[274],"Comunidad","hackathon-35-days","cnZ8LX1KV-v8mH9BAr2hu2dsATiVNryHiEPF7Ya_osk",{"id":278,"title":279,"author":6,"body":280,"coverBackground":260,"date":261,"dateModified":261,"description":579,"extension":263,"image":264,"locale":580,"meta":581,"navigation":267,"path":582,"readingTime":269,"seo":583,"status":271,"stem":584,"tags":585,"union":275,"__hash__":587},"blog_en\u002Fen\u002Fblog\u002Fhow-we-organized-a-hackathon-in-35-days.md","How we organized a hackathon in 35 days",{"type":8,"value":281,"toc":567},[282,286,289,292,295,298,303,307,310,342,345,350,354,357,384,387,391,394,411,414,418,421,445,450,457,463,469,475,490,494,497,541,545,548,551,554,559,562],[11,283,285],{"id":284},"why-hold-a-hackathon","Why hold a hackathon",[16,287,288],{},"When we decided to organize an AI agents hackathon, we were not thinking about branding exercises or recruiting pipelines. We had a simpler, more genuine motivation: we wanted to bring together the people in Chile who are actually building with AI agents—not just talking about them—and give them a reason to push their ideas further in a single, intense weekend.",[16,290,291],{},"The AI agent ecosystem in Latin America is still young. There are plenty of conferences and meetups where people discuss what agents could do, but far fewer spaces where builders sit down, write code, and ship something real. We wanted to create that space.",[16,293,294],{},"We also believed that a hackathon would surface the kind of raw, creative applications of AI agents that you do not see in polished product launches. When talented people have 48 hours and no constraints other than \"build something with AI agents,\" the results are often surprising—and sometimes genuinely useful.",[16,296,297],{},"There was one catch: we gave ourselves just 35 days to pull it off.",[16,299,300],{},[31,301],{"alt":302,"src":34},"The hackathon where we met",[11,304,306],{"id":305},"meeting-basic-standards","Meeting basic standards",[16,308,309],{},"Organizing a hackathon is ultimately an exercise in logistics and trust. Participants invest a weekend of their time—often taking days off work or sacrificing family time. The least you can do is make sure the basics are covered:",[75,311,312,318,324,330,336],{},[78,313,314,317],{},[45,315,316],{},"Venue."," A space large enough to accommodate all teams comfortably, with reliable Wi-Fi, power outlets at every table, and a layout that encourages both focused work and casual interaction.",[78,319,320,323],{},[45,321,322],{},"Food and drinks."," People cannot build well on empty stomachs. We ensured there was good food throughout the event—not just pizza and energy drinks, but real meals and healthy options.",[78,325,326,329],{},[45,327,328],{},"Clear schedule."," Participants need to know exactly when things start, when they end, when judging happens, and what the submission requirements are. Ambiguity breeds frustration.",[78,331,332,335],{},[45,333,334],{},"Technical support."," Having mentors and technical staff available throughout the event to help teams debug issues, clarify rules, or provide guidance on APIs and tools.",[78,337,338,341],{},[45,339,340],{},"Fair judging."," Transparent criteria, qualified judges, and a process that participants trust. Nothing kills a hackathon faster than the perception that judging was arbitrary or biased.",[16,343,344],{},"We treated these as non-negotiable. Every decision in our 35-day planning sprint was filtered through a simple question: does this make the experience better for the participants?",[16,346,347],{},[31,348],{"alt":349,"src":66},"It wasn't easy",[11,351,353],{"id":352},"simple-rules-level-playing-field","Simple rules, level playing field",[16,355,356],{},"We kept the rules deliberately simple:",[358,359,360,366,372,378],"ol",{},[78,361,362,365],{},[45,363,364],{},"Build with AI agents."," The project had to meaningfully use AI agents—not just call an API for a text completion.",[78,367,368,371],{},[45,369,370],{},"Build during the hackathon."," Pre-built projects were not allowed. Teams could bring ideas and research, but code had to be written during the event.",[78,373,374,377],{},[45,375,376],{},"Team size: 2-6 people."," Small enough to be agile, large enough to tackle ambitious projects.",[78,379,380,383],{},[45,381,382],{},"Demo or it did not happen."," Every team had to present a working demo. Slide decks alone did not count.",[16,385,386],{},"These constraints created a level playing field. Whether you were a senior engineer from a major tech company or a university student building your first agent, the rules were the same. What mattered was what you built in those 48 hours.",[11,388,390],{"id":389},"partnership-approach","Partnership approach",[16,392,393],{},"We could not have done this alone in 35 days—nor did we want to. We reached out to partners who shared our belief in the Latin American AI community and were willing to contribute meaningfully:",[75,395,396,402,408],{},[78,397,398,401],{},[45,399,400],{},"ElevenLabs"," came on board as a key sponsor, providing API credits and a dedicated prize track for the best use of their voice AI technology.",[78,403,404,407],{},[45,405,406],{},"Cerebras"," provided access to their high-speed inference infrastructure, giving teams the ability to run models that would otherwise have been too slow for a hackathon setting.",[78,409,410],{},"Several other sponsors contributed prizes, API credits, mentorship time, and logistical support.",[16,412,413],{},"The partnership model was simple: we asked partners to contribute things that directly benefited participants—compute credits, API access, prizes, mentors—rather than just logo placement. Every partner delivered.",[11,415,417],{"id":416},"results","Results",[16,419,420],{},"The numbers exceeded our expectations:",[75,422,423,428,433,439],{},[78,424,425],{},[45,426,427],{},"194 registered participants",[78,429,430,432],{},[45,431,128],{}," who showed up and built",[78,434,435,438],{},[45,436,437],{},"20 teams"," that submitted working projects",[78,440,441,444],{},[45,442,443],{},"48 hours"," of building",[446,447,449],"h3",{"id":448},"prizes","Prizes",[16,451,452,453,456],{},"The total prize pool exceeded ",[45,454,455],{},"$60,000 USD",", distributed across three main tracks:",[16,458,459,462],{},[45,460,461],{},"1st Place — Compass: $28,800 USD","\nCompass built an AI agent system for navigating complex regulatory landscapes. The judges were impressed by the technical depth, the practical applicability, and the quality of execution in just 48 hours.",[16,464,465,468],{},[45,466,467],{},"Skyward Prize — EnseñIA: $26,000 USD","\nEnseñIA created an AI-powered educational agent that personalizes learning paths based on student interactions and performance. The team demonstrated a deep understanding of how agents can maintain context and adapt over time—exactly the kind of application that excites us at Skyward.",[16,470,471,474],{},[45,472,473],{},"ElevenLabs Prize — Signos: $5,940 USD","\nSignos built an accessibility tool that uses voice AI to help people with hearing impairments interact more naturally with digital services. The creative use of ElevenLabs' voice technology and the social impact of the project made it a clear winner in this track.",[16,476,477,480,482,484,486,488],{},[31,478],{"alt":479,"src":156},"Hackathon event",[31,481],{"alt":479,"src":159},[31,483],{"alt":479,"src":162},[31,485],{"alt":479,"src":165},[31,487],{"alt":479,"src":168},[31,489],{"alt":479,"src":171},[11,491,493],{"id":492},"key-recommendations","Key recommendations",[16,495,496],{},"For anyone considering organizing a hackathon, here is what we learned:",[358,498,499,505,511,517,523,529,535],{},[78,500,501,504],{},[45,502,503],{},"Start with the participant experience."," Every decision—venue, food, schedule, rules, judging—should be made through the lens of \"does this make the event better for the people who show up to build?\"",[78,506,507,510],{},[45,508,509],{},"Keep rules simple and enforce them consistently."," Complex rules create loopholes and arguments. Simple rules create clarity and fairness.",[78,512,513,516],{},[45,514,515],{},"Invest in logistics, not decoration."," Good Wi-Fi matters more than fancy banners. Enough power outlets matter more than branded swag.",[78,518,519,522],{},[45,520,521],{},"Choose partners who contribute substance."," API credits and mentors are more valuable than logos on a website.",[78,524,525,528],{},[45,526,527],{},"Communicate early and often."," From registration to post-event follow-up, participants should never be left guessing about what comes next.",[78,530,531,534],{},[45,532,533],{},"Have a contingency plan."," Things will go wrong—a sponsor drops out, the Wi-Fi fails, a team disputes a judging decision. Plan for the most likely failure modes in advance.",[78,536,537,540],{},[45,538,539],{},"Document everything."," Photos, videos, participant feedback, project submissions. You will want this material later, and participants appreciate being able to look back at what they built.",[11,542,544],{"id":543},"core-lessons","Core lessons",[16,546,547],{},"Thirty-five days is not a lot of time to organize a hackathon. It forced us to be ruthlessly focused on what mattered and to cut everything that did not directly serve the participant experience. In retrospect, that constraint was a gift.",[16,549,550],{},"The most important lesson was this: the Latin American AI builder community is hungry for real spaces to create. Not panels, not webinars, not pitch competitions—spaces where they can sit down with other talented people and build something from scratch. When you provide that space and remove the friction, the results speak for themselves.",[16,552,553],{},"We walked away from the weekend with 20 working projects, several of which have continued development beyond the hackathon. More importantly, we saw a community forming—people exchanging contacts, forming teams for future projects, and getting genuinely excited about what AI agents can do.",[16,555,556],{},[31,557],{"alt":558,"src":239},"Nothing is impossible",[16,560,561],{},"We are already planning the next one.",[16,563,564],{},[31,565],{"alt":566,"src":248},"You could be number 5 or 6",{"title":250,"searchDepth":251,"depth":251,"links":568},[569,570,571,572,573,577,578],{"id":284,"depth":251,"text":285},{"id":305,"depth":251,"text":306},{"id":352,"depth":251,"text":353},{"id":389,"depth":251,"text":390},{"id":416,"depth":251,"text":417,"children":574},[575],{"id":448,"depth":576,"text":449},3,{"id":492,"depth":251,"text":493},{"id":543,"depth":251,"text":544},"SkywardAI organized its first AI agents hackathon in Chile. 194 registered, 104 hackers, 20 teams and over $60,000 USD in prizes in just 35 days of planning.","en",{},"\u002Fen\u002Fblog\u002Fhow-we-organized-a-hackathon-in-35-days",{"title":279,"description":579},"en\u002Fblog\u002Fhow-we-organized-a-hackathon-in-35-days",[586],"Community","bdH8UZaiBCIN5l5qv9jSqUS8QzK4GbeEqdmcIP7V9Tk",1782297061528]