Job Application Design
-
Hi Guys, I am designing a Job Engine website for my developers. I have seen a lot of Job engine website in the net and ofcourse i know how the job engine works. But i have a point which worth to be discussed. ofcouse there will be database for jobs adverts and job seekers profiles/cvs. where job seekers will search for jobs and apply. Ok, The point that i would like to discuss here is: when the job seeker apply for a job. In real-life scenario, when a job seeker (John Smith) wants to apply for a job. he will send his cv to the employer. And again if the employer after some time advertise for another job. and the Job Seeker (John Smith) submitted his CV (but this time his profile/CV got update from last time). The Employer, in this case will have two cvs for (John Smith). Old one and Updated one. Now, comming back to our system design. the Job Seeker (John Smith) registered in the website and he created his profile and build his cv. of course he can update his profile/cv any time. If we follow the above real-life scenario, by making the system copy the entire job seeker profile againest the job advert he is appying. we may end up with the following: 1. Put more weight on the database by creating multiple job seekers profiles. 2. The Employer may get confused by seeing an old job seeker profile. and when he search about the same job seeker (John Smith) in the job seekers database, he will see a different (updated) profile for the same job seeker. Ok, the second scenario (which i am plannig to do) is: keeping a single profile for each job seeker and when a job seeker apply for a job.. we just link the job seeker profile with the job advert (no profile copy). but this way we will face the following: 1. Whenever a job seeker updated his profile it will get reflected in all the job advert responses. I mean, when an employer view the responses againest his job advert. he can see for exmple, application date, and job seeker name. and when he click on the job seeker name it just reading the job seeker profile from the database (the current). even if the job seeker applied before a year and before he updated his profile. what i want from you guys, just your feed back and thoughts. awaiting your replies.
Hussain Mohammed Saleh Attiya ISP Technical Manager Atyaf Telcom - Bahrain
-
Hi Guys, I am designing a Job Engine website for my developers. I have seen a lot of Job engine website in the net and ofcourse i know how the job engine works. But i have a point which worth to be discussed. ofcouse there will be database for jobs adverts and job seekers profiles/cvs. where job seekers will search for jobs and apply. Ok, The point that i would like to discuss here is: when the job seeker apply for a job. In real-life scenario, when a job seeker (John Smith) wants to apply for a job. he will send his cv to the employer. And again if the employer after some time advertise for another job. and the Job Seeker (John Smith) submitted his CV (but this time his profile/CV got update from last time). The Employer, in this case will have two cvs for (John Smith). Old one and Updated one. Now, comming back to our system design. the Job Seeker (John Smith) registered in the website and he created his profile and build his cv. of course he can update his profile/cv any time. If we follow the above real-life scenario, by making the system copy the entire job seeker profile againest the job advert he is appying. we may end up with the following: 1. Put more weight on the database by creating multiple job seekers profiles. 2. The Employer may get confused by seeing an old job seeker profile. and when he search about the same job seeker (John Smith) in the job seekers database, he will see a different (updated) profile for the same job seeker. Ok, the second scenario (which i am plannig to do) is: keeping a single profile for each job seeker and when a job seeker apply for a job.. we just link the job seeker profile with the job advert (no profile copy). but this way we will face the following: 1. Whenever a job seeker updated his profile it will get reflected in all the job advert responses. I mean, when an employer view the responses againest his job advert. he can see for exmple, application date, and job seeker name. and when he click on the job seeker name it just reading the job seeker profile from the database (the current). even if the job seeker applied before a year and before he updated his profile. what i want from you guys, just your feed back and thoughts. awaiting your replies.
Hussain Mohammed Saleh Attiya ISP Technical Manager Atyaf Telcom - Bahrain
Hi, Unfortunatly, no body gives his thoughts or feedback. So, i am going to reply myself. first of all, when a job seeker builds his/her CV he is always upgrading it during his career to make it more richer and professional. noboddy will, downgrade his CV. Hince, in any case when the employer view the job seeker cv (the current one) which he submitted a year back and same cv he submitted now.. will not make any different for the employer.. the CV is always uptodate. so, the system should be designed using the second way. which is keeping a single profile for the job seeker
Hussain Mohammed Saleh Attiya ISP Technical Manager Atyaf Telcom - Bahrain
-
Hi Guys, I am designing a Job Engine website for my developers. I have seen a lot of Job engine website in the net and ofcourse i know how the job engine works. But i have a point which worth to be discussed. ofcouse there will be database for jobs adverts and job seekers profiles/cvs. where job seekers will search for jobs and apply. Ok, The point that i would like to discuss here is: when the job seeker apply for a job. In real-life scenario, when a job seeker (John Smith) wants to apply for a job. he will send his cv to the employer. And again if the employer after some time advertise for another job. and the Job Seeker (John Smith) submitted his CV (but this time his profile/CV got update from last time). The Employer, in this case will have two cvs for (John Smith). Old one and Updated one. Now, comming back to our system design. the Job Seeker (John Smith) registered in the website and he created his profile and build his cv. of course he can update his profile/cv any time. If we follow the above real-life scenario, by making the system copy the entire job seeker profile againest the job advert he is appying. we may end up with the following: 1. Put more weight on the database by creating multiple job seekers profiles. 2. The Employer may get confused by seeing an old job seeker profile. and when he search about the same job seeker (John Smith) in the job seekers database, he will see a different (updated) profile for the same job seeker. Ok, the second scenario (which i am plannig to do) is: keeping a single profile for each job seeker and when a job seeker apply for a job.. we just link the job seeker profile with the job advert (no profile copy). but this way we will face the following: 1. Whenever a job seeker updated his profile it will get reflected in all the job advert responses. I mean, when an employer view the responses againest his job advert. he can see for exmple, application date, and job seeker name. and when he click on the job seeker name it just reading the job seeker profile from the database (the current). even if the job seeker applied before a year and before he updated his profile. what i want from you guys, just your feed back and thoughts. awaiting your replies.
Hussain Mohammed Saleh Attiya ISP Technical Manager Atyaf Telcom - Bahrain
You are obviously a child of today, no patience at all. I think you have it wrong, try this scenario. I am happy applying for 3-4 different types of contract, developer/architect, winforms developer, database, web (under duress) and shortly silverlight. Add in VB and/or C# and I may want 5+ CVs Now I want a different CV emphasising different skill sets based on the type of contract I want to apply for. Also I have decades of development experience and can easily fill 10 pages simply by briefly listing the projects I have worked on. Most HR teams will choke on anything over 2 pages but some will want the lot so I offer a summary CV and a full project listing. So in this instance I would retain all CVs, categorise them and allow the developer to indicate which CV to put forward for each contract. I would also have the functionality to replace a CV of x type with a new one.
Never underestimate the power of human stupidity RAH
-
You are obviously a child of today, no patience at all. I think you have it wrong, try this scenario. I am happy applying for 3-4 different types of contract, developer/architect, winforms developer, database, web (under duress) and shortly silverlight. Add in VB and/or C# and I may want 5+ CVs Now I want a different CV emphasising different skill sets based on the type of contract I want to apply for. Also I have decades of development experience and can easily fill 10 pages simply by briefly listing the projects I have worked on. Most HR teams will choke on anything over 2 pages but some will want the lot so I offer a summary CV and a full project listing. So in this instance I would retain all CVs, categorise them and allow the developer to indicate which CV to put forward for each contract. I would also have the functionality to replace a CV of x type with a new one.
Never underestimate the power of human stupidity RAH
Thanks Mycroft Holmes, about having funtionality of creating professional CV containing projects, summary etc. it is already in the design plan.. but i did not mentioned. we have also, customized a recruitment website for our client using a puchased source code from the following UK company http://www.strategies.co.uk/products/job-board-software.asp[^] that was classic asp we bought before 3 years. i dont know if they have the .Net version or not. Anyway, those, guys also allowing job seeker to replace a CV when he is attempt to apply for a job. this will do the functionality of the differnet set of skills you mentioned. in our application, we are trying to collect all the good features from the different jobs applications and also, we have to look the real-life HR scenarios. thanks for your reply
Hussain Mohammed Saleh Attiya ISP Technical Manager Atyaf Telcom - Bahrain
-
Thanks Mycroft Holmes, about having funtionality of creating professional CV containing projects, summary etc. it is already in the design plan.. but i did not mentioned. we have also, customized a recruitment website for our client using a puchased source code from the following UK company http://www.strategies.co.uk/products/job-board-software.asp[^] that was classic asp we bought before 3 years. i dont know if they have the .Net version or not. Anyway, those, guys also allowing job seeker to replace a CV when he is attempt to apply for a job. this will do the functionality of the differnet set of skills you mentioned. in our application, we are trying to collect all the good features from the different jobs applications and also, we have to look the real-life HR scenarios. thanks for your reply
Hussain Mohammed Saleh Attiya ISP Technical Manager Atyaf Telcom - Bahrain
Well doing what was suggested IS real life :) It is always standard procedure (talk to a few people that help you locate jobs) to tailor your resume to a specific target, so many people have many multiple versions handy that highlight specific areas for specific reasons. A system that allows profiles to be built should account for that. While it sounds like you are trying to consolidate ALL a persons information into one picture of a person that covers all their interests and experience, you may find that muddies the waters a bit when trying to do to searches and weighted matching.
-
Well doing what was suggested IS real life :) It is always standard procedure (talk to a few people that help you locate jobs) to tailor your resume to a specific target, so many people have many multiple versions handy that highlight specific areas for specific reasons. A system that allows profiles to be built should account for that. While it sounds like you are trying to consolidate ALL a persons information into one picture of a person that covers all their interests and experience, you may find that muddies the waters a bit when trying to do to searches and weighted matching.
Hi, The system is already designed and almost going to be finish... from our experience with many clients when we set with the HR team and take all thier requirements. Yes, it is a standard procedures. Job Seeker Register -> update his profile (his personal details, contacts and address) --> build his cv (using cv builder) or upload a document (CV). when he attempt to apply he either apply with his current CV or upload new one. this standard functionality is already taken into the account of the system. What i wanted is just to collect thouhgts and feedback. But i raise just one point which is: when a job seeker update his CV using CV builder tool. Technically, he his editing the current record not keeping it as an old version CV and building a New CV from scratch (Adding new Record.). And whenever he want to apply with different cv he can do: 1. upload new cv when he attempt to apply for job (this is the easy way) 2. using cv builder to build a new cv (this will overwrite the existing one) then apply with his curent updated cv. that was my point bcz some of our client asked for copying the entire CV records againest the job and keep the orginal one unchanged. We are trying to come up with a general job application that fits most requirements. the point i mentioned. i felt it is not right.
Hussain Mohammed Saleh Attiya ISP Technical Manager Atyaf Telcom - Bahrain