I wasn't offered the job, but I regret nothing.
I've done plenty of code tests in the past, these days it would take A LOT to motivate me.
Usually I just say thanks, but no thanks if they insist on testing me.
I know I probably would, so I'm curious.
Then again, not completely sure what the GP means about "screening stage"; if a take-home assignment is given before any kind of substantive interaction between the company and me, that'd be a definite red flag. I'm not going to spend 45 minutes doing your resume screening for you.
The thing is that any kind of test is going to signal a lack of trust, and that's not a great way to start.
* Live coding during an interview sucks. I'm not convinced interviewers actually learn all that much useful during those, and I know a lot of people who perform well on the job but choke up during interviews when there's a live coding component.
* It's not like there isn't precedent for this sort of thing outside tech. For example, marketing/sales positions will often require the interviewee to prep a mock presentation specifically for the interview. (That is, not something generic they can use for multiple interviews.)
I get that people have commitments outside of work, and that the ideal situation is that you're interviewing for a job while you already have one (so interviewing work is going to be on top of all your existing responsibilities). But at the same time, take-home assignments in tech are becoming more common, and refusing to do them is going to limit your options. And I don't think the usual "well I probably wouldn't enjoy working at a company that does $THING during their interviews" really applies here.