Might grant a new agreed upon event kind in the future (specially if there’s several job board clients), but for now a client can just start publishing a new event (if needed) and we can figure out how to interop later. That’s one of the beautiful things about nostr.

Imagine a nip or kind for each of infinite use cases. The protocol should deal with the storage and retrieval of different data/message types(like mime types, but we're already beyond that). I failed to articulate this in a convincing way early on. Maybe the protocol level could deal with applications in general, but I also am unable to conceptualize how to achieve this.