How mahithabsl/ai-powered-hr-assistant works
Project Type and Purpose
• This is a domain-specific, full-stack data pipeline and question-answering application for HR, named “AI-Powered-HR-Assistant” (Graph-RAG).
• It processes PDF resumes into structured data, constructs a knowledge graph in Neo4j, and offers two interfaces:
• An interactive Streamlit chatbot UI for graph-based QA
• Jupyter notebooks for interview-question generation and metadata exploration.
File Structure Analysis
• Top-level scripts and notebooks:
• Pdf_2_Text.py: PDF ingestion and text extraction
• MetaData_Extraction.ipynb: Structured metadata extraction from text
• Pdf_2_Graph.py: Graph construction into Neo4j
• Graph_QA.py: Streamlit app for graph-based QA
• Generate_Interview_Questions.ipynb: Interview Q generation
• Data folder:
• data/resumes: raw PDF resumes
• data/metadata: metadata spreadsheets
• data/resume_data.csv: intermediate CSV
• Configuration:
• config.ini: Neo4j credentials, API keys, PDF processing parameters
• Static assets: images/css for the UI in static/
Key Components
• Frontend: Streamlit-based Chatbot UI
• Backend services:
• PDF Processing Module (Pdf_2_Text)
• Metadata Extraction Notebook/Module
• Graph Builder Module (Pdf_2_Graph)
• QA Module (Graph_QA)
• Interview Question Generation (notebook)
• Database: Neo4j graph database
• External Services:
• LLM Providers (OpenAI, Groq, Ollama)
• Embedding Providers (Cohere, OpenAI, Ollama)
• Storage:
• Local file system (PDFs, CSV, Excel metadata)
Relationships and Data Flows
• PDF files → Pdf_2_Text → raw text
• Raw text → MetaData_Extraction → structured JSON/CSV
• Structured data + PDFs → Pdf_2_Graph → Neo4j
• Streamlit UI / Graph_QA:
• Retrieved data → LLM (RAG) → generated answer → UI
• Interview Q Gen notebook calls APIs/graph to produce questions
Architectural Patterns and Design Principles
• Modular pipeline: each stage isolated (ingestion, extraction, graphing, QA)
• RAG pattern: retrieval from graph + generative LLM
• Layered design: UI layer, processing layer, persistence layer, external services
• Config-driven: all credentials and parameters in config.ini
Essential Elements
• Arrowheads indicating data flow direction
• Annotations for protocols (e.g., Bolt, HTTP, API calls)