Spaces:
Paused
Paused
Update README.md
#3
by grasimus - opened
README.md
CHANGED
|
@@ -11,8 +11,15 @@ pinned: false
|
|
| 11 |
---
|
| 12 |
|
| 13 |
|
|
|
|
| 14 |
|
| 15 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 16 |
|
| 17 |
To power the retrieval engine, I evaluated three open-source, 384-dimensional sentence-embedding models from Hugging Face: `all-MiniLM-L6-v2`, `BAAI/bge-small-en-v1.5`, and `intfloat/e5-small-v2`. The evaluation ran on a random sample of 2,500 questions and measured three things:
|
| 18 |
|
|
@@ -36,7 +43,7 @@ One implementation detail worth noting: `e5-small-v2` is an asymmetric retrieval
|
|
| 36 |
|
| 37 |
---
|
| 38 |
|
| 39 |
-
##
|
| 40 |
|
| 41 |
To validate that the chosen model organizes the interview domain in a meaningful way, the embedding space was analyzed with three complementary techniques: K-Means clustering with the Elbow Method, t-SNE projection, and hierarchical clustering.
|
| 42 |
|
|
@@ -71,7 +78,7 @@ The fact that this taxonomy matches how humans intuitively divide interviews —
|
|
| 71 |
|
| 72 |
---
|
| 73 |
|
| 74 |
-
##
|
| 75 |
The application utilizes a Vector-Based Retrieval strategy to recommend the most relevant interview question to the user based on their specific configuration.
|
| 76 |
|
| 77 |
**The Pipeline:**
|
|
@@ -80,3 +87,16 @@ The application utilizes a Vector-Based Retrieval strategy to recommend the most
|
|
| 80 |
3. **Query Embedding:** The input query is passed through the selected `e5-small-v2` model, converting it into a 384-dimensional query vector.
|
| 81 |
4. **Vector Similarity Search:** The system computes the **Cosine Similarity** between the user's query vector and the pre-computed question embeddings database.
|
| 82 |
5. **Retrieval:** The system identifies the vector with the highest similarity score (argmax) and retrieves the exact matching interview scenario.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 11 |
---
|
| 12 |
|
| 13 |
|
| 14 |
+
## Exploratory Data Analysis (EDA) & Dataset Details
|
| 15 |
|
| 16 |
+
Please note that the comprehensive Exploratory Data Analysis (EDA)—including data quality checks, distribution analysis, and the full dataset card—is hosted in a separate dataset repository to keep this application space clean and focused.
|
| 17 |
+
|
| 18 |
+
You can explore the complete EDA and access the raw dataset in the README at:
|
| 19 |
+
🔗 [Davichick/InterviewForge_GenDS](https://huggingface.co/datasets/Davichick/InterviewForge_GenDS)
|
| 20 |
+
|
| 21 |
+
|
| 22 |
+
## 1. Embedding Model Selection
|
| 23 |
|
| 24 |
To power the retrieval engine, I evaluated three open-source, 384-dimensional sentence-embedding models from Hugging Face: `all-MiniLM-L6-v2`, `BAAI/bge-small-en-v1.5`, and `intfloat/e5-small-v2`. The evaluation ran on a random sample of 2,500 questions and measured three things:
|
| 25 |
|
|
|
|
| 43 |
|
| 44 |
---
|
| 45 |
|
| 46 |
+
## 2. Embeddings Analysis & Clustering
|
| 47 |
|
| 48 |
To validate that the chosen model organizes the interview domain in a meaningful way, the embedding space was analyzed with three complementary techniques: K-Means clustering with the Elbow Method, t-SNE projection, and hierarchical clustering.
|
| 49 |
|
|
|
|
| 78 |
|
| 79 |
---
|
| 80 |
|
| 81 |
+
## 3. Recommendation System (How it Works)
|
| 82 |
The application utilizes a Vector-Based Retrieval strategy to recommend the most relevant interview question to the user based on their specific configuration.
|
| 83 |
|
| 84 |
**The Pipeline:**
|
|
|
|
| 87 |
3. **Query Embedding:** The input query is passed through the selected `e5-small-v2` model, converting it into a 384-dimensional query vector.
|
| 88 |
4. **Vector Similarity Search:** The system computes the **Cosine Similarity** between the user's query vector and the pre-computed question embeddings database.
|
| 89 |
5. **Retrieval:** The system identifies the vector with the highest similarity score (argmax) and retrieves the exact matching interview scenario.
|
| 90 |
+
|
| 91 |
+
|
| 92 |
+
## 4. Dual-Model Architecture: Retrieval vs. Evaluation
|
| 93 |
+
|
| 94 |
+
|
| 95 |
+
|
| 96 |
+
* **Model 1: The Retrieval Engine (`intfloat/e5-small-v2`)**
|
| 97 |
+
When the interview begins, this embedding model handles the search. It translates the user's specific configuration into a 384-dimensional vector and searches the 20,444-question database to fetch the exact, context-aware question. It does not generate new text; it retrieves the best existing scenario.
|
| 98 |
+
|
| 99 |
+
* **Model 2: The Evaluation Engine (`Qwen/Qwen2.5-1.5B-Instruct`)**
|
| 100 |
+
Once the user submits their answer to the question, a completely different Generative AI (LLM) takes over. This model acts as the "Interviewer." It analyzes the candidate's specific response against the original question and generates a personalized, structured evaluation. The output includes a numeric Grade, highlighted Pros and Cons, and a concrete Example of how to answer it better.
|
| 101 |
+
|
| 102 |
+
**Why this matters:** This separation of concerns ensures the application is highly efficient. It uses aמ embedding model for the heavy lifting of searching through thousands of records, while reserving the deeper, more computationally expensive Generative LLM exclusively for providing human-like, nuanced feedback.
|