The project will involve building an IT HR “job site” tool. Both candidates and companies will use it. Candidates enter descriptive data regarding skills and interests, post a resume etc. Companies enter descriptive data and post jobs including necessary skills. There are 3 types of “skills” each user type must describe. Candidates – skills possessed and expertise. Company – skills required for job posted. These are:
Technical
Business
Culture or attitudinal (To some this is most important. You can be trained on the other 2 types.)
Check out some job sites. Get info on what data is collected from candidates and what is listed in job postings. You can borrow from these to make workable skills lists. You will have to create some kind of matching algorithm to take the skills possessed by candidates and match them to job postings. The result of running this algorithm is a rank ordered list of matches from best to worst. Companies see a list of candidates matches. Candidates see a list of job matches.
The algorithm used is something that you choose. You can use k nearest neighbors, distance matching, clustering, neural nets, or whatever you find that you can implement. If you have an algorithm that lists matches it will generally have some scoring method, so displaying scores is important in the output lists.
If you check out the Octalysis paper, you will see how gamification can be used to make the tool, at least more interesting. Data Visualization techniques are important here.
A company probably wants analytics capability. Info showing candidate skills range and incidence, jobs watched, etc. I mentioned more last night.
The following are requirements which I mentioned last night. This is a more formal list. Your team should add whatever you need to these lists.
Build some use cases to inform this whole process.
FUNCTIONAL
User
• New users should be easily added
• User Login/Logout
• User Registration/Edit profile
• User account deletion
• Opt-In to responsibilities/agreements for use of application
• Login password and authentication
• Restricted view based on privileges
Candidate – Looks for jobs/enters a personal profile
Candidate Login/Logout
Candidate Registration/Edit profile Tech skills, Business skills, Culture/work attitudes
Candidate account deactivation – but data remains
Browse companies
Browse jobs in database Filter by demographics, tech skills, attitudes, etc.
Create/edit/delete job searches Filter by demographics, tech skills, attidtudes, etc.
List reference names/contact info
Upload resume document
GET rank ordered sort (tech skills & attitude) of best job fits (ALGORITHM); Ability to contact them
Company – Looks for candidates/posts jobs (This is the main focus)
Company Login/Logout
Company Registration/Edit profile
Company account deactivation
Post/edit/close jobs List for each: Tech skills, Business skills, Culture/work attitudes
Browse candidates in database Filter by demographics, tech skills, attidtudes, etc.
Create/edit/delete job postings
Create/edit/delete candidate searches Filter by demographics, tech skills, attitudes, etc.
Review outstanding and closed searches
GET rank ordered sort (tech skills, biz skills & attitude) of best candidates for a job (ALGORITHM); Ability to contact them
Administrator/superuser
Login/manage/maintain site
Access databases
Edit/deactivate/activate accounts
For both Candidate and Company
OptIn to responsibilities/agreements
Login password and authentication
Restricted view based on privileges
Browsing should allow inclusion of culture fit as a filter
Ability to create/edit/save/delete search parameters
Ability to save selected search outcomes (candidates OR companies) – dependent on user role
Ability to contact search list users – at least email and phone contact info. How about chat?
NON FUNCTIONAL
Usability/Interface
White space, clean design
No extraneous features
Easy to Learn, Use, Remember
Data display
Charts, graphs, visualization. Can you animate any of the data displays?
Reliability
24X7
Performance
Initially 100s of candidates and companies
Scale up to handle larger numbers as time goes by
Quick response time
Implementation
Any commonly used application development languages, OS, environments, development platforms
Web server based
Scalable relational database commonly used in web based applications
Delivery
Web based. No installation
Supportability
Basic web/DB/development skills in web based environment
Web Browser support
Minimum IE v7, Mozilla Firefox, Google Chrome
Device support
PC browser, mobile device a plus
Legal
Terms of service
The project will involve building an IT HR “job site” tool. Both candidates and companies will use it. Candidates enter descriptive data regarding skills and interests, post a resume etc. Companies enter descriptive data and post jobs including necessary skills. There are 3 types of “skills” each user type must describe. Candidates – skills possessed and expertise. Company – skills required for job posted. These are: Technical Business Culture or attitudinal (To some this is most important. You can be trained on the other 2 types.)
Check out some job sites. Get info on what data is collected from candidates and what is listed in job postings. You can borrow from these to make workable skills lists. You will have to create some kind of matching algorithm to take the skills possessed by candidates and match them to job postings. The result of running this algorithm is a rank ordered list of matches from best to worst. Companies see a list of candidates matches. Candidates see a list of job matches.
The algorithm used is something that you choose. You can use k nearest neighbors, distance matching, clustering, neural nets, or whatever you find that you can implement. If you have an algorithm that lists matches it will generally have some scoring method, so displaying scores is important in the output lists.
If you check out the Octalysis paper, you will see how gamification can be used to make the tool, at least more interesting. Data Visualization techniques are important here. A company probably wants analytics capability. Info showing candidate skills range and incidence, jobs watched, etc. I mentioned more last night.
The following are requirements which I mentioned last night. This is a more formal list. Your team should add whatever you need to these lists.
Build some use cases to inform this whole process.
FUNCTIONAL User • New users should be easily added • User Login/Logout • User Registration/Edit profile • User account deletion • Opt-In to responsibilities/agreements for use of application • Login password and authentication • Restricted view based on privileges
Administrator • Login/manage/maintain site • Access databases • Analyse usage • Analytic tools
TWO specific user types
Candidate – Looks for jobs/enters a personal profile Candidate Login/Logout Candidate Registration/Edit profile Tech skills, Business skills, Culture/work attitudes Candidate account deactivation – but data remains Browse companies Browse jobs in database Filter by demographics, tech skills, attitudes, etc. Create/edit/delete job searches Filter by demographics, tech skills, attidtudes, etc. List reference names/contact info Upload resume document GET rank ordered sort (tech skills & attitude) of best job fits (ALGORITHM); Ability to contact them
Company – Looks for candidates/posts jobs (This is the main focus) Company Login/Logout Company Registration/Edit profile Company account deactivation Post/edit/close jobs List for each: Tech skills, Business skills, Culture/work attitudes Browse candidates in database Filter by demographics, tech skills, attidtudes, etc. Create/edit/delete job postings Create/edit/delete candidate searches Filter by demographics, tech skills, attitudes, etc. Review outstanding and closed searches GET rank ordered sort (tech skills, biz skills & attitude) of best candidates for a job (ALGORITHM); Ability to contact them
Administrator/superuser Login/manage/maintain site Access databases Edit/deactivate/activate accounts
For both Candidate and Company OptIn to responsibilities/agreements Login password and authentication Restricted view based on privileges Browsing should allow inclusion of culture fit as a filter Ability to create/edit/save/delete search parameters Ability to save selected search outcomes (candidates OR companies) – dependent on user role Ability to contact search list users – at least email and phone contact info. How about chat?
NON FUNCTIONAL Usability/Interface White space, clean design No extraneous features Easy to Learn, Use, Remember Data display Charts, graphs, visualization. Can you animate any of the data displays? Reliability 24X7 Performance Initially 100s of candidates and companies Scale up to handle larger numbers as time goes by Quick response time Implementation Any commonly used application development languages, OS, environments, development platforms Web server based Scalable relational database commonly used in web based applications Delivery Web based. No installation Supportability Basic web/DB/development skills in web based environment Web Browser support Minimum IE v7, Mozilla Firefox, Google Chrome Device support PC browser, mobile device a plus Legal Terms of service