Advice: Don't sweat the coding questions if they exist, just do the best you can, try to explain the way you think, and realize that they don't count for 100% of the hire/no-hire decision at all of the companies that give them...
Also, I like to point potential employers to Joel Spolsky's "The Guerrilla Guide to Interviewing" https://www.joelonsoftware.com/2006/10/25/the-guerrilla-guid...
If they read it but disagree with it, I don't count it against them.
If they read it and agree with it, that's a huge positive. I might be able to overlook other flaws in their software development process and take the job...
If they don't read it, BIG RED FLAG!!! What else are they not going to listen to if/when you propose it? A job should be a two-way street with employees doing what they are told, but at the same time constantly proposing ways to improve their employers' processes! Even if employers do not accept those proposals (totally OK, they are the employer after all), they should at least have the common courtesy to READ anything reasonable, and RESPOND to those things, with the EXACT REASONS as to WHY those proposals are unacceptable!!!
If a potential employer, pre-hire, won't read a web page you send them, and won't comment on it in such a way as to provide actionable intelligence one way, or the exact reason WHY on the other... that's a BIG RED FLAG!!!
Also... for an alternative viewpoint on Mental Illness, you might wish to read "The Myth Of Mental Illness" by Dr. Thomas Szasz, M.D. https://en.wikipedia.org/wiki/The_Myth_of_Mental_Illness
"Insanity is doing the same thing over and over and expecting different results" -Albert Einstein