How hosanna1616/ai-recruiter- works
Main Components
a. Frontend (React + Material-UI)
b. Backend API (Node.js + Express)
c. Database (SQLite)
d. AI-Screening Service (internal module or external API)
e. File‐Storage (for resumes)
f. External Services (e.g., email/SMS scheduler)
Relationships and Data Flows
• The React App communicates via REST calls (HTTP/HTTPS) to the Express API.
• Express routes invoke controllers (auth, candidate, job, resume).
• Controllers use models (User, Job, JobApplication) via an ORM or raw SQL to read/write the SQLite database.
• The resume controller passes uploads through upload.middleware, stores files, and may invoke the AI-Screening module.
• The AI-Screening Service returns candidate scores/insights to the backend, which persists results and exposes them to the frontend.
• Real-time analytics data is fetched from the database or pushed via a websocket/pub-sub layer to the dashboard React pages.
• Interview scheduling may integrate with an external calendar/email API.
Architectural Patterns
• Layered MVC-style backend (middleware → controllers → models → database).
• RESTful API design.
• Componentized frontend (pages → reusable components → assets).
• Separation of concerns: UI, business logic, data access, and external integrations isolated into distinct modules.
Technologies & Frameworks
• Frontend: React, Material-UI, Recharts, React Router
• Backend: Node.js, Express, sqlite3 (via config/db.config.js), multer in upload.middleware.js
• AI Screening: custom JS module or external AI API called within resume.controller.js
• Auth: JWT or session-based in auth.middleware.js + auth.controller.js
• Database: SQLite files (database.sqlite, quenerecruit.sqlite) initialized via config/init-db.js and importSchema.js