At Bigleaf we've recognized that the cloud is only as good as your connection. Bigleaf optimizes business Internet for access to cloud applications including VoIP, VDI, and SaaS. If your business relies on the internet then you need Bigleaf. With previously unavailable features such as Seamless Failover for all applications, Intelligent Load-Balancing, and Dynamic Quality-of-Service over commodity internet, Bigleaf unlocks the power of the cloud.

Bigleaf Networks

United States

Site Reliability Engineer

If you are passionate about creating scalable, highly reliable software systems and work well in a fast paced atmosphere, this might be a great role for you! Welcome to Bigleaf – We keep businesses connected to the cloud. Wonder how that works? Check out the videos on our homepage:? https://www.bigleaf.net/how-it-works

Bigleaf is growing quickly and we have big plans. We’re looking for a Site Reliability Engineer to join our team. We’re a well-funded fast-growing startup, so your day-to-day tasks will vary quite a bit and morph over time, but here’s an overview:

What you’ll be doing:

As a Site Reliability Engineer at Bigleaf you’ll be working with our network operations, support, and development teams to resolve customer issues, build and maintain internal and public-facing infrastructure (hardware and software), and to identify and resolve system issues in a dynamic fast paced environment. We are looking for someone that believes that operations is a software problem and seeks to define prescriptive ways for measuring availability, uptime, outages, toil, etc.

Responsibilities:

  • Provide the first line of internal support for the Bigleaf server, OS, and software infrastructure, including triage of software, networking, resource, and security issues
  • Build, maintain, and deploy infrastructure for software and hardware systems
  • Maintain and extend the Bigleaf development environment including Linux tools, Bamboo, Puppet, Terraform, AWS, Azure and other cloud providers
  • Share ownership with developers by using the same tools and techniques across the stack
  • Have a formula for balancing accidents and failures against new releases
  • Encourage automation and minimize manual systems work to focus on efforts that bring long-term value to the system