calvintennant

Onfleet, San Francisco, On-site, Lead Mobile Engineer

We’re looking for a top-notch lead mobile engineer to take our iOS and Android apps to the next level. Substantial experience (2+ years) with both iOS and Android is a must. A deep understanding of mission-critical, location-based applications (especially the challenges around global use) is a huge plus.

We're building a modular platform that solves the hard technical problems around fleets of mobile workforces (e.g. route optimization, simplified dispatch UX/UI, real-time location tracking, driver mobile apps for multiple platforms). We provide an end-to-end solution for assigning work, tracking drivers and driver performance, and providing a delightful end-user experience with automatic SMS updates including accurate ETAs and a map to track deliveries en route. Onfleet powers hundreds of thousands of deliveries every month, for hundreds of businesses around the world.

Our backend is built using the latest technologies, including Node.js, Redis, Postgres, MongoDB, and WebSockets. Our product is mission-critical, so reliability and stability are essential. Our mobile apps use the latest frameworks and must be extremely robust in all types of device and connectivity situations. Our customers’ drivers see our apps as their most essential work tool and spend much of their day interacting with them.

As our third engineering hire, and only dedicated mobile engineer, you will work very closely with our product-focused founding team to bring a perfect delivery management experience to SMBs and other delivery-centric tech companies, enabling them to scale their businesses and delight their customers. We’ve recently passed the 1M delivery mark and are growing aggressively on all fronts month over month.

More details here: https://onfleet.com/careers

Feel free to email our VP of Engineering m[at]onfleet.com with any questions you might have.

Onfleet, San Francisco, On-site, Lead Mobile Engineer

We’re looking for a top-notch lead mobile engineer to take our iOS and Android apps to the next level. Substantial experience (2+ years) with both iOS and Android is a must. A deep understanding of mission-critical, location-based applications (especially the challenges around global use) is a huge plus.

We're building a modular platform that solves the hard technical problems around fleets of mobile workforces (e.g. route optimization, simplified dispatch UX/UI, real-time location tracking, driver mobile apps for multiple platforms). We provide an end-to-end solution for assigning work, tracking drivers and driver performance, and providing a delightful end-user experience with automatic SMS updates including accurate ETAs and a map to track deliveries en route. Onfleet powers hundreds of thousands of deliveries every month, for hundreds of businesses around the world.

Our backend is built using the latest technologies, including Node.js, Redis, Postgres, MongoDB, and WebSockets. Our product is mission-critical, so reliability and stability are essential. Our mobile apps use the latest frameworks and must be extremely robust in all types of device and connectivity situations. Our customers’ drivers see our apps as their most essential work tool and spend much of their day interacting with them.

As our third engineering hire, and only dedicated mobile engineer, you will work very closely with our product-focused founding team to bring a perfect delivery management experience to SMBs and other delivery-centric tech companies, enabling them to scale their businesses and delight their customers. We’ve recently passed the 1M delivery mark and are growing aggressively on all fronts month over month.

More details here: https://onfleet.com/careers

Feel free to email our VP of Engineering m[at]onfleet.com with any questions you might have.

Onfleet, San Francisco, On-site, Backend engineer

We're looking for a top-notch backend engineer, with the opportunity to grow into much more. Backend experience and/or experience with building RESTful APIs is a must. Frontend experience is a plus.

We're building a modular platform that solves the hard technical problems around fleets of mobile workforces (e.g. route optimization, simplified dispatch UX/UI, real-time location tracking, driver mobile apps for multiple platforms). We provide an end-to-end solution for assigning work, tracking drivers and driver performance, and providing a delightful end-user experience with automatic SMS updates including accurate ETAs and a map to track deliveries en route. Incumbent fleet management software is antiquated, pre-smartphone era, and expensive.

Our backend is built using the latest technologies, including Node.js, Redis, MongoDB, and WebSockets. Our product is mission-critical, so reliability and stability are critical.

As our third engineering hire, you would work very closely with our product-focused founding team to bring a perfect delivery management experience to SMBs and other delivery-centric tech companies, enabling them to scale their businesses and delight their customers.

More details here: https://onfleet.com/careers

Feel free to email our VP of Engineering m[at]onfleet.com with any questions you might have.

Onfleet, San Francisco, On-site, Backend engineer

We're looking for a top-notch backend engineer, with the opportunity to grow into much more. Backend experience and/or experience with building RESTful APIs is a must. Frontend experience is a plus.

We're building a modular platform that solves the hard technical problems around fleets of mobile workforces (e.g. route optimization, simplified dispatch UX/UI, real-time location tracking, driver mobile apps for multiple platforms). We provide an end-to-end solution for assigning work, tracking drivers and driver performance, and providing a delightful end-user experience with automatic SMS updates including accurate ETAs and a map to track deliveries en route. Incumbent fleet management software is antiquated, pre-smartphone era, and expensive.

Our backend is built using the latest technologies, including Node.js, Redis, MongoDB, and WebSockets. Our product is mission-critical, so reliability and stability are critical.

As our third engineering hire, you would work very closely with our product-focused founding team to bring a perfect delivery management experience to SMBs and other delivery-centric tech companies, enabling them to scale their businesses and delight their customers.

More details here: https://onfleet.com/careers

Feel free to email our VP of Engineering m[at]onfleet.com with any questions you might have.

Onfleet, San Francisco, On-site, Backend engineer

We're looking for a top-notch backend engineer, with the opportunity to grow into much more. Backend experience and/or experience with building RESTful APIs is a must. Frontend experience is a plus.

We're building a modular platform that solves the hard technical problems around fleets of mobile workforces (e.g. route optimization, simplified dispatch UX/UI, real-time location tracking, driver mobile apps for multiple platforms). We provide an end-to-end solution for assigning work, tracking drivers and driver performance, and providing a delightful end-user experience with automatic SMS updates including accurate ETAs and a map to track deliveries en route. Incumbent fleet management software is antiquated, pre-smartphone era, and expensive.

Our backend is built using the latest technologies, including Node.js, Redis, MongoDB, and WebSockets. Our product is mission-critical, so reliability and stability are critical.

As our third engineering hire, you would work very closely with our product-focused founding team to bring a perfect delivery management experience to SMBs and other delivery-centric tech companies, enabling them to scale their businesses and delight their customers.

More details here: https://onfleet.com/careers

Feel free to email our VP of Engineering m[at]onfleet.com with any questions you might have.

Onfleet, San Francisco, On-site, Backend engineer

We're looking for a top-notch backend engineer, with the opportunity to grow into much more. Backend experience and/or experience with building RESTful APIs is a must. Frontend experience is a plus.

We're building a modular platform that solves the hard technical problems around fleets of mobile workforces (e.g. route optimization, simplified dispatch UX/UI, real-time location tracking, driver mobile apps for multiple platforms). We provide an end-to-end solution for assigning work, tracking drivers and driver performance, and providing a delightful end-user experience with automatic SMS updates including accurate ETAs and a map to track deliveries en route. Incumbent fleet management software is antiquated, pre-smartphone era, and expensive.

Our backend is built using the latest technologies, including Node.js, Redis, MongoDB, and WebSockets. Our product is mission-critical, so reliability and stability are critical.

As our third engineering hire, you would work very closely with our product-focused founding team to bring a perfect delivery management experience to SMBs and other delivery-centric tech companies, enabling them to scale their businesses and delight their customers.

More details here: https://onfleet.com/careers

Feel free to email our VP of Engineering m[at]onfleet.com with any questions you might have.

And we're back.

"for people who wants to censor" AAARRRRGH. Grammar.

Thanks for the python wrapper Dan! That was passed around the office a couple weeks ago, we were all quite happy to see it.

More of a happy accident, I guess. I don't think we realized "on fleek" was a thing until long after we had the domain.

You don't think we can hop on the momentum there? "This craft ice cream delivered on-demand to my door is #onfleet".

And thanks :)

"Apple would be looking to make such an enormous leap from its core competency — building great consumer electronics".

Don't electric cars fall into the category of consumer electronics?

What the fuck kind of quotes are those?

Heh: https://blockchain.info/address/18PyfH1AqV2DbEweh6USf1HYg7D9...

No transactions found for this address, it has probably not been used on the network yet.

It continues: http://imgur.com/6XRxpkk

In other news: http://imgur.com/6XRxpkk

In the `Asynchronous Wait` example did you mean: `function getUserFriends(userName, next) {` when you wrote: `var getUserFriends(userName, next) {`?

Techcrunch article: http://techcrunch.com/2012/11/28/gorgeous-photos-in-your-poc...

Another update lets the user add in their own chords: http://calvintennant.ca/learningguitar/12-08-21/

Dosen't really justify another post, but I wrote a little update that lets the user pick chords: http://calvintennant.ca/learningguitar/12-08-20/

Release early, release often.

Thanks :) I was planning on adding the chord chart to help me learn some more chords.

And because I'm a content-management geek: http://codepen.io/anon/pen/wxytJ

Ahha, actually I did. A friend pointed it out minutes after I posted the petition and I corrected it.

For sure, I expect that Google Fiber will be available throughout most of the US before the service comes to Canada, but prepending their arrival here the CRTC will have to restructure some of the laws that are currently in place. I feel it is best for Google to know that there is demand here sooner so that they can start having these kinds of discussions with Canadian lawmakers.

I hope that we can have this discussion; I've even created a repo for it: https://github.com/calvintennant/Open-Specification-for-Broa.... There are a lot of issues with how the CRTC is operating, I hope we can induce change.

It's not as important to get Google to pay attention as it is to get the CRTC to pay attention. There are laws in place preventing foreign competition in the Canadian marketplace, which in conjunction with other laws have essentially created a non-competition environment for Canadian ISPs. This petition is more about generating awareness for Canadians and and to trying and formulate a discussion around change.

Also posted this on Reddit for those of you there: http://www.reddit.com/r/technology/comments/pst53/att_fcc_al...

This is a really big issue, Canada faced usage-based-billing once already. Big telcos need to know that we're not going to put up with their caps.