You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: backend/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ No need to reinvent auth, migrations, or admin panels when Django gives you all
21
21
22
22
**Processor app** - This is where the magic starts. Upload a resume, it queues a job in Redis, extracts text with pdfplumber or OCR, sends it to an LLM (OpenAI's GPT-4o-mini) to structure it properly, then generates a review of what could be improved. The structured data is what makes everything else possible.
23
23
24
-
**Storage app** - Once we have structured data, it goes two places. Neo4j stores the actual resume data as a graph (people connected to companies, skills, technologies), while Qdrant stores embedding vectors for semantic search. The graph gives us relationship queries ("who worked at Google?"), vectors give us semantic similarity ("find someone like this person").
24
+
**Storage app** - Once we have structured data, it goes two places. Neo4j stores the actual resume data as a graph (people connected to companies and skills), while Qdrant stores embedding vectors for semantic search. The graph gives us relationship queries ("who worked at Google?"), vectors give us semantic similarity ("find someone like this person").
25
25
26
26
**Search app** - This is where it all comes together. You can do semantic search (vector similarity), structured search (graph queries), or hybrid search (both combined). The results show not just who matched, but exactly which parts of their resume matched and why.
0 commit comments