Once I was a senior engineer, every single employment contract specifically had clauses preventing me from contributing to open source projects (except with specific, explicit permission from your manager).
Once I was a senior engineer, every single employment contract specifically had clauses preventing me from contributing to open source projects (except with specific, explicit permission from your manager).
I've found the former to be reasonably common (and I don't object to that).
I've not encountered the latter at all, but then I also always make sure to negotiate away all the clauses that give my employer any claim over work I do on my own time with my own resources, or the ability to prohibit me from engaging in development on my own.
Regardless, I suspect that most senior devs have quite a lot of negotiating power.
The terms of employment are the opening offer of a contract negotiation. The worst thing making a counteroffer will get you is "no", not "we're withdrawing the employment offer".
As my old business partner taught me, if you don't ask then the answer is automatically "no".
Yes, they'd rather lose me as a candidate than offer a one-off contract change. A surprising number of places are like this - the perceived cost of maintaining a unique contract over the years is greater than the value provided by any possible engineer.