Welcome to the Used Car Price Prediction Challenge! 🎉 This project is designed to help you level up your end-to-end data science skills — from scraping real-world data, to building predictive models, to designing a user-friendly interface.
Each team will complete the entire workflow and compete to see who can engineer the best features and achieve the highest R² score.
-
Goal: Predict used car prices from dubizzle.com.om data.
-
Teams: 4 teams of 5 members each.
-
Focus: End-to-end ML pipeline + UI development.
-
Key Skill Areas:
- Data scraping & cleaning
- Feature engineering
- Regression modeling & evaluation
- R² score optimization
- Streamlit app development
- Team collaboration & presentation
-
Data Scraping & Cleaning
- Scrape used car listings from dubizzle.com.om.
- Handle challenges like missing data, text cleaning, and formatting.
- Deliver a clean dataset ready for modeling.
-
Feature Engineering
- Design and test new features to improve predictions.
- This is the main differentiator between teams.
-
Model Development
- Train at least 3 regression models (e.g., Linear Regression, Random Forest, XGBoost, Polynomial Regression).
- Evaluate on a test split using R² score.
- Select your best-performing model.
-
User Interface
- Build a Streamlit app where users can input car details and get price predictions.
- Focus on clarity, simplicity, and usability.
-
Presentation & Comparison
- Share your process, challenges, and results.
- Compete based on model accuracy, feature creativity, and app usability.
Your project will be judged on:
- Model Performance – R² score on test data.
- Feature Engineering – originality, usefulness, and impact.
- User Interface – usability, clarity, and design.
- Collaboration & Presentation – documentation and delivery.
git clone https://github.com/khoulaCode/Brain-Byte-Used-Car-Project
cd Brain-Byte-Used-Car-Projectpip install -r requirements.txtstreamlit run app.py├── data/ # Raw and cleaned datasets
├── notebooks/ # Jupyter notebooks for EDA and prototyping
├── src/ # Source code (scraping, modeling, utils)
├── app/ # Streamlit app files
├── requirements.txt # Project dependencies
├── README.md # Project documentation
└── LICENSE
All teams are solving the same problem. The key to winning is better feature engineering, smarter modeling, and a polished UI.