Yep, I have looked over your sample test. It was in both Go and Ruby. I finished the Go section and then decided against bothering with the rest.
The "instructions" for the sample test were either purposely obfuscated or just badly written and it reflected poorly on the merit of your documentation methods more so than anything else.
To be quite honest, you are nothing more than an arm of IBM at this point and I would never work for a company that so carelessly devalues developer time and then comes into a forum arguing with random developers that they are right and everyone who disagrees is wrong.
In all seriousness though, what do you guys even do? Set up etcd for a cluster? Or PostgreSQL? etc.? Do you have any idea how simple that is these days?
For all interested: the work sample was focused around alerting DevOps via third-party services like Slack and PagerDuty. In other words: I imagine the developer positions here are simultaneously "on-call" operations positions as well! haha!
Good luck, Compose Team. You're going to need it! :)
The "instructions" for the sample test were either purposely obfuscated or just badly written and it reflected poorly on the merit of your documentation methods more so than anything else.
To be quite honest, you are nothing more than an arm of IBM at this point and I would never work for a company that so carelessly devalues developer time and then comes into a forum arguing with random developers that they are right and everyone who disagrees is wrong.
In all seriousness though, what do you guys even do? Set up etcd for a cluster? Or PostgreSQL? etc.? Do you have any idea how simple that is these days?
For all interested: the work sample was focused around alerting DevOps via third-party services like Slack and PagerDuty. In other words: I imagine the developer positions here are simultaneously "on-call" operations positions as well! haha!
Good luck, Compose Team. You're going to need it! :)