Ask HN: Do you refuse to do coding challenges for software engineer interviews?
1–10 of 17 posts
Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#2Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#3Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#4A 30-60 minute skills check is nbd, especially if it's used to understand how I approach problems.
Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#5If it's something reasonable, I don't mind it at all. My GitHub profile is pretty sparse as everything I write is for work. A 30-60 minute skills check is nbd, especially if it's used to understand how I approach problems.
Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#6Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#7Of course, there are exceptions to this. I'm also explicitly excluding here employers who outsource the technical challenge to a third party like leetcode.
Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#8Re: Ask HN: Do you refuse to do coding challenges for software engineer interviews?
#9No, I lean in the opposite direction - I would be more inclined towards employment opportunities which have a reasonable coding challenge as part of the hiring process. In my experience, there is a strong correlation between how technically challenging the hiring process is and how good a place is to work as an engineer. A reasonable coding challenge is a signal that there are competent engineers within the organizat…