How soaraway/taleq works
Project Type and Purpose
• This is a Next.js–based full-stack talent acquisition web application ("taleQ") that leverages AI to screen resumes, match candidates to jobs, and schedule interviews.
• Key features (from README): resume screening, AI–based matching/scoring, spam/fake resume detection, customizable job requirements, PDF generation, notification, file uploads, calendar view.
File Structure Analysis
• Top-level files: configuration for Next.js, ESLint, PostCSS, package.json, plus components.json (deployment metadata).
• public/: static assets.
• src/app/: Next.js App Router structure, with API routes under src/app/api/{generate-pdf, notify-interview, upload-jobs, upload-resume}/route.js.
• src/components/: reusable React UI components (Calendar, JobPosting, SearchBar, Settings, UploadResume, etc.) and a ui/ subfolder for primitive UI controls (button, card, table, etc.).
• src/lib/utils.js: shared utility functions (e.g., file validation, AI integration helpers).
Architecture Overview
• Browser (user) interacts with the Next.js Frontend (SSR/SSG + client-side React).
• Frontend calls serverless API Routes (hosted on Vercel or Node.js env) for:
a. Resume upload
b. Job posting upload
c. PDF generation
d. Interview notifications
• API routes orchestrate:
• File storage (e.g., S3 or Vercel Blob)
• Database operations (e.g., MongoDB, PostgreSQL) for jobs, resumes, users
• External AI service calls (e.g., OpenAI) for resume screening & matching
• Email/SMS service (e.g., SendGrid, Twilio) for notifications
• Future modules (per README “Things to do”): user authentication, calendar DB, email ingestion.
Components
• Frontend Layer
• User’s Browser / Mobile Client
• Next.js App (React)
• Backend Layer (Serverless Functions)
• UploadResume Service
• UploadJobs Service
• GeneratePDF Service
• NotifyInterview Service
• Data Storage
• Blob/File Storage (resumes, PDF)
• Database (job postings, resume metadata, user data, schedules)
• External Services
• AI/ML Engine (resume screening, spam detection, candidate scoring)
• Email/SMS Gateway
• Auth Provider (future)
• Utilities & Shared Libraries
• src/lib/utils.js for shared logic
Relationships and Data Flows
• Frontend → API Routes (POST /api/upload-resume, etc.)
• API Routes → File Storage (uploading CVs)
• API Routes → Database (CRUD operations)
• API Routes → AI Service (screening, matching) → back to DB or Frontend
• API Routes → Email/SMS Service for notifications
• API Routes → PDF Generation component → Blob Storage → returns PDF URL
Architectural Patterns & Principles
• Separation of Concerns:
• UI vs. API vs. Data Stores
• Micro-services style (each API route is its own function)
• Serverless design (deployable on Vercel Functions or AWS Lambda)
• Use of React component hierarchy for UI primitives vs. domain components
• Future extensibility points: authentication, calendar subsystem