Skip to content

Commit c336438

Browse files
author
Sid Rathi
committed
update readme
1 parent 52f1777 commit c336438

File tree

2 files changed

+34
-10
lines changed

2 files changed

+34
-10
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
.idea/

README.md

Lines changed: 33 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,44 @@
11
# Build Experience Profile from Resumes
22

3-
In this project, we use text extraction and retireval for the following functions:
43

5-
1. Get useful information from a candidate’s (prospective employee) resume
6-
2. Build an experience profile connection candidate’s experience in various tools and technologies, for each of the resumes
7-
3. Rank the available set of resumes based on the skill set, using the keywords provided in the query
4+
1. What are the names and NetIDs of all your team members? Who is the captain? The captain will have more administrative duties than team members.
5+
* alokk3@illinois.edu
6+
* dkrovi2@illinois.edu
7+
* jsaxena3@illinois.edu
8+
* rathi9@illinois.edu
9+
10+
2. What is your free topic? Please give a detailed description. What is the task? Why is it important or interesting? What is your planned approach? What tools, systems or datasets are involved? What is the expected outcome? How are you going to evaluate your work?
11+
12+
* In this project, we use text extraction and retireval for the following functions:
13+
* Get useful information from a candidate’s (prospective employee) resume
14+
* Build an experience profile connection candidate’s experience in various tools and technologies, for each of the resumes
15+
* Rank the available set of resumes based on the skill set, using the keywords provided in the query
16+
17+
The current keyword based search used by many online websites might not be entirely accurate, as the coorelation between the skills and the experience is often missing.
18+
19+
For example, for a skill set of ‘Spark’, instead of just searching for the keyword ‘Spark’ in the resume, we want to know (for scoring purpose)
20+
- if the employee worked in Spark for X number of years,
21+
- did he have experience on Spark, in multiple organizations.
22+
23+
We then create a score for each profile/resume based on the skill set mentioned in the query and rank them in order of score (highest to lowest).
24+
825

9-
The current keyword based search used by many online websites might not be entirely accurate, as the coorelation between the skills and the experience is often missing.
26+
3. Which programming language do you plan to use?
1027

11-
For example, for a skill set of ‘Spark’, instead of just searching for the keyword ‘Spark’ in the resume, we want to know (for scoring purpose)
12-
- if the employee worked in Spark for X number of years,
13-
- did he have experience on Spark, in multiple organizations.
28+
* We will use the standard text retireval tools and programming APIs (MeTA, python, numpy etc) with a customized algorithm to score each resume.
1429

15-
We then create a score for each profile/resume based on the skill set mentioned in the query and rank them in order of score (highest to lowest).
30+
4. Please justify that the workload of your topic is at least 20*N hours, N being the total number of students in your team. You may list the main tasks to be completed, and the estimated time cost for each task.
1631

17-
We use the standard text retireval tools and programming APIs (MeTA, python, numpy etc) with a customized algorithm to score each resume.
32+
The following are the steps and key milestones for this project:
1833

34+
Task | Time needed | Completion date
35+
---- | ----------- |----------------
36+
Build the resume database with resumes | 4 hours | Nov 8
37+
Progress report | 2 hours | Nov 15
38+
Build the text retrieval algorithm and document indexes | 20 hours | Nov 22
39+
Build scoring engine to pick relevant resumes | 12 hours | Nov 29
40+
Build an experience profile | 8 hours | Dec 5
41+
Software code submission with documentation | 8 hours | Dec 9
1942

2043
# Contributors
2144

0 commit comments

Comments
 (0)