Team Australia
- KishenCaptain
- HarryAI Leader
- Joanna SPM
- Georgia / ChristieQA & Content
- Kaleb / Dane / ScottPM Assist
One day. Three teams. Three countries. Build real, working software that moves the needle for Truckit, then show everyone what you've made.
A hackathon is a short, focused sprint where small teams take a problem and build a working solution from scratch in a single day. No long meetings, no six-month roadmap. Just ideas, code and a hard deadline.
Team captains get the challenge at the 11am briefing. Nobody sees it before then.
Five hours to go from idea to working prototype, with AI tools, real data and each other.
Each team gets 15 minutes to demo live to the judges and the rest of the business.
The winning team takes the trophy, and their build becomes a real Truckit product.
This isn't a slide deck competition. Every team delivers a working piece of software that does something useful for Truckit, our customers or our carriers.
Real code, not no-code tools. It has to run, and you have to demo it live at 4pm.
Solve a problem that matters: saving time, winning customers or unlocking new revenue.
Package it like a launch, with marketing materials, a web page and collateral. Show us how it goes to market.
All three teams get the same brief, revealed to team captains at the 11am briefing on the day. No peeking, and no building beforehand.
Need access to anything else on the day? Ask Saurav.
Not the brief, just the kinds of Truckit problems worth thinking about before the day:
Three countries, one clock. Pick your time zone.
Kick off the day together with the latest from the business.
The challenge is unveiled to team captains, then the clock starts.
Plan, design, code, test, market. Food and drinks are on us to keep you going.
Building stops. Whatever runs now is what you demo.
15 minutes per team: live demo, go-to-market pitch and Q&A with the judges.
The trophy goes to the winning team, and their build heads for production.
Google Meet is open all dayJoin the update, drop into a team, or watch the presentations from anywhere.
๐ Link shared on the dayTeams are locked in, one per country. May the best build win.
The builders are mainly our coders, product and CS people, but a winning hackathon team needs much more than code. If you can free up part of your day, jump in.
Know how the business really works? Help a team shape requirements and understand the problem.
Write the pitch, design the one-pager, name the product. Market readiness scores points.
Build the landing page or product copy that shows how this goes to market.
Be the customer. Try the build, break it and tell the team what's confusing.
Everyone's welcome to take part, but we still have customers to look after. Work with your manager to balance your priorities, then give the hackathon whatever time you can.
Pull up a chair or join the Google Meet. Sit in with a team, see how they work, and definitely tune in for the 4pm presentations.
Extra points for innovative thinking and genuine market readiness. Here's what the judges are looking for.
Does it work? Does it solve the problem?
Could we launch this next week?
Did you go above and beyond?
The winning build doesn't sit in a drawer. It becomes a real Truckit product and goes live.
"AI is changing how software gets built. We want Truckit to lead that change, and the best ideas come from the people who know our business best: you."
Putting AI to work on real Truckit problems, not just talking about it.
Proving we can go from idea to live product faster than ever.
Brisbane, Nepal and the Philippines building side by side.
No. Coders will do the building, but every team needs people for requirements, testing, marketing materials and the website. If you know the business, you can add real value.
It's top secret until the 11am briefing on the day, when team captains get the brief. All three teams get the same challenge.
No building, no code and no prep on the solution beforehand. Everyone starts from zero at 11am. You're welcome to warm up your brain on the problem areas above.
Every team gets access to an AWS dev playground, Truckit API credentials and AI tools. Beyond that, use company data and whatever else helps. If you need anything extra, ask Saurav. The only rule is no no-code builders. It has to be real, working software.
A working prototype you can demo live at 4pm, plus the marketing materials, website or collateral that show how it would go to market.
Demo what works. A focused prototype that works beats an ambitious one that crashes. Show the judges where it's heading, too.
Absolutely. Sit in, help a team with non-coding work, or jump on the Google Meet. Just balance it with your day job and check in with your manager.
A Google Meet runs all day. Use it for the 10:30am update, to drop in on teams, and for the 4pm presentations.
15 minutes per team, covering a live demo, your go-to-market pitch and questions from the judges.
Yes, it's on us. Nobody hacks well on an empty stomach.
It becomes a real Truckit product and goes live. The team also takes home the trophy and bragging rights until Hackathon #002.