EvoX Genesis
EvoX Genesis turns a high-level software objective into a persistent recursive software world: finite-lived agents recursively develop software, while only accepted consequences persist across develop
Analyze resumes through an API
Translation pending
AI summary · website content
Developer toolsTypeScript · PythonGitHub @SyedMuhammdSohaibOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗An AI-powered web app that analyzes a resume and gives clear, useful feedback: strengths, weaknesses, missing skills, and suggestions for improvement.
Built as a beginner-friendly MVP using LangChain, FastAPI, Groq and Next.js.
| Layer | Technology |
|---|---|
| Frontend | Next.js, React |
| Backend | Python, FastAPI |
| AI | LangChain + Groq API |
resume-analyzer/
├── backend/ # FastAPI server + LangChain logic
├── frontend/ # Next.js user interface
└── README.md
git clone https://github.com/SyedMuhammdSohaib/AI-ResumeAnalyzer.git
cd AI-ResumeAnalyzer
cd backend
python -m venv venv
# Windows
venv\Scripts\activate
# Mac/Linux
source venv/bin/activate
pip install -r requirements.txt
cp .env.example .env
Edit backend/.env to fill in your keys.
If the model gives a 404 for your key, set GROQ_MODEL to openai/gpt-oss-120b or llama-3.3-70b-versatile.
Start the server:
uvicorn app.main:app --reload
The API runs at http://localhost:8000.
Open a new terminal:
cd frontend
npm install
cp .env.example .env.local # or set NEXT_PUBLIC_API_URL in your shell
npm run dev
The app runs at http://localhost:3000.
Windows shortcut: double-click start-resume-analyzer.bat in the project root. It starts both servers and opens the browser.
With the backend running:
cd backend
pip install httpx
python test_analyze.py
| Method | Path | What it does |
|---|---|---|
| GET | /health | Health check |
| POST | /analyze | Form: file (PDF or DOCX), optional job_description, language |
| POST | /rewrite | JSON: { "text": "...", "job_description": "..." } → 3 rewrites |
| POST | /improve | Form: file (PDF or DOCX), optional job_description → weak lines + fixes |
| POST | /improved-cv | Form: file (PDF or DOCX), optional job_description, rewrites, format (docx or pdf) → file |
| POST | /cover-letter | Form: file (PDF or DOCX), job_description → cover letter text |
| POST | /skill-roadmap | Form: file (PDF or DOCX), optional job_description, target_role, language → learning roadmap |
The backend includes backend/api/index.py and backend/vercel.json, so it can run on Vercel as a Python serverless function.
backend and Framework Preset to Other.GROQ_API_KEY, GROQ_MODEL and ALLOWED_ORIGINS (see the table below).https://<your-backend>.vercel.app/health. It should return {"status":"ok"}.Create a new Render Web Service and connect this repository.
Use the following settings:
pip install -r backend/requirements.txtuvicorn app.main:app --host 0.0.0.0 --port $PORT (Render sets $PORT; the included backend/Dockerfile also works if you prefer a Docker deploy)Add the following environment variables under Environment:
| Variable | Description | Example |
|---|---|---|
GROQ_API_KEY | Your Groq API key | gsk_... |
GROQ_MODEL | LLM model to use | openai/gpt-oss-120b (or llama-3.3-70b-versatile) |
ALLOWED_ORIGINS | Comma-separated list of allowed frontend origins (CORS) | https://your-app.vercel.app,http://localhost:3000 |
Deploy the service. Your backend URL will be something like https://your-backend.onrender.com.
Import this repository into Vercel.
Set the project root to frontend in Vercel project settings.
Add the following environment variable:
| Variable | Description | Example |
|---|---|---|
NEXT_PUBLIC_API_URL | Base URL of your deployed backend (no trailing slash) | https://your-backend.onrender.com |
Deploy. The frontend will call ${NEXT_PUBLIC_API_URL}/analyze.
Update ALLOWED_ORIGINS on your Render backend to include your new Vercel URL.
Notes:
.env and related files. See backend/.env.example and frontend/.env.example.ALLOWED_ORIGINS (comma-separated). By default it allows http://localhost:3000 for local development.process.env.NEXT_PUBLIC_API_URL (falls back to http://127.0.0.1:8000 for local development).Syed Muhammad Sohaib GitHub: @SyedMuhammdSohaib
This project is open source and available for learning purposes.