Yup I agree you need to cut people a lot of slack in interviews. Don't use the same rigor you'd expect from production code. Definitely as an interviewer you

Yup I agree you need to cut people a lot of slack in interviews. Don't use the same rigor you'd expect from production code. Definitely as an interviewer you shouldn't care about syntax or remembering proper libraries. Even better, give hints about libraries, and maybe be proactive about saying you don't care about syntax. The coding under pressure line is bullshit, code under pressure ends up being bad code that makes things worse. Rollback under pressure sure. Look at monitoring graphs under pressure. Write new code? Helllll no. A lot of interviewers have unrealistic expectations though, it sucks.