About this role

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.

This role is offered as a remote in Poland . We are only able to accept applications for those based in Poland or who have sponsorship to live and work 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. What you'll do at Jamf : At Jamf, we empower people to be their best selves and do their best work.

As a Software Engineer II on a new team enabling secure, governed adoption of autonomous and agentic workflows, you'll help build production systems where AI agents do real work on real code - authoring changes inside deterministic gates, with independent verification and a full audit trail. This is a greenfield build inside a mature platform, starting with Security. What you can expect to do in this role: Build the production systems where AI agents do real work on real code – authoring changes that run inside deterministic gates, with independent verification and a full audit trail behind every one.

Take customer and platform problems, break them into workable pieces with your agile team, and own most of them end to end. Draw the line on autonomy: design the trust boundaries, blast radius, and least-privilege model for the automation itself, which holds elevated access to production. Build the evaluation and observability that keeps non-deterministic systems honest – measuring accuracy and catching silent degradation before anyone else does.

Make the systems answer the auditor's "show me" – producing evidence that a control worked, not just the claim that it did. Work shoulder to shoulder with security engineering and PDD developers, and explain the tricky parts clearly to the rest of the organization. Bring engineering best practices to the table: ask the sharp questions, solve the hard problems, and help others level up. #LI-Remote What we are looking for: Must-have: 3+ years building enterprise-grade software commercially, with a solid grasp of testing and QA.

3+ years of commercial experience in Java or Python. <li data-leveltext="•" data-fon

Source listing: greenhouse_jamf