How vishwajeetdabholkar/resume_parser_api works
Project Type & Purpose
• This project is a full-stack backend API service built with FastAPI. Its main purpose is to process PDF resumes, perform OCR (leveraging Tesseract and Poppler), and extract structured information using AI (through OpenAI’s API) including text embeddings.
Analyzing the File Structure
• Notice the “app” folder that is organized into sub-modules:
• “api/routes/”: Contains the API endpoint definitions (resume parsing endpoints).
• “services/”: Contains core business logic. For instance, “pdf.py” is the PDF processing service and “ai.py” is the service managing OpenAI interactions.
• “core/”: Contains configuration, dependency management, and logging.
• “models/”: Contains data models and schemas.
• Top-level directories Tesseract-OCR and poppler-23.11.0 are used as bundled external dependencies for OCR and PDF processing.
• The project’s entry point is in “main.py”, and additional configuration is managed by a .env file.
• There are directories for logs and additional documentation.
Architectural Patterns & Technologies
• Modular Architecture: Each main function (PDF processing, AI processing, API routing) is encapsulated in its own module.
• Mention use of FastAPI as the framework handling routing and dependency injection.
• That the design is orchestrated with a pipeline pattern: from “PDF Upload” -> “PDF Processing/OCR” -> “Text Process & AI Extraction” -> “Final Structured Response”.
• External dependencies: Tesseract-OCR, Poppler, and OpenAI API.
• That configuration and logging are cross-cutting concerns managed centrally.