Site Reliability Engineer - Observability

As a Site Reliability Engineer - Observability at Komoju, your primary responsibilities will include designing and maintaining our observability stack, defining SLIs and SLOs for service health, collaborating with engineering teams to enhance application visibility, and building actionable dashboards and alerts. You'll also troubleshoot performance issues using observability data and educate engineering teams on monitoring best practices.

To qualify for the Site Reliability Engineer - Observability position at Komoju, candidates should have at least 3 years of experience in SRE roles, hands-on experience with observability tools like Datadog, proficiency with Terraform, and a background in software development. Knowledge of scripting languages, familiarity with AWS, and understanding monitoring design principles are also essential.

For the Site Reliability Engineer - Observability role at Komoju, proficiency in at least one programming or scripting language is necessary. Candidates should be comfortable with languages like Ruby/Rails, Python, Go, or Shell Script, as these will be crucial for developing and maintaining observability solutions effectively.

Yes, the Site Reliability Engineer - Observability position at Komoju supports a remote-first approach. While the role is primarily remote, candidates should be willing to relocate to Tokyo, as we also offer office space for those who prefer in-person collaboration.

Komoju provides a number of benefits for the Site Reliability Engineer - Observability role, including 10 vacation days, an additional 5 days each for summer and winter vacations, a paid birthday holiday, and a self-learning allowance to help employees keep their skills sharp. Language training for Japanese is also provided, enhancing your professional and personal development.

Talk about the observability tools you've used, such as Datadog, and describe specific metrics you monitored and improved. Sharing examples of how you enhanced performance through these tools can illustrate your expertise.

Discuss your approach to establishing service-level indicators (SLIs) and service-level objectives (SLOs). Explain how you ensure they align with business goals and are monitored effectively to maintain service health.

Share the systematic methods you adopt for troubleshooting, emphasizing your reliance on observability data. Provide examples where you successfully diagnosed issues and implemented solutions to improve performance.

Outline your approach to integrating observability in CI/CD, such as adding monitoring and alerting throughout the build and deploy processes. Mention specific tools or practices that help maintain observability.

Discuss the importance of clear documentation in incident response and system observability. Explain how you maintain documentation of processes, configurations, and best practices for easier team collaboration.

Explain methods you've used to minimize alert fatigue, such as refining alert thresholds and ensuring alerts provide actionable insights. Providing specific examples demonstrates your proactive approach.

Detail your experience in incident response, emphasizing how you became part of postmortem reviews. Discuss how these experiences contributed to lessons learned and system improvements.

Share strategies for educating teams, including training sessions, workshops, or collaborative retrospectives. Highlight any successful initiatives that fostered a culture of observability within your previous roles.

Discuss any programming or scripting languages you're proficient in and provide examples of how you've utilized them to automate processes or enhance observability.

Express your enthusiasm for Komoju’s role in empowering merchants through technology. Mention your alignment with their innovative culture and how you can leverage your skills in observability to contribute to their success.