Welcome to RAKT's unique and exciting way of discovering new talent. At RAKT, we believe in fun, creativity, and thinking outside the box. This challenge is your playground to showcase your skills in a way that's both enjoyable and insightful.
- Enjoy the Process: We want you to have fun with this challenge. Think of it as a mini-hackathon where your creativity and innovation can shine.
- Reflect Real-World Scenarios: Just like our work at RAKT, this challenge mirrors real-world scenarios but with a twist of fun and creativity.
- No Pressure: Say goodbye to the traditional, high-pressure coding interviews. We're more interested in how you think and create, not just how you code under stress.
Our team in San Francisco are on a quest to discover the hidden gems of street food, particularly food trucks! Your challenge is to to make it possible for us to find a food truck no matter where our work takes us in the city.
This is a freeform assignment. You can write a web API that returns a set of food trucks (our team is fluent in JSON). You can write a web frontend that visualizes the nearby food trucks. We also spend a lot of time in the shell, so a CLI that gives us a couple of local options would be great. And don't be constrained by these ideas if you have a better one!
The only requirement for the assignment is that it give us at least 5 food trucks to choose from a particular latitude and longitude.
Feel free to tackle this problem in a way that demonstrates your expertise of an area -- or takes you out of your comfort zone. For example, if you build Web APIs by day and want to build a frontend to the problem or a completely different language instead, by all means go for it - learning is a core competency in our group. Let us know this context in your solution's documentation.
San Francisco's food truck open dataset (csv) is included in this repo.
- Time Commitment: Dedicate around three hours of focused work to this assignment. Quality matters more to us than quantity, so there's no need to overengineer your solution.
- Real-World Simulation: Treat this task as you would a project intended for production. Create a GitHub repository, use git for version control, and document your project in a README.md file.
- Production-Oriented: Your solution should reflect what you would deliver in a production environment. We understand this might limit the scope within the given time, but we prefer a production-ready approach over a feature-heavy one.
- Documentation and Rationale: Document your technical decisions, trade-offs, and any considerations you had. If you had more time or were to do it again, let us know what you would change or improve.
- Flexibility in Tools and Languages: Please use django as your framework but do not limit yourself to vanilla django, feel free to use everything you'd like on top of it.
- Private Fork: Instead of forking the public repository, create a copy of it. You can do this by cloning the repository to your local machine and then pushing it as a new public repository under your own GitHub account.
- Document Your Process: Include a README.md in your submission detailing how to set up and run your script. This should be unique to your implementation and understanding.
- Comment Your Code: Ensure your script is well-documented with comments that explain your logic and approach. This documentation should reflect your personal problem-solving process.
- Email Submission: Rather than creating a pull request, which is public, send us a link to your public repository via email to [email protected] with the title "[P1-Submission] Your name". Ensure your repo is public so that we can access it.
- Deadline: Please submit your assignment within 5 days of receiving these instructions.