October 30-31

Grab's biggest hacking event

Are you ready?

Register

Pick your battle

Technically Challenging

How far can you go as an engineer and show off your amazing skills?
The projects with the highest technical complexity that use new technologies and framework will be rewarded.

Hyper Local

Because we love to be close to our communities and stay true to our values:
Tailor to our lovely customers, the awesome people of South East Asia, to get rewarded!

Metric Mover

Can your amazing project help raise Grab's rides, profit per ride, or CE efficiency?
The most game-changer that promise amazing data will be rewarded!

Win amazing prizes

Google Wifi

Beats Headphones

Amazon Vouchers

And more to be announced!

Impress the judges

Amit Saini

Andrew Michalik

Hannah Vergera

Minci Loh

Sherizan Sheikh

Don't have an idea yet?

Don't worry! Join our Shark Tank event to get a chance to join a team.
Listen to the great pitches given by our intrapreneurs and find a project you'll love!

If you have an idea but you need more team members, that's your time to shine!
Prepare a 3 minutes presentation of your project that includes your ideal team roaster. The most successful teams are the ones who have a variety of backgrounds and experiences!

Happy Hour - Chill Zone (L3)

Save the date: October 20th

Schedule

Day 1 - October 30th
12:00 AM Registration close
10:00 AM Registration confirmation
10:30 AM T-shirt distribution
10:45 AM Introduction from Anthony and Ling
11:00 AM Explain the rules and developer constraints & Grabathon commencement
12:30 PM Lunch
07:30 PM Dinner
11:00 PM Lucky draw prize #1
Day 2 - October 31st
01:00 AM Lucky draw prize #2
03:00 AM Lucky draw prize #3
08:30 AM Breakfast
12:00 PM Grabathon Ends
12:30 PM Lunch + Presentations

Developers Rules

  • Make sure all code is in the grabathon repository. Create a sub folder under Oct2017 with your team code. You can upload it close to finishing to avoid any merge conflicts / accidentally deleting someone else's code.
  • Do not make any modifications on staging or production, or teams will face disqualification.
  • Do not use existing staging / production keys if you are using 3rd party tools like Twilio / Nexmo / Google etc.
  • You can use your team's sub account for projects but remember to get approval from the owner of the subaccount that you have access to. These should be developer test sub accounts not sub accounts like Data Engineering which has production workloads.
  • Destroy all instances after they are used.
  • Keep your AWS usage under SG$25 per team.
  • Existing APIs on staging are accessible for your projects. Alternatively, you might want to check out Marionette and Marionette API by the Internal Tools team.