Submitted cv myself (not a recruiter for this one as genuinely interested), received coding challenge somewhat out of the blue. Was a little surprised not to have a chat first or at least be warned in the jd that the first action would be the code challenge. Challenge was good though - straightforward if you know what you're doing and designed to be an intro to graphql which is something I thought was particularly clever. So the challenge never really felt like a waste of time. Unfortunately the lack of notice and family commitments meant my code challenge didn't get done till over a week after it was sent - would've been nice to have some warning but I could have communicated better myself. Anyway I did the code challenge got a very positive call back 'excited to meet me' etc, set up the interview but they obviously had someone further along the candidate trail as they cancelled the interview having filled the role. Was ok with this tbh. Needs must. The process wasn't perfect but was definitely better than most. I asked for feedback on the code exercise which I always think should be provided as it's a time for time exchange, but I was a little narked to get sent the flake8 and isort errors list rather than anything I could really learn from. Yes I should have linted, but if that was really an issue you shouldn't have offered an interview. If you really appreciated the time I put in as you claimed to, five minutes feedback on the django and graphql would not kill you. 7 out of 10.