Reliability Engineer I
Job Type: Full Time / Permanent
The Associate Reliability Engineer will work with other Reliability Engineers (RE), Product Managers, Software Engineers, and Architects to produce mission-critical infrastructure, tools, performance improvements, actionable and meaningful performance measurements, and communication to stakeholders. The RE will work with the business and technical teams to close gaps between solution design and business processes and assess impacts to services/processes across the enterprise. The RE role provides an opportunity to blend system design and software engineering skills with passion for troubleshooting and defects elimination to address an ever-changing applications and environments with scalability and reliability challenges.
Responsibilities: • Perform engineering and technical tasks as assigned by applying general engineering principles. • Perform independent research in support of technical tasks. • Contribute positively to open-source projects and join existing communities. Navigate this broader ecosystem and structure projects with upstream/ downstream opportunities in mind. • Participate in an on-call rotation, have strong written communication skills, and be able to develop working relationships with coworkers. • Provide technical expertise and consultation through direct involvement to identify and resolve problems. • Work frequently with Product teams on shared goals. • Troubleshoot infrastructure and application performance and availability issues. • Drive root cause analysis/investigations through identifying, analyzing, and remediating service(s) performance and availability issues to ensure maximum service uptime and availability. • Bring experience, pragmatism, empathy, and composure to interactions with teams outside of the RE organization. • Work frequently with Product teams on shared goals. • Balance planned and reactive work using basic project planning techniques and technical roadmaps. • Identify and integrate with third-party solutions where it makes the most sense. • Use data to understand the availability, reliability, and sustainability of our software.
Networking basics: TCP vs UDP, basic troubleshooting, HTTP – load balancing, firewall, private networks, multi-tier design, scale-out, persistent data • Cloud computing concepts (not necessarily provider specific) – VMs vs Docker Containers, block storage vs object storage, infra-automation vs install automation. • Experience operating a platform, software as a service, or shipping software. • First-hand experience with Prometheus and Istio. • Experience as an open-source contributor.