You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Plume

Site Reliability Engineer

  • Office
  • 3-6 years

Salary

Not stated

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company runs an open, hardware-independent service delivery platform for smart homes, small businesses, enterprises and more. It uses WiFi, AI and machine learning to power connected spaces at large scale.

It serves more than 60 million locations worldwide and has managed over 3 billion devices. Over 400 ISPs use it, including some of the largest in the world, to evolve their smart home services and learn from their own data.

The company reached Series F funding in four years and is growing quickly in a category it is creating.

The team is made up of builders, thinkers and doers who question how things are usually done and only ship work they can do well.

The role sits in engineering. You will build the tools, processes and automation that product engineers rely on, while keeping systems stable and reliable. It calls for software engineering and cloud-native infrastructure skills, strong communication and a collaborative approach.

Responsibilities

  • Run scalable, reliable infrastructure defined as code with infrastructure-as-code (IaC) tools.
  • Build observability solutions so engineers can keep services highly available and performing well.
  • Create and maintain CI/CD pipelines that make deployments smoother.
  • Work with development teams to design services that are reliable and easy to operate.
  • Take part in a global on-call rotation supporting critical production systems.
  • Reduce repetitive operational work through automation and better processes.
  • Manage and tune cloud resources to keep costs down and performance high.

Requirements

  • Bachelor's degree in computer science, engineering or a related field, or equivalent experience.
  • 5+ years working as a Site Reliability Engineer, DevOps Engineer or in a similar role.
  • Strong skills in at least one programming language, such as Python or Go.
  • Experience with one or more cloud platforms, such as AWS or GCP.
  • Working knowledge of configuration management and IaC tools, such as Terraform or Salt.
  • Hands-on experience with Kubernetes-based environments.
  • Experience with monitoring and logging tools, such as Prometheus, Grafana or OpenSearch.
  • Clear, effective technical communication.
  • Preferred: experience with large-scale distributed systems.
  • Preferred: knowledge of networking and security best practices.
  • Preferred: familiarity with SQL and NoSQL database technologies.

Where you’d work

From the office

About the company

Plume

Office in Ljubljana, Slovenia

1 of their 4 open roles is remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 1 red flag

Still hiring?

13 checks

No red flags

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details9 facts · Role, Location, Compensation
Tech stack
  • Python
  • Go
  • AWS
  • Kubernetes
  • Terraform
  • Elasticsearch
  • CI/CD
  • Prometheus
  • Grafana
Specialty
SRE
Region
Europe
Pay period
Annual
Show 5 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
SRE
Experience
5+ years
Tech stack
  • Python
  • Go
  • AWS
  • Kubernetes
  • Terraform
  • Elasticsearch
  • CI/CD
  • Prometheus
  • Grafana

Location

Work model
Office
Region
Europe
Office
  • Ljubljana, Slovenia

Compensation

Salary
Salary by agreement
Pay period
Annual

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason