> Markdown version of [/jobs/ext/4736302-iam-automation-engineer-iii-bu-info-security](https://www.wearedevelopers.com/jobs/ext/4736302-iam-automation-engineer-iii-bu-info-security). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # IAM Automation Engineer III, BU Info Security - **Company:** Boston University - **Location:** Boston, MA, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Microsoft Windows, Active Directory, Artificial Intelligence, Automation of Tests, C Sharp (Programming Language), Code Generation, Code Review, Information Leak Prevention, Linux, Identity and Access Management, Lightweight Directory Access Protocols (LDAP), OAuth, OpenID, Windows PowerShell, Regression Testing, Azure Active Directory, Ansible, Security Assertion Markup Language (SAML), Software Engineering, Retrieval-Augmented Generation, Large Language Models, Agentic-AI, Git, Containerization, AI Platforms, Kubernetes, Invoking Functions, SailPoint, Restful APIs, Model Context Protocol, Terraform, Software Version Control, Docker, Golang - **Published:** November 15, 2026 - **Apply:** https://www.wayup.com/i-Education-j-IAM-Automation-Engineer-III-BU-Info-Security-Boston-University-611600967641098/ ## About the Role + Bachelor's degree in a related field or equivalent experience. + 3+ years of related experience in identity and access management, security engineering, or infrastructure engineering, including hands-on software development and automation work. + Proficiency in at least one general-purpose programming language: Python, Go, Java, C#, or PowerShell. + Git-based version control, and experience building CI/CD pipelines that include automated testing. + Practical experience writing automated tests, including unit, integration, and regression tests. + REST API and directory service integration: LDAP, SAML, OAuth 2.0, OIDC, SCIM. + Linux and Windows administration. + Demonstrated fluency with current AI tooling, including routine use of AI-assisted development environments and practical experience integrating large language models or AI services into working tools using tool and function calling, retrieval-augmented generation, or agentic patterns. + Judgment about where AI output requires verification, and an understanding of how AI-generated code and tests fail. + Working understanding of the security risks specific to AI systems, including prompt injection, data leakage through model context, and authorization for non-human and agentic principals. + A track record of teaching or enabling colleagues: pairing, internal training, documentation others actually use, or reusable patterns adopted by a team., + If you do not meet these, you are still encouraged to apply; we value employees with a willingness to learn. + Model Context Protocol (MCP) server or client development - Infrastructure as code (Terraform, Ansible) and containerization (Docker, Kubernetes) ## Description If you like identity work but would rather automate a process than run it, we want to talk to you. Boston University's Identity and Access Management team supports Active Directory, Microsoft Entra ID, SailPoint IdentityIQ, and Radiant Logic across a mixed Linux and Windows environment, and we're modernizing the service as we go. This role does the same engineering work as the rest of the team, with one difference: we expect you to build it as code. Version control, pipelines, tests that run before a change ships, and monitoring you didn't have to remember to check. We also expect real fluency with current AI tooling - working in AI-assisted development environments day to day, using AI to help generate and validate tests and review code, and applying models to identity problems like entitlement mining, access request triage, and anomaly detection. That includes building MCP integrations that connect AI tools to our systems safely, and knowing when an AI approach is the wrong answer. The part that makes this role unusual is that raising everyone else's capability is a permanent part of the job, not a side project. You'll pair with colleagues on their first automation, build the patterns other people reuse, run working sessions, and keep the team current as the tooling shifts under all of us. If you like that kind of work, you'll have real room to shape how a major research university does this. You'll join a collaborative team with strong benefits, including tuition remission.