FAQs
What skills are necessary for the Site Reliability Engineer position?
Necessary skills include experience in site reliability, scalability, performance, cost management, monitoring solutions, debugging applications, and supporting production workloads in languages such as Node, Typescript, Ruby, Java, and Python. Familiarity with AWS services, Kubernetes, DevOps practices, Infrastructure-as-Code tools like Terraform, database performance tuning, and Linux CLI is also important.
What responsibilities will I have as a Site Reliability Engineer?
As a Site Reliability Engineer, you will define and implement best practices for site reliability, design monitoring solutions, troubleshoot applications with development engineers, support production applications, ensure security and compliance, collaborate with the Platform team, and manage your workload autonomously. You will also participate in an on-call rotation.
What programming languages should I be proficient in for this role?
Proficiency in programming languages such as Python, Ruby, Java, Node, and Typescript is expected for this position.
What is the importance of APM (Application Performance Monitoring) in this role?
APM is important as it allows you to monitor application performance, identify bottlenecks, and debug complex microservice applications, which is crucial for maintaining the reliability and performance of the systems.
How much experience should I have to apply for this role?
Candidates should have at least 3 years of experience in an SRE or development role, 1 year of experience with Kubernetes, 2 years of experience in system architecture, and 1 year of DevOps experience.
Will I need to work independently in this position?
Yes, the role requires a self-starter who can operate autonomously, manage their workload effectively, and take initiative in improving applications and systems.
What kind of work environment should I expect?
You should expect a highly collaborative and fast-paced work environment, where you will work closely with global R&D teams and various engineering initiatives.
Is experience with cloud services important for this position?
Yes, experience with AWS core services such as EC2, RDS, S3, Cloudwatch, and WAF is essential for this position.
What is the significance of working with Infrastructure-as-Code tools?
Working with Infrastructure-as-Code tools allows for better management of infrastructure, automation of deployments, and ensuring that the environment can be reliably reproduced, which is critical for maintaining consistency and efficiency in operations.
Will I need to participate in an on-call rotation?
Yes, participation in an on-call rotation with the Platform team is a requirement for this role.