How garvbhalla12/job-market-analyst works
The repository combines a FastAPI job-market API, whose implemented runtime workflow is authentication and refresh-token management, with a separate file-based job-data preparation workflow. The latter converts job JSON to CSV, cleans records, and extracts and counts technical skills. The supplied excerpts show those workflows but no connection between the analytics files and API. The graph therefore keeps them separate; it does not infer analytics endpoints or unseen integrations.
Main entry points: auth.py Auth routes · dependencies.py User dependency · skill_extraction.py Skill extraction · models.py User and token models
Components 16
Authentication API
- FastAPI app
backend/main.py - Auth routes
backend/routes/auth.py
Auth Internals
- Auth schemas
backend/schemas.py - Token security
backend/security.py - User dependency
backend/dependencies.py - User and token models
backend/models.py - SQLite database
backend/database.py
Job Data Analytics
- JSON conversion
convert_dataset.py - Job data cleaning
backend/data_cleaning.py - Skill extraction
backend/skill_extraction.py
Dataset Files
- Jobs JSON
dataset/jobs.json - Jobs CSV
dataset/jobs.csv - Cleaned jobs
dataset/jobs_cleaned.csv - Jobs with skills
dataset/jobs_with_skills.csv - Skill demand
dataset/skill_demand.csv
Other components
- API client
Connections 17
- API client → FastAPI app: calls API
- FastAPI app → Auth routes: registers routes
backend/main.py - Auth routes → Auth schemas: uses request models
backend/routes/auth.py - Auth routes → Token security: hashes and issues tokens
backend/routes/auth.py - Auth routes → User and token models: queries and updates
backend/routes/auth.py - Auth routes → SQLite database: gets DB session
backend/routes/auth.py - User dependency → SQLite database: gets DB session
backend/dependencies.py - User dependency → User and token models: loads user
backend/dependencies.py - User dependency → Token security: reads JWT settings
backend/dependencies.py - User and token models → SQLite database: uses declarative base
backend/models.py - Jobs JSON → JSON conversion: read by
convert_dataset.py - JSON conversion → Jobs CSV: writes
convert_dataset.py - Jobs CSV → Job data cleaning: read by
backend/data_cleaning.py - Job data cleaning → Cleaned jobs: writes
backend/data_cleaning.py - Cleaned jobs → Skill extraction: read by
backend/skill_extraction.py - Skill extraction → Skill demand: writes counts
backend/skill_extraction.py - Skill extraction → Jobs with skills: writes annotations
backend/skill_extraction.py