How alexd36/career-advisor-ai-mvp works
Project type and purpose
• This is a full-stack web application called “Next Step — AI-Powered Career Advisor.”
• Frontend: Next.js + Tailwind CSS offering pages and interactive components (career path discovery, CV builder, interview simulator, dashboards).
• Backend: Spring Boot REST API serving business logic (user management, OpenAI integration, CV PDF generation, interview sessions) and persisting data in MySQL.
• External services: OpenAI GPT-4 for AI features, Google OAuth 2.0 for authentication.
File structure
Top-level:
• frontend/Meta – Next.js app folder (app-router pages, shared components, hooks, utilities, Tailwind styles, Dockerfile).
• backend/Meta – Spring Boot project (controllers, services, models, repositories, security & CORS config, application.properties).
• career_db_dump.sql – initial MySQL dump.
• podman-compose.yml & start.bat – container orchestration for frontend, backend, MySQL.
Backend directory breakdown:
• controller – REST endpoints (AuthController, ChatGPTController, CvController, etc.).
• service – business logic layers (ChatGPTService, JwtService, UserService, etc.).
• repository – Spring Data JPA interfaces (UserRepository, InterviewSessionRepository, etc.).
• model/dto – persistence entities and data‐transfer objects.
• config & auth – JWT filters, security, CORS, OpenAPI docs.
Frontend directory breakdown:
• app – Next.js routes under /app (login, signUp, dashboard roles, cvTools, interview-sim, etc.).
• components/ui – reusable UI building blocks (Button, Card).
• hooks & lib – custom React hooks (useAuthToken, useAxiosAuth) and utility functions.
• public – static assets.
• next.config.ts, package.json – build configuration.
Detail without clutter
• Controllers (Auth, ChatGPT, CV, Interview, User, Admin, Mentor, DailyTask) grouped under “API Endpoints.”
• Service layer between controllers and repositories, label key services (ChatGPTService, JwtService, CvPdfService).
• Repository layer connecting to MySQL.
• ChatGPTService → OpenAI GPT-4 API
• AuthController → Google OAuth 2.0
• That the frontend uses custom hooks (useAuthToken, useAxiosAuth) to manage tokens and API calls.