Senior Site Reliability Engineer
About this position
Amity Solutions is seeking a Senior Site Reliability Engineer to ensure smooth service operations and future growth, while also helping developers release software securely and efficiently on cloud native applications.
Responsibilities
• Manage all aspects of infrastructure operations and management of cloud-based UAT/production systems to ensure availability, performance, and scalability
• Manage, innovate and create new processes, automation, information security and tooling that continuously improve our product and services' availability, scalability, latency, and efficiency
• Define strategy and procedures for 24x7 site reliability, escalation workflows, production incident resolution, and disaster recovery plans
• Ownership of all Cloud, Network, Virtualization Server, Datacenter, and related services on AWS service across our product
• Build application orchestration framework to host various types of production workloads, covering services management, big data jobs, and distributed storage services.
• Oversee budgeting for technology infrastructure and cloud computing
Requirements
• Site Reliability Engineer/Senior DevOps Engineers at Amity Solutions are hybrid Software/System engineers who ensure that our service runs smoothly and have the capacity for future growth. Also, help developers get software out the door more quickly and with security in mind on our cloud native application. You are expected to learn and expand on your engineering knowledge and experiences to build a world-class product together.
• We value efficiency and are always looking for ways to improve our tech stack to provide the best experience to our users. Our commitment to the latest developments in React, Mobx, Node.js, and native iOS and Android frameworks allows us to iterate quickly while providing a clean, maintainable architecture that's a joy to develop on.
• We put emphasis on the quality of the code, where each piece of the code will require unit tests and will be reviewed by at least two other backend engineers before merging any change.