How about adding an @EmploymentEvent subtype of @BusinessEvent, and then just use @Person.performerIn (as "participant")?

Then you can use @Event.organizer for the employer and all their info, plus it then automatically gives you all the other stuff you'll want like @Event.startDate, @Event.endDate, @Event.location, @Event.subEvent, etc.

This would also work better for your current employer, enhancing the limited @Person.jobTitle @Person.worksFor @Person.workLocation, without having to add a heap of work related stuff to @Person.

This is one of the use cases for Role. It would look something like:

<script type="application/ld+json">
{
  "@context": "http://schema.org",
  "@type": "Person",
  "name": "Jane Doe",
  "worksFor": {
    "@type": "Role",
    "worksFor": {
      "@type": "Organization",
      "name": "ACME Products"
    },
    "startDate": "2018",
    "endDate": "2019",
    "roleName": "Q&A Specialist"
  }
}
</script>

Wow, that's what I get for just reading the Person schema.

http://blog.schema.org/2014/06/introducing-role.html

I had no idea this facility existed, thanks!

There's even https://schema.org/EmployeeRole :-)

I see worksFor is already there but it strikes me as less useful than something like employedBy, which more closely matches alumniOf and connotes an employee/employer relationship.

Perhaps this discussion could be merged with #1698