2. ● Shobhit, responsible for engineering at Mobility
● Mostly found in Bangalore
● At Go-jek since October, 2015
● Previously, co-founder @ CodeIgnition
● Worked on various teams, including
○ Systems
○ Kilat/Send
○ Allocation
4. Too many people involved!
&
Too much attention!
● Go-ride
● Allocation
● Data Science
● Driver Platform
● Data Engineering
● Go-Food
● Go-Send
● BoDs
6. Dynamic pricing
● Start from end state, break into small chunks:
○ Milestone 1: Chart of demand to supply ratio
○ Milestone 2: Manually defined surge multipliers
○ Milestone 3: Dynamic surge only in specific area
○ Milestone 4: Phased nationwide roll-out
● Iterative improvement: Balancing surge multipliers
across GO-RIDE, GO-FOOD, GO-SEND—multiple
service types served by the same fleet
8. Key takeaway: Iterate, iterate, iterate
● Always start small—you can be ambitious with the end
state, just don’t try to build the whole thing at once
● Make sure everyone working on a project feels like one team -
will require a lot of listening
● Regular cadence, and prompt distribution of information -
be it good or bad
● Involve people at right time - milestoning can help in
deciding when