How akshayap1101/ai-interview-pro works
Project type and purpose
• From the README and file-tree, this is a lightweight full-stack AI platform (“AI-Interview-Pro’n”) designed to help users prepare for interviews.
• The “client” folder contains a UI overlay component (Overlay.js) that likely injects interview prompts or hints into the user’s browser or application.
• The “server” folder contains an agent component (agent.js) that orchestrates calls to one or more AI/LLM services to generate or evaluate interview questions and answers.
File structure
• Top level:
• README.md
• client/Overlay.js
• server/agent.js
• There are exactly two runtime components:
• A front-end overlay that presents/intercepts interview content
• A back-end “agent” microservice that handles AI logic
• No DB or persistent-storage directory is present; all state is likely in memory or ephemeral.
• No build scripts or config files are shown, so we assume a simple npm/node setup for both client and server.
Key insights from README
• “An Agentic AI platform for interview prep” implies:
• The server “agent” will manage prompts, context, and interaction loops with the AI.
• The client “Overlay” will capture user actions (e.g. question display) and render suggestions, follow-ups, or feedback.
a. Main components
• Client Overlay (UI layer)
• Server Agent (business logic / AI orchestrator)
• External AI/LLM Service(s) (e.g. OpenAI, Anthropic, local model endpoint)
b. Relationships / Data flow
1. User interacts with the Interview UI → Overlay.js intercepts event
2. Overlay.js → REST/WebSocket → Server.agent.js
3. agent.js → AI/LLM API (send user prompt, context)
4. LLM → agent.js (response)
5. agent.js → Overlay.js (processed suggestions or follow-ups)
6. Overlay.js → Renders suggestions back to user
c. Architectural patterns
• Two-tier client-server (thin client, stateless backend)
• Agent pattern: the server encapsulates AI-specific logic and retry/temperature tuning
• Overlay injection pattern on the client for non-intrusive UI enhancement
d. Key technologies
• JavaScript/Node.js on both client and server
• REST or WebSocket for communication
• External AI API (OpenAI, Azure OpenAI, etc.)