2 ms·
I’m a devops engineer. I sometimes write code (like interfacing with the k8s apis and gluing stuff together). Some considerations: 1. No salary = you don’t pa
by znpy 4y ago
I’m a devops engineer. I sometimes write code (like interfacing with the k8s apis and gluing stuff together).
Some considerations:
1. No salary = you don’t pay well.
If you paid well you’d be listing that first in the job posting.
2. Also the four hours assignment… when it comes to devops kind of stuff, chances are it’s impossible, or impossible to do in 4 hours.
If I have to spin up infrastructure to do your assignment, I have to pay out of pocket.
If there’s a service I haven’t used before then I must spend additional time to go though the documentation, do some trial and error (on my time, out of my pocket).
Chances are very high there could be a tool I haven’t used before, and that would mean I could just fail because I don’t know that tool (but I could learn it easily on the job, if I hadn’t a four hour limit).
So yeah the four hour assignment is completely moronic and unless the scope is cristal clear and laser focused (eg: only aws and only ec2+s3) i’d skip you too.