I wanted to comment as I truly believe the interview process for developer roles (particularly in London, where I operate) is getting grossly out of hand.
From multi-stage interviews to take home "weekend" tech tests, there's a lot to be reviewed.
We often push very hard for our partners to go for a 1 stage interview, technical test done during that interview, never a whiteboard coding exercise (we do allow whiteboard exercises for architecture questions when dealing with Senior/Lead Engineers).
We always ensure the test is relevant to the day to day work that will be done by the person who gets the job, not just some ridiculous algorithmic exercise if you're hiring a front end developer! And we often give the choice to the person interviewing if they want to pair or be left alone to crack on.
The industry needs to change, and it will only do that with people like yourself voicing their opinion.
I am a creative, passionate, full stack web developer. I love technology! Currently I'm really into Node & React but I am very experienced in PHP, Drupal 8, accessibility, CI/CD #WomenWhoCode
Thanks so much Val! Yes I've been looking in London and honestly I'm finding the process tiring, even as someone with plenty of experience and great references so I cannot imagine how it must be for less experienced developers now. I think that some people just see it as moaning, but the fact that it's really hurting diversity and causing people to even quit the industry means that something really needs to be done.
I feel like a good interview should test your skills but leaving you feeling positive, whatever the outcome. It's really great to hear that there are people out there like you trying to change the process. The fact that you're giving the person the choice to pair or work alone too is brilliant, pairing can be really intimidating in an interview situation!
I haven't been in hiring for awhile now (I contract freelance), but I never really focused on interview tests. Before I'd get a candidate to come in I asked them to send me to a Github repo or some code they were particularly proud of writing. I could tell a lot from reviewing that code than I could by watching them fumble through ridiculous whiteboard tests.
I felt it was much more important to find out who the person was and if they would fit into the team. Any good FE developer can learn your process or code the way your team codes. Perhaps this process only worked for the small 30 or so person businesses I was working for, but I never had a bad hire so I think that must count for something.
I love this, and, as a potential candidate I'd apply to this company only because of the interview style. Yeah, I do random stuff sometimes (that's how I got my first job)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Awesome post, Charlotte!
I wanted to comment as I truly believe the interview process for developer roles (particularly in London, where I operate) is getting grossly out of hand.
From multi-stage interviews to take home "weekend" tech tests, there's a lot to be reviewed.
We often push very hard for our partners to go for a 1 stage interview, technical test done during that interview, never a whiteboard coding exercise (we do allow whiteboard exercises for architecture questions when dealing with Senior/Lead Engineers).
We always ensure the test is relevant to the day to day work that will be done by the person who gets the job, not just some ridiculous algorithmic exercise if you're hiring a front end developer! And we often give the choice to the person interviewing if they want to pair or be left alone to crack on.
The industry needs to change, and it will only do that with people like yourself voicing their opinion.
Thanks so much Val! Yes I've been looking in London and honestly I'm finding the process tiring, even as someone with plenty of experience and great references so I cannot imagine how it must be for less experienced developers now. I think that some people just see it as moaning, but the fact that it's really hurting diversity and causing people to even quit the industry means that something really needs to be done.
I feel like a good interview should test your skills but leaving you feeling positive, whatever the outcome. It's really great to hear that there are people out there like you trying to change the process. The fact that you're giving the person the choice to pair or work alone too is brilliant, pairing can be really intimidating in an interview situation!
I haven't been in hiring for awhile now (I contract freelance), but I never really focused on interview tests. Before I'd get a candidate to come in I asked them to send me to a Github repo or some code they were particularly proud of writing. I could tell a lot from reviewing that code than I could by watching them fumble through ridiculous whiteboard tests.
I felt it was much more important to find out who the person was and if they would fit into the team. Any good FE developer can learn your process or code the way your team codes. Perhaps this process only worked for the small 30 or so person businesses I was working for, but I never had a bad hire so I think that must count for something.
I love this, and, as a potential candidate I'd apply to this company only because of the interview style. Yeah, I do random stuff sometimes (that's how I got my first job)