Coding Challenge Guidelines
If you don't have code to share, you can work on our coding challenge described below.
Please organize, design, test, document and deploy your code as if it were going into production, then send us a link to the hosted repository (e.g. Github, Bitbucket...).
Prototype one of the following projects:
- Departure Times
- SF Movies
- Email Service
- Food Trucks
The UX/UI is totally up to you. If you like, get creative and add additional features a user might find useful!
Create a service that gives real-time departure time for public transportation (use freely available public API). The app should geolocalize the user.
Here are some examples of freely available data:
Create a service that shows on a map where movies have been filmed in San Francisco. The user should be able to filter the view using autocompletion search.
Create a service that accepts the necessary information and sends emails. It should provide an abstraction between two different email service providers. If one of the services goes down, your service can quickly failover to a different provider without affecting your customers.
Example Email Providers:
- SendGrid - Simple Send Documentation
- Mailgun - Simple Send Documentation
- SparkPost - Developer Hub
- Amazon SES - Simple Send Documentation
All listed services are free to try and are pretty painless to sign up for, so please register your own test accounts on each.
Create a service that tells the user what types of food trucks might be found near a specific location on a map.
The architecture will be split between a back-end and a web front-end, for instance providing a JSON in/out RESTful API. Feel free to use any other technologies provided that the general client/service architecture is respected.
Choose one of the following technical tracks that best suits your skillset:
- Full-stack: include both front-end and back-end.
- Back-end track: include a minimal front-end (e.g. a static view or API docs). Write, document and test your API as if it will be used by other services.
- Front-end track: include a minimal back-end, or use the data service directly. Focus on making the interface as polished as possible.
We believe there is no one-size-fits-all technology. Good engineering is about
using the right tool for the right job, and constantly learning about them.
Therefore, feel free to mention in your
README how much experience you have
with the technical stack you choose, we will take note of that when reviewing
Here are some technologies we are more familiar with:
You are also free to use any web framework. If you choose to use a framework that results in boilerplate code in the repository, please detail in your README which code was written by you (as opposed to generated code).
The front-end should ideally be a single page app with a single
linking to external JS/CSS/etc. You may take this opportunity to demonstrate
your CSS3 or HTML5 knowledge.
When you’re done, host it somewhere (e.g. on Amazon EC2, Heroku, Google AppEngine, etc.).