Position does not allow for array

[johnvilsack]

The current schema locks "position" into an expected string. While uncommon, there are many instances in which a person may have fulfilled multiple roles at the same organization concurrently as opposed to chronologically.

For example, I fulfilled the roles of CTO, CIO, and CISO at the same time.

[virtadpt]

Same. Last job I had I was in the roster for three separate positions (engineer, security practitioner, CISO), and before that (system administrator, RF researcher, RF comms consultant).

[SethFalco]

Just adding notes for when another maintainer can comment on this. 🤔

I don't know how things work globally, but normally, individuals only have 1 job title, unless they actually have multiple jobs/contracts, which isn't often under the same work entry.

Having responsibilities for more than 1 role is not the same as a having more than 1 job title, which, is what position is referring too.

For example, a CTO, who is also the Principle Software Engineer, and is on rotation for ticket/customer support, still only has 1 position. They just also have other responsibilities which could be noted in summary or highlights.

Allowing multiple job titles could be nice, but if it's not considered practical or standard, it'd be better to adapt that scenario to fit the existing schema.

[thomasdavis]

You can just create multiple work items, with your new role, summaries and highlights.

To keep the schema simple, I think the above is a better strategy then a more complicated nested roles array.