How saifshamsi28/jobnet-a-smart-job-finder works
Project Type and Purpose
• This is a full-stack mobile platform (“JobNet”) with three tiers:
• Android App (Java/XML + Room)
• Spring Boot backend (Java, JWT, MongoDB)
• Python/Flask microservices (Selenium scraper + resume parser)
File Structure
• Top level:
• app/ – Android client module (Activities, Adapters, API, Models, Database, Utils)
• Gradle scripts & wrapper – build and dependency management
• app/src/main/java/com/saif/jobnet:
• Activities – UI screens (Login, Main, JobList, JobDetail, Profile, etc.)
• Adapters – RecyclerViews for jobs, skills, saved jobs
• Api – Retrofit client & service interfaces
• Database – Room entities, DAOs, DatabaseClient
• Models – Data classes (Job, User, Resume, Skill, Education, etc.)
• Utils – Config, converters, watchers
• Resources: layouts, drawables, menus, animations for UI
README for Additional Insights
• Emphasizes key technologies: Android+Room, Retrofit, Spring Boot+MongoDB, Flask+Selenium, JWT, resume parsing
Main Components and Their Interactions
a. Android Client
• UI Layer (Activities + Layouts)
• Data Layer
– Local Cache: Room database
– Remote API: RetrofitClient → ApiService
• Image Loading: Glide (MyGlideModule)
b. Spring Boot Backend
• REST Controllers (jobs, auth, resume upload)
• Service Layer (JWT auth, business logic)
• Data Access: MongoDB (via Spring Data)
c. Flask Scraper Microservice
• Selenium-based scraper for Naukri/Indeed
• Exposes REST endpoint to fetch new jobs
d. Flask Resume Parser
• Parses uploaded resumes to extract skills/experience
• Called by Spring Boot for recommendations
e. Data Stores & External Systems
• MongoDB – primary data store for jobs, users, resumes
• External Job Sites – Naukri, Indeed
Architectural Patterns and Design Principles
• Android: MVC/MVVM-style separation (Activities → Adapters → Room)
• Repository Pattern for Room + Retrofit
• RESTful API between client and backend
• Microservices separation: scraper and parser decoupled from core API
• Caching Pattern: Room for offline, MongoDB for server-side cache
• JWT for stateless, secure authentication
• Left: Android App block
• Sub-blocks: UI (Activities), Offline Cache (Room), Network Client (Retrofit)
• Center: Spring Boot Backend block
• Sub-blocks: Auth Service, Job Service, Resume Service
• Right: Microservices & Data
• Flask Scraper (→ External Sites)
• Flask Resume Parser
• Far Right: External Systems
• Android → Spring Boot:
• GET /jobs → returns list (cached in Room)
• POST /login → returns JWT
• POST /resume → triggers resume parsing & recommendations
• Spring Boot → MongoDB: read/write jobs, users, resumes
• Spring Boot → Flask Scraper: “if job not in DB” → fetch fresh from Naukri/Indeed
• Flask Scraper → External Sites: web scrape via Selenium → return jobs
• Spring Boot → Flask Parser: send uploaded resume → receive parsed data
• Spring Boot → Android: deliver parsed recommendations