dotlas / mission_dotlas

🥁 An engaging data science & engineering assessment for internships & part-time roles

Mission Dotlas 🌎

📆 Fall 2023

• Mission Dotlas 🌎
  • Overview
    • About us
    • The Mission
  • Getting started
    • Create a Private fork
    • Install Python v3.9 or higher
    • Install dependencies
    • Get crackin'
    • Learning resources
  • Evaluation
    • Submission
    • Criteria
    • Nice-to-have
    • Contact

⚠️ Warning

Applicants will be disqualified if they make a public fork of this repository. Create a private fork instead.

Overview

About us

We at Dotlas are building a platform for controlling, optimizing & growing retail businesses through AI-driven insights. We've been refining and revamping this assignment for a while now, and we're excited to see what you can do with it! Optionally view past assignments, along with stats in the archives

The Mission

Your mission, should you choose to accept it, is to transform, process and analyze our dataset of Restaurants in The State of California, USA. Here are a few maps to get you inspired!

Restaurants in California

Restaurants in Los Angeles, grouped into Hexagons according to their Price Range

Restaurants in Los Angeles, on a Grid, height indicates count

Restaurants in San Francisco, according to their Dress Code, height indicates count

We've uploaded our dataset to an interactive map on Foursquare Studio. Feel free to explore it.

Getting started

Create a Private fork

Let's create a private fork of this repository:

• Go to the Import a repository page on GitHub

• Fill in the information as shown below:

  

  How to create a private fork

Once the repository is created on GitHub, clone it onto your local system!

Install Python v3.9 or higher

• You can download it from the Python website

• Or, you can install Anaconda and run the following command in your terminal:

  conda create --name dotlas python=3.9 -y
  conda activate dotlas

Install dependencies

python -m pip install -r requirements

You may install any additional dependencies!

Get crackin'

Your mission's details are displayed in mission.ipynb.

Learning resources

Please refer to HELP.md for some resources to help you get acquainted with the tools you will need.

Evaluation

Submission

Once you're ready for evaluation, invite us as private collaborators to your private fork!

Criteria

Submissions will be judged on:

• Readability & maintainability of code
• Correctness & approach to the solution
• Use of "best practices" by adhering to the Pythonic way

Nice-to-have

Incorporating the following will be marginally helpful to the graders to reduce friction in evaluating your assignment

• Do not create additional branches on your private repository with the submission. Keep all changes on the main branch.
• Add your answers to the same jupyter notebook file.
• Do not delete markdown sections of the jupyter notebook. Feel free to add as many sections for documentation or otherwise as you need but don't delete sections already present.

Contact

Feel free to reach out to us, should you have any questions.

Name	LinkedIn	GitHub
Nuno Freitas	https://www.linkedin.com/in/nunoamaralfreitas/	https://github.com/NaFreitaz
Eshwaran Venkat	https://linkedin.com/in/eshwaranv98/	https://github.com/cricksmaidiene
Kelvin DeCosta	https://linkedin.com/in/kelvindecosta/	https://github.com/kelvindecosta

Feel free to ping us anytime for support.

May the Force be with You!