How vadiml1024/jobhunterai works
Main system components
• Frontend (Client Layer): Represented by the “client” directory, it contains the React code (pages, components, hooks, layouts, and UI elements). Note the distinct UI sections such as Dashboard, Jobs, Applications, Resume Management, and Profile.
• API/Backend Layer: Resides in the “server” directory and includes modules for authentication, calendar integration, job boards, LinkedIn integration, file uploads, and configuration. This layer also encapsulates the LLM service integration (with files like llm-service.ts, openai.ts, gemini.ts).
• AI Service Layer: Abstracts over different AI providers (OpenAI and Gemini) to power features like resume analysis, cover letter generation, and chat support. This should be highlighted as a sub-component of the backend or as an external service.
• Data Layer: Use a PostgreSQL database to store user profiles, resumes, job data, and application statuses, with Drizzle ORM (configuration in drizzle.config.ts and shared schema files) as the interface.
• External Integrations: Include integration points such as LinkedIn (for profile import), calendar services (e.g., Google Calendar), and possibly external job board APIs.
Interactions
• AI Service Layer as a module that the API calls into for features like resume analysis or job recommendation.
• External integrations (LinkedIn API, calendar services, job boards) connecting with the API layer.
Architectural patterns and technologies
• Separation of concerns: UI (React with TypeScript, TanStack Query, Shadcn/UI, Tailwind CSS) is separated from business logic (Express backend) and data persistence (PostgreSQL with Drizzle ORM).
• That the file tree indicates a modular, component-based structure for the client and a route-centric design for the server, reflecting clean architectural practices.
• Out the use of configuration files (e.g., vite.config.ts, postcss.config.js, tailwind.config.ts) which solidify the toolchain setup.
• Shared code (in “shared/schema.ts”) to show how the system maintains consistency between the client and server.
Detailed system design elements
• Frontend Components: Represent the main UI modules such as Dashboard, Applications, Jobs, Resume Management, Profile, and AI Chat Assistant. You might abstract these as a collective “Client Layer” with internal subdivisions.
• Backend Modules: Represent key files such as auth.ts, calendar.ts, jobboards.ts, and routes.ts under the API layer. Indicate that these modules interact with each other as well as with external services.