How hunchd/job-market-analysis works
Main Components
• Data Sources: The primary dataset originates from external sources (i.e., Kaggle’s job postings) which is later cleaned using Excel.
• ETL (Data Preparation) Layer: This is represented by the “sql_load” folder that contains the scripts to create the database, tables, and make schema modifications.
• Database System: MySQL is used as the DBMS where the cleaned data is loaded.
• Query & Analysis Layer: The “Job_Market_EDA” folder houses multiple SQL files each answering specific analysis tasks (e.g., salary analysis, remote work trends, skills analysis, etc.).
• Visualization & Reporting: The “assets” folder includes generated graphical outputs (bar graphs, pie chart, etc.) and is also utilized for creating presentation-ready charts.
Relationships and Data Flow
• The Database (MySQL) then serves as the central repository.
• SQL queries in the “Job_Market_EDA” folder are executed against this database to produce analyses corresponding to:
• Job trends and demand,
• Salary analysis,
• Skills and their related salaries,
• Remote work analysis,
• Education and job correlations,
• Geographical insights.
• The results of these queries are visualized (saved in the assets folder) and documented within the README.
Architectural Patterns and Technologies
• Separation of concerns: Notice that ETL, data storage, analysis logic, and visualization are clearly separated into different folders.
• Use of SQL-centric analysis: The project emphasizes in-depth querying using advanced SQL techniques (CTEs, window functions, subqueries) in the Job_Market_EDA layer.
• The analytical flow follows a “data ingestion – processing – analysis – visualization” pattern.
• Technologies include Excel (for cleaning and visualization post-processing), MySQL (database operations), and Git (version control) as noted in the README.