Cloud Operations Engineer

The Cloud Operations Engineer is vital for maintaining stability, availability, and performance of our cloud systems. Responsibilities include monitoring, ing, optimizing cloud infrastructure, collaborating across teams for seamless operations, and contributing to ongoing service improvement

Why

The company is building a cloud-based graphic and video production platform. The aim is to help small and big broadcasters produce their content using SaaS, cloud solutions. This is a challenging program as we are laying foundations of the company technology in the cloud for the next decade, if not for the next generation.

How

Our vision is to have highly-available and secure products, frequently delivering compelling features to our customers. Way to achieve this is through a systematic approach combining systems and software engineering. We would like to know about problems before our customers are impacted, we don’t like repeating issues, neither short-term solutions a.k.a. more future problems which are waiting for the worst timing. And automation is a must.

What

Our primary focus is on deep understanding of our customer needs, and our technology stack. We do primarily automation, incidents prevention, resolving them, and learning from them.

Must Haves

• Ability to understand and work with complex or distributed cloud systems
• Algorithmization and scripting ability (Python, Bash, PowerShell, or any scripting language)
• Willingness to learn AWS cloud
• Problem-solving attitude
• Oncall duty rotations are mandatory
• Communication skills for effective collaboration with , developers, and seamless handovers in an on-call AWS Cloud Ops role
  
  

Nice to Have

• Experience with public cloud (AWS, G, Azure)
• Understanding of best security practices, data protection and system integrity
• A fan of the post-mortem (lessons learned) culture
• Keep pace in fast, constantly changing environment - old (systems, technologies, procedures) is discarded and new is implemented constantly, changes are implemented as we constantly grow and learn
  

Not to Have

The position is not suitable for a person who is in general not thinking in a long term:

• Lacking a systematic approach, such as an aversion to following established processes, reluctance to document procedures, overlooking recurring issues, and showing a preference for manual repetition over automation
• Finishing tasks with minimal attention to detail, achieving basic functionality, and moving forward without gaining control over the underlying technology