Am I wrong to be turned off by coding examinations in interviews?
retained text
I've been speaking to recruiters recently about roles in my area. Almost every set of interviews now has a live coding portion to it. I've got an interview next week where I've been told I will be asked to live code. When asked what sort of coding, I was told - it could be writing Terraform, Python, writing a helm chart, kubernetes manifests. It will be random on the day. I've individually done a lot of these. I've been writing Terraform for years, and I do Kubernetes manifests every single day. However, I might not touch Terraform for months whilst I work on one project. Python might be even longer. If tasked with a Terraform project, I'll look at some recent work I did, get a feel for it again, and I'm productive pretty quickly. But just throw me into an interview, and have multiple engineers ask me to live code, and I feel like I would turn to jelly. I can't remember off the top of my head how to do a module for Terraform - give me a previous one I created, I can take it as a template and start rewriting it, looking up functions if I need new things. Same for Kubernetes. I will take a deployment file and a svc I did for something in the past, copy and paste it into a new file and edit it to fit my new needs. Writing the document from scratch without documentation... I can't remember that for shit. Who does it afresh on every new service?
document fetched 2026-11-04 00:24 · canonical https://reddit.com/r/devops/comments/1xmsxbb/am_i_wrong_to_be_turned_off_by_coding