Python isnt my first language - I dip in and out of it when the task in hand requires it so it was tough. It was a great challenge though and I loved every minute of it. It was a cleverly written challenge with lots of facets. I treated the 48 hours as 2 workings days (we all need a work-life-balance right). My time had run out but I had produced a script that worked, had options for operations to run in verbose mode and I had also created documentation that described how to run the script, described the features and reasoning behind choices as well as describing future enhancements. Having had an operation background (where an SREs operational experience adds most value), I wrote mine with lots of checks and stubs for extending and had created a scalable and reliable script, but I didnt get any further through the process. Now, I believe the reason why it didnt go any further is that it was reviewed by some very experienced python developers; developers who can impress others with their clever use of (operationally unsupportable) one liners. I've since found out that TM are struggling to find an SRE, but that may be because they dont yet know what they are looking for. There is no operations team yet as the service isn't live to complete the feedback loop so all Dev have to go on is more Dev. What they are currently seeking is another Developer with advanced programming scripts who has had some operations interaction experience. This was evident from the feedback: "The role of SRE at Thought Machine requires advanced programming skills", "When developing applications or tools, we recommend providing automated unit tests", "Python offers virtual environments to avoid installing dependencies system-wide - should have used Docker".