Site Reliability Engineer

At Jamf, we believe in an open, flexible culture based on respect and trust. Our track record and thriving work environment all stem from the freedom we grant ourselves to get the job done right. We take pride in helping tens of thousands of customers around the globe succeed with Apple.

The secret to our success lies in our connectivity, while operating with a high degree of flexibility. Work-life balance remains our priority while feeling connected is important to maintain our strong culture, achieve our goals, and thrive as #OneJamf.

What you’ll do at Jamf:

As a Senior Site Reliability Engineer, you'll help us balance development velocity with the reliability our customers depend on. You'll partner with engineering teams to shape how their services are measured, lead the work to improve them, and use what you learn from production to build the automation and agentic tooling that improves reliability globally. You'll work fluently with agentic development tools as part of your everyday practice, using them to move faster, to investigate harder problems and to multiply your impact. This is individual contributor role at the intersection of Engineering, Product, Customer Success and Technical Support, where you'll play a meaningful part in shaping how we practice SRE at Jamf.

This role if offered as remote in Poland. You may be required to work periodically at a Jamf office or collaborative work location with other Jamf employees in your area for certain events or moments that matter. We are only able to accept applications for those based in Poland and have sponsorship to live and work in Poland.

#LI-Remote

What you can expect to do in this role:

• Partner with engineering teams to define service-level objectives, error budgets, and supporting indicators for their services, and help them use those measures to inform prioritization and reliability investment. 
• Investigate complex production issues end-to-end across application, data, infrastructure, and network layers, using AI to correlate logs, metrics, and code and to pressure-test hypotheses before acting.
• Produce clear technical documentation, runbooks, architecture notes, postmortems and proofs of concept for both technical and non-technical audiences, in a form that engineers and AI tools can re-use.
• Identify systemic sources of toil and lead the work to eliminate them through automation, AI agents, tooling, and process change. 
• Set the conditions for AI agents to do reliable work in our environment, including repository context, well-specified tasks, integrations such as MCP servers that give AI safe access to the systems it needs, and the tests and guardrails needed for AI-authored change to be trusted.