No, I lean in the opposite direction - I would be more inclined towards employment opportunities which have a reasonable coding challenge as part of the hiring process. In my experience, there is a strong correlation between how technically challenging the hiring process is and how good a place is to work as an engineer. A reasonable coding challenge is a signal that there are competent engineers within the organization (in order to be able to come up with and mark such challenges), and that the organization values engineering capability to some degree.
Of course, there are exceptions to this. I'm also explicitly excluding here employers who outsource the technical challenge to a third party like leetcode.
That's ridiculous! Obviously not every software engineer knows algorithms and data structures, but if you do pass a leet code question you have at least some minimum of skill.
It's shocking how many interviews I've done where the candidate can barely code anything unfortunately, so it is absolutely worthwhile.
Having done many coding interviews I can assure you there is more to it than memorizing a problem and solution. I don't see how asking someone who is applying for a software engineer job to do a miniature software engineering task is controversial!
Of course, there are exceptions to this. I'm also explicitly excluding here employers who outsource the technical challenge to a third party like leetcode.