Many companies butcher their interview processes, so it's not surprising to hear this story. That said, OP's refusal of code challenges all together seems every

Many companies butcher their interview processes, so it's not surprising to hear this story. That said, OP's refusal of code challenges all together seems every bit as silly as being asked to jump through the hoops described. If we were to take a moment to think about the purpose of interviews at a high level: Initial Interviews (Phone/HR/etc) - Determine mutual interest - Estimate likelihood of match - Check for red flags Follow-up Interviews (With team/Code Challenges/etc) - Confirm initial impressions - Evaluate finer points of fit (skills, etc) - Determine final interest Each of the interview goals above apply to both the interviewer and interviewee. Failures happen when either side tries to monkey with this formula too much. If your job is to write code and be an engineer, it's not outlandish to think that you'll be asked to write code as part of your evaluation for a new position. It's also not too much to expect that as an interviewee, you should be properly sold on the job by the interviewer before being asked to invest time to prove your skills. (Both sides should estimate high likelihood of match before confirming impressions) If the company's preference is to hire full-stack engineers into front-end jobs, fine — more power to them. But those expectations should be included way up front in the process, so candidates like OP can mark a "red flag" and opt out of additional interviews. TL;DR: Properly setting expectations in the interview process is ultra-important, but rarely practiced. Note: I'm the founder of Mighty Spring (https://www.mightyspring.com https://www.mightyspring.com), an anonymous, passive job discovery site. Part of our service is to help our clients (companies) hire more efficiently by coaching them up on interview process improvements like this. We're in private beta now, but send out new candidate invites regularly.