I'm based in the Netherlands and recently started an internship focused on reducing toil and supporting a DevOps team. I originally got into cloud engineering almost by accident, so I'm still learning what the different roles actually involve.
While researching SRE careers, I saw average salary figures of around €90K per year in the Netherlands, with DevOps salaries supposedly about €20K lower. Those numbers seem surprisingly high to me, especially since entry-level roles requiring one to three years of experience appear to reach €60K or more.
If my internship goes well, I may be able to stay with the company and build more experience. The work I'm doing seems to overlap quite a bit with SRE responsibilities, so I'm trying to understand whether these salary figures are realistic and what explains the difference between SRE and DevOps pay. I'm currently learning Oracle-related cloud technologies as part of the role—does that expertise tend to be valuable in the Dutch job market?
4 Answers
Dutch salaries in that range definitely exist. One experienced cloud platform engineer working at an advisory level reported earning about €112K plus a company car, while a senior hire at the same organization started around €70K. That doesn’t mean every SRE role pays that much, but it shows the numbers aren’t necessarily fabricated. Seniority, employer, location, and the exact scope of the role make a big difference.
Be careful when comparing countries. US compensation can be two or three times higher for similar titles, but those roles may come with higher living costs, weaker job security, longer workweeks, and employer-dependent health insurance. Dutch salaries can look lower while still providing a comfortable overall quality of life. For the Netherlands, €60K or more is plausible for an early-career role at a strong employer, but €90K is more likely to reflect experienced or specialized work than an average beginner salary.
SRE tends to have a higher salary band because it usually isn’t an entry-level job. Many employers expect a combination of software engineering, production operations, automation, scripting, and cloud experience. Junior SRE salaries may be close to junior DevOps salaries, but experienced candidates are rarer and are often trusted with more critical systems.
Those figures can be realistic, but the job titles overlap heavily. In some companies, DevOps is closer to enabling developers and maintaining infrastructure, while SRE usually combines software engineering, reliability work, automation, and reducing operational toil. SRE isn’t always a clearly defined role, and the actual responsibilities matter more than the title.
These teams often improve productivity, reliability, and operating costs rather than directly generating sales, so compensation usually depends on how critical the systems are, the company’s size, and the experience expected.
That makes sense, although I’m still wondering why SRE would be paid more if both roles mostly improve efficiency. In practice, the responsibilities seem to blend together and depend heavily on the organization.
That explanation fits what I’ve been seeing. The requirements often include scripting, Python or Java, and cloud expertise, so it seems like SRE is usually a progression from several related areas rather than a true junior position.