What participants post publicly
No polished testimonial deck, just real posts published right after the hackathons.
The posts are loaded from LinkedIn, which may process data and set cookies of its own. They only load once you request them here.
Talk to us directly
AI Hackathons is run by Tim Jamboula. There is no sales team and no ticketing queue between you and the person who will actually scope your hackathon. Book a discovery call at Termin buchen and we will talk through your team, your goals, and where AI could move the needle for you.
What happens on the call
The discovery call is the first step of the one-week timeline. We get to know your team, your headcount, your timeline, and the real problems worth solving. From there we schedule a tools and challenges call to match the right format (Spark, Ignite, or Blaze) and the right tools to your situation. Nothing is sold on this first call, it is a conversation to figure out whether and how a hackathon fits.
Before you book
Come with a rough sense of team size and which department or group you want to start with. You do not need a fully scoped problem statement, we help shape that during the tools and challenges call. If you want to document an AI literacy measure for the EU AI Act Article 4, mention that up front so we can align the internal project record with your documentation needs. It does not replace your own assessment.
Why certification alone is not enough
AI certification has search demand, but companies rarely buy a certificate for its own sake. They buy reduced risk, visible progress and a workforce that can use AI responsibly. Our answer is to keep the certificate or literacy proof, then attach it to a shipped workflow. That makes the record credible for HR and compliance and useful for the business function.
