Working on the “back-end” in our architecture involves more than just your typical back-end workload, as Hurdlr’s API is consumed by products other than just Hurdlr’s apps. Hurdlr’s back-end also consumes 15+ APIs, with several years worth of new and intriguing integrations on the roadmap.
See hurdlr.com/tax-api for examples. Furthermore, Hurdlr’s API has tracked more than $6B in finances, opening up lots of opportunities for predictive analytics and other “big data” opportunities.
Working on the “front-end” in our architecture involves more than working on your traditional front-end, as much of our core technology sits on the phone/front-end itself, including an auto-sensing mileage-tracking algorithm using GPS, which we built from scratch, full offline edit capabilities, and more.
We believe that developers should pick an area of focus, based on their interest and existing skill set, and then gradually learn other parts of the stack. That way, the developer can contribute immediately while also learning for the future.