I think you need to stick more to existing standards.
Location: US is really big. It's a good idea to stick with ISO country codes but maybe use an optional state/province and zip code to make it more specific?
Date/time: the advantage of YYYY-MM-DD is that you can sort date strings alphabetically and they will be chronologically sorted as well. There already is a date/time standard, so why not use it? https://tools.ietf.org/html/rfc3339#section-5.6
Thinks like market, position, perks should all be coded instead of being strings. People will not write SaaS but 'Software as a Service', 'SaaS-startup', and all kinds of variations. They're US-English as well right now - that will make it even more difficult to make this an international standard. So you need find existing standards that codify these kind of things and refer to them, or make your own repository and spend effort in finding different spellings and coupling them.
Location: US is really big. It's a good idea to stick with ISO country codes but maybe use an optional state/province and zip code to make it more specific?
Date/time: the advantage of YYYY-MM-DD is that you can sort date strings alphabetically and they will be chronologically sorted as well. There already is a date/time standard, so why not use it? https://tools.ietf.org/html/rfc3339#section-5.6
Thinks like market, position, perks should all be coded instead of being strings. People will not write SaaS but 'Software as a Service', 'SaaS-startup', and all kinds of variations. They're US-English as well right now - that will make it even more difficult to make this an international standard. So you need find existing standards that codify these kind of things and refer to them, or make your own repository and spend effort in finding different spellings and coupling them.
You could classify businesses using NAICS (http://en.wikipedia.org/wiki/North_American_Industry_Classif...) and SOC codes to classify job titles. For instance a backend engineer has SOC code 151133 (http://www.bls.gov/soc/2010/soc151133.htm). These are still US-specific standards, but it's better than inventing your own, or none at all.
Type: full-time. Maybe make this hrs/week?
For descriptions maybe make it an associative array with ISO language codes as a key, and the description in that language as a value?