3 ms·
It looks like you're automating coding interviews. Not technical interviews. I conduct technical interviews routinely and very rarely do I touch on anything co
by whoknew1122 5y ago
It looks like you're automating coding interviews. Not technical interviews.
I conduct technical interviews routinely and very rarely do I touch on anything coding-related. That's because I'm in security, compliance, and identity.
I'd strong suggest changing changing 'technical interview', because it gave me a completely incorrect idea of your product.
Coding interviews are technical. But not all technical interviews are coding.
- geekbird 5y agoSeriously. I'm not an actual software developer, I do systems admin and DevOps config whacking. If I have to bring up an IDE to write something I'm waaaaay out of my wheelhouse. I don't touch JS, React, Java or any of that stuff. So this "technical" interview would tell people absolutely nothing about the skills needed fort my job. This is a software engineering test only, and very specific stacks at that. It would be a waste of a person's time unless that was the exact stack they used in the past, or was demanded by the job.
- Melatonic 5y agoThat is still very technical work however - and I bet you are decent at scripting in a language or two. Still plenty to test with that (theoretically).
- dang 5y agoOk, we've s/technical/coding/'d the title above.
- garyjlin 5y agoThis is a really good point, thanks for bringing it up, @dang has already helped us update the HN post title, and we've made that copy change on our website as well! From now on, our messaging will be "coding interviews", not "technical interviews". That is, until we start supporting all the other technical specialties ;)