Senior Software Engineer II - Confluent, Product Security Access Management at IBM
ROCHESTER, MN
—
Jul 27, 2026
ROCHESTER, MN
Jul 29, 2026
What this job asks for AI summary
A software engineering role on IBM's Product Security Access Management team, focused on designing and implementing access control primitives for users and service accounts, including RBAC, ABAC, and related authorization policies. The work spans large-scale cloud systems and involves close collaboration with product, engineering, and security teams. Suited to engineers with a distributed systems background who want to specialize in identity and access management.
Mid level · 4+ years · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
No work location is specified in the posting — CBSA and state fields are left blank. The role may be remote or at an IBM office; the posting does not say.
The SOC classification is a judgement call: the role is primarily software development (building access management systems), but has a meaningful security engineering dimension. 15-1252 Software Developers was chosen because the JD emphasizes designing, building, and deploying code; 15-1212 Information Security Analysts is the runner-up.
The language requirement lists Java, Scala, C/C++, Go, or 'other statically typed languages' as alternatives — Java is used as the primary name with the others captured as alternatives.
Public cloud experience (AWS, Azure, GCP) and IAM domain experience appear under the Preferred section and are marked accordingly.
No compensation range is stated in the posting.
Seniority is assessed as Mid (4+ years, independent project execution on a team) despite the high-impact framing; the requirements do not describe org-wide technical authority or cross-team architectural leadership that would warrant Senior or above.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.