Create README.md
Browse files
README.md
ADDED
|
@@ -0,0 +1,59 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
This dataset is a custom-built text classification dataset for detecting fraud risk in internship and entry-level job postings. This dataset is created for an embeddings-based classifier that helps students evaluate whether internship and entry-level job postings may be legitimate, suspicious, or fraudulent.
|
| 2 |
+
|
| 3 |
+
|
| 4 |
+
## Dataset Summary
|
| 5 |
+
|
| 6 |
+
The dataset contains job posting texts labeled into three risk categories:
|
| 7 |
+
|
| 8 |
+
- `legitimate`: postings that look like normal internship or entry-level job advertisements
|
| 9 |
+
- `suspicious`: postings with warning signs such as vague requirements, missing company information, remote-only work, unclear application process, or unrealistic opportunity language
|
| 10 |
+
- `fraudulent`: postings originally labeled as fraudulent in the source dataset
|
| 11 |
+
|
| 12 |
+
The final dataset contains 900 examples: 300 legitimate, 300 suspicious, and 300 fraudulent job postings.
|
| 13 |
+
|
| 14 |
+
## Source Data
|
| 15 |
+
|
| 16 |
+
This dataset was adopted from the Kaggle public dataset: Real / Fake Job Posting Prediction dataset, which is based on the Employment Scam Aegean Dataset (EMSCAD).
|
| 17 |
+
|
| 18 |
+
Sources:
|
| 19 |
+
|
| 20 |
+
- Kaggle: `shivamb/real-or-fake-fake-jobposting-prediction`
|
| 21 |
+
- Original dataset: Employment Scam Aegean Dataset (EMSCAD)
|
| 22 |
+
|
| 23 |
+
## Custom Processing
|
| 24 |
+
|
| 25 |
+
The original dataset contains job advertisements with a binary `fraudulent` label. I transformed it into a custom internship-focused dataset by:
|
| 26 |
+
|
| 27 |
+
1. Combining job fields such as title, location, company profile, description, requirements, benefits, employment type, education, industry, and function into one text field.
|
| 28 |
+
2. Filtering toward internship, student, trainee, junior, assistant, graduate, and entry-level roles.
|
| 29 |
+
3. Preserving fraudulent examples so the model learns scam-related language.
|
| 30 |
+
4. Converting the original binary label into three labels: `legitimate`, `suspicious`, and `fraudulent`.
|
| 31 |
+
5. Adding red-flag annotations such as missing company profile, missing requirements, no company logo, no screening questions, remote/telecommuting, money-transfer language, upfront-fee language, and unrealistic easy-money language.
|
| 32 |
+
6. Creating transparent rule-based suspicious variants from legitimate examples to balance the borderline-risk class.
|
| 33 |
+
7. Balancing the final dataset to 300 examples per class.
|
| 34 |
+
|
| 35 |
+
## Columns
|
| 36 |
+
|
| 37 |
+
The dataset includes:
|
| 38 |
+
|
| 39 |
+
- `id`: row identifier
|
| 40 |
+
- `source_job_id`: original job ID or generated suspicious variant ID
|
| 41 |
+
- `title`: job title
|
| 42 |
+
- `location`: job location
|
| 43 |
+
- `text`: combined job posting text used for model training
|
| 44 |
+
- `label`: target class (`legitimate`, `suspicious`, `fraudulent`)
|
| 45 |
+
- `risk_level`: low, medium, or high
|
| 46 |
+
- `red_flags`: semicolon-separated warning indicators
|
| 47 |
+
- `source_dataset`: source dataset name
|
| 48 |
+
- `source_type`: processed public dataset or rule-augmented suspicious variant
|
| 49 |
+
- `original_fraudulent`: original binary fraud label from EMSCAD
|
| 50 |
+
- `internship_related`: whether the posting matched internship/early-career terms
|
| 51 |
+
|
| 52 |
+
|
| 53 |
+
## Limitations
|
| 54 |
+
|
| 55 |
+
This dataset should not be used as a final authority for deciding whether a job is safe. The `suspicious` class is partly rule-based and may not capture all real-world borderline cases. The dataset is useful for experimentation, model comparison, and demo development, but users should still manually verify company identity, application links, contact methods, and payment-related requests.
|
| 56 |
+
|
| 57 |
+
## References:
|
| 58 |
+
|
| 59 |
+
Vidros, S., Kolias, C., Kambourakis, G., & Akoglu, L. (2017). Automatic detection of online recruitment frauds: Characteristics, methods, and a public dataset. *Future Internet, 9*(1), 6.
|