Contract Spy
Remote (United Kingdom)
Overview A model will hand you a pipeline and an infrastructure change that apply cleanly and quietly leave a security group open to the world, a state file that will corrupt on the next run, and a rollback path that does not exist. In production those mistakes page someone at 3am. Reasoning about the whole system is the job. As a DevOps Engineer you'll evaluate how models handle CI/CD, infrastructure-as-code, and cloud operations, expose where their automation breaks, and write the answers a strong platform engineer would trust. What you’ll actually do
Probe infrastructure reasoning across CI/CD, infrastructure-as-code, containers, and cloud config, and see where the model's automation falls apart.
Find the failures that matter : insecure defaults, broken state, missing rollbacks, and changes that pass CI and break prod.
Write the correct approach when the model falls short, with failure modes and recovery made explicit.
Roles this fits Common...