Open DandyLyons opened 3 months ago
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
.
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.
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:
salary
tocompensation
as there are many types of compensation at different jobs, including hourly wages, commission, and even stock options.compensation
should be an object, not just a string so that it can hold other valuable metadata, including thetype
of compensation.other
compensationtype
.