Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Person-Job Fit #44

Closed
dmaurath opened this issue Jul 7, 2014 · 9 comments
Closed

Person-Job Fit #44

dmaurath opened this issue Jul 7, 2014 · 9 comments
Labels

Comments

@dmaurath
Copy link

dmaurath commented Jul 7, 2014

Ever since I worked for a recruitment startup, I have pushed for standardization of resumes but for this to catch on, I think job descriptions need to also be standardized. And if both are standardized, you would want to make some changes according to the theory of Person-Job fit.

In Industrial-Organizational Psychology we determine how a person fits with a job by first determining the KSAOs, or Knowledge, Skills, Abilities and Other Characteristics (e.g. personality), needed to complete all tasks of the job. Then we design tests, interviews, and other selection tools to assess applicants on their level of each KSAO. Thus, for each job description and resume, you would be able to best predict fit, if the JD and resume each had matching KSAOs.

P-J fit is only one aspect of selecting a candidate. You could also try to match an applicant to a job based on shared values with an organization (Person-Organization fit), how their skills complement their immediate working group (Person-Group fit), or how their work style and norms align with their immediate supervisor (Person-Supervisor fit).

Takeaways:

  1. Create a complementary JSON Job Description
  2. Include fields for Knowledge, Abilities and Other Characteristics in addition to Skills
  3. Include a field for values.
@thomasdavis
Copy link
Member

Hey @dmaurath, thanks for chiming in with your expertise in this area. If you don't mind I might focus on some of the other core specification before diving deep into this.

@thomasdavis
Copy link
Member

Closing for now but referenced in README as an issue to reinvestigate.

@dmaurath
Copy link
Author

dmaurath commented Aug 9, 2014

Completely understand. Its a bit of a far-fetched idea.

@kbdavis07
Copy link

I do think there should be some Universal standardize job description or title.

Example of this is in the web development field.

Searching through job posts the description and skills required for a

"Web Developer"

Can be very different from one company to another.

May be not part of the Resume-Schema directly but maybe pull in data from a Universal Source used by all world wide.

Within the Resume-Schema provide an URI to the Job Title/Description

JobTitle: http://SomeUniversalSource/WebDeveloper

This way if employer or job seeker has any question about the job description for a title is there is one source of information to go to get it.

Sort of like an Dictionary for Job Titles with Descriptions.

Just a thought :)

@aloisdg
Copy link
Contributor

aloisdg commented Oct 27, 2015

As a test, I wrote a project called JSONHire. It is a draft to create schema for hire post. It is a kind of nemesis of JSONResume. I could explain more, but a read will be better. It is short. You can find here.

@kbdavis07
Copy link

Hi @aloisdg good start on jsonhire.

I think it is a good idea which should go hand and hand with JSON resume :)

I believe if we can tie together the Resume and Hire JSON formats with a Global Universal Job Title/Position dictionary would be helpful in having universal job titles/positions from one company to another.

I have some ideas in the works :)

Starting first with a Resume Repostory at http://ResumeRepo.com

Thanking of putting features to upload json format Resumes and Hire posts.

An editor that is connected to a dictionary for drop down menu
s and search features for job titles.

An employer can select skills from a drop down or from a search.

Lets say they enter in HTML, JavaScript, Jquery for skills needed.

The editor will select for job title for the employer Front End Web Developer.

Now another employer enter in for skills Asp.Net MVC C#, the editor would select

Sever Side Web Application Developer or Asp.Net MVC Web Application Developer.

A job seeker enters in for skills HTML, JavaScript, Jquery and that is it the editor will select

Front End Web Developer.

If Job seeker enters in a different title editor will display an error requiring different skills to be entered to continue.

This way Job Title and Job Skills are correct and validated.

@aloisdg
Copy link
Contributor

aloisdg commented Oct 29, 2015

@kbdavis07 It is exactly what I would love to see and to use. If JSONHire is going to grow, I will open a organisation with the same model than JSONResume.

@villasv
Copy link

villasv commented Feb 8, 2017

I wanted to bump up this discussion. Recently I've been using the Job Posting from schema.org but it certainly isn't ready for this kind of qualitative analysis proposed by @dmaurath.

@aloisdg
Copy link
Contributor

aloisdg commented Feb 8, 2017

@villasv I will look into this schema. What do you think of JSONHire as a draft. Feel free to add any comments/improvements in this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants