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

Feedback for the job schema #487

Open
DandyLyons opened this issue Aug 3, 2024 · 2 comments
Open

Feedback for the job schema #487

DandyLyons opened this issue Aug 3, 2024 · 2 comments

Comments

@DandyLyons
Copy link
Contributor

I'd like to open this issue as a place to share and discuss feedback regarding the draft schema for job descriptions. First of all, thank you for creating this. I think it has the potential to be a big help for many people! Here's my feedback:

  • Compensation:
    • I propose renaming salary to compensation as there are many types of compensation at different jobs, including hourly wages, commission, and even stock options.
      • And compensation should be an object, not just a string so that it can hold other valuable metadata, including the type of compensation.
      • No doubt this will be difficult as there will be many non-standard forms of compensation, but I think we should be able to add the most common use cases and leave the very rare compensation types to a plugin or perhaps a other compensation type.
    • In the current job market there are many jobs that offer a combination of compensation types (i.e. multiple simultaneous compensation types for the same job). This is particularly common with jobs that offer a salary AND stock options.
  • Add expiry date to job listing
@DandyLyons
Copy link
Contributor Author

Also, I'm curious what is the intended interaction between job-schema.json and schema.json (the resume schema). I didn't see any mention of the job schema in the roadmap.

Many, including me, feel that a person shouldn't have just one resume. Rather the resume should be tailored specifically to the job that you are applying for. This strategy ensures that you are highlighting the details that are most relevant to the hiring manager.

So I think it could be advantageous to provide the ability to somehow link a resume to a job (the job that this version of the resume is applying to). Unfortunately, I don't have a concrete suggestion on this topic, but I can say that I find myself wanting to keep track of which resume is intended to be used for which job application. I don't see an easy way to do this in the current resume schema. Perhaps it would be helpful if a description property were added to meta on the schema.json.

@thomasdavis
Copy link
Member

Hey @DandyLyons great feedback, I got the flu at the moment, but want to get the job schema to a better place, should be on the weekend.

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

No branches or pull requests

2 participants