Systems Engineer II
Anaplan · Minneapolis, MN · 1 mo ago
On-siteInformation Technology$106k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also must not include sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes Base Salary Range: $106,000 USD - $152,000 USD. Also schedule: Successful hire will work hybrid schedule with 2 days/week in our Minneapolis North Loop office. So we have Pay and Schedule sections.
Also Benefits? Not explicitly mentioned. There's mention of "Everything that makes you unique is welcome; join us and let’s build what’s next - together!" but not benefits. There's a DEIB statement but that's boilerplate? It's about diversity, equity, inclusion and belonging. Might be considered EEO boilerplate; we should remove it as it's legal/EEO boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the DEIB paragraph and the Fraud Recruitment Disclaimer etc. Also remove "Our Commitment to Diversity, Equity, Inclusion and Belonging (DEIB)" etc. Also remove "Supported by operating principles..." maybe that's part of About the role? It's about culture. Could be considered part of About the role. We'll keep substantive description about company and culture as part of About the role.
We need sections: About the role (maybe a brief paragraph summarizing role). Responsibilities (list of duties). Requirements (maybe experience). Qualifications (education). Skills (maybe technical skills). Benefits (none). Pay (salary range). Schedule (hybrid). We'll decide.
Let's extract content:
Company description: At Anaplan, we are a team of innovators focused on optimizing business decision-making through our leading AI-infused scenario planning and analysis platform so our customers can outpace their competition and the market. What unites Anaplanners across teams and geographies is our collective commitment to our customers’ success and to our Winning Culture. Our customers rank among the who’s who in the Fortune 50. Coca-Cola, LinkedIn, Adobe, LVMH and Bayer are just a few of the 2,400+ global companies who rely on our best-in-class platform. Our Winning Culture is the engine that drives our teams of innovators. We champion diversity of thought and ideas, we behave like leaders regardless of title, we are committed to achieving ambitious goals, and we love celebrating our wins – big and small. Supported by operating principles of being strategy-led, values-based and disciplined in execution, you’ll be inspired, connected, developed and rewarded here. Everything that makes you unique is welcome; join us and let’s build what’s next - together!
That's about the company and culture; could be About the role.
Responsibilities: list under "Your Impact" with subheadings: Identity & Access Management (IAM): ... Microsoft 365 & Cloud Endpoint Administration: ... Slack Enterprise Grid Administration & Collaboration: ... Cross-System Integrations & Process Automation: ... Operational Health, Monitoring & Escalations: ...
We need to turn each bullet into
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also must not include sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes Base Salary Range: $106,000 USD - $152,000 USD. Also schedule: Successful hire will work hybrid schedule with 2 days/week in our Minneapolis North Loop office. So we have Pay and Schedule sections.
Also Benefits? Not explicitly mentioned. There's mention of "Everything that makes you unique is welcome; join us and let’s build what’s next - together!" but not benefits. There's a DEIB statement but that's boilerplate? It's about diversity, equity, inclusion and belonging. Might be considered EEO boilerplate; we should remove it as it's legal/EEO boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the DEIB paragraph and the Fraud Recruitment Disclaimer etc. Also remove "Our Commitment to Diversity, Equity, Inclusion and Belonging (DEIB)" etc. Also remove "Supported by operating principles..." maybe that's part of About the role? It's about culture. Could be considered part of About the role. We'll keep substantive description about company and culture as part of About the role.
We need sections: About the role (maybe a brief paragraph summarizing role). Responsibilities (list of duties). Requirements (maybe experience). Qualifications (education). Skills (maybe technical skills). Benefits (none). Pay (salary range). Schedule (hybrid). We'll decide.
Let's extract content:
Company description: At Anaplan, we are a team of innovators focused on optimizing business decision-making through our leading AI-infused scenario planning and analysis platform so our customers can outpace their competition and the market. What unites Anaplanners across teams and geographies is our collective commitment to our customers’ success and to our Winning Culture. Our customers rank among the who’s who in the Fortune 50. Coca-Cola, LinkedIn, Adobe, LVMH and Bayer are just a few of the 2,400+ global companies who rely on our best-in-class platform. Our Winning Culture is the engine that drives our teams of innovators. We champion diversity of thought and ideas, we behave like leaders regardless of title, we are committed to achieving ambitious goals, and we love celebrating our wins – big and small. Supported by operating principles of being strategy-led, values-based and disciplined in execution, you’ll be inspired, connected, developed and rewarded here. Everything that makes you unique is welcome; join us and let’s build what’s next - together!
That's about the company and culture; could be About the role.
Responsibilities: list under "Your Impact" with subheadings: Identity & Access Management (IAM): ... Microsoft 365 & Cloud Endpoint Administration: ... Slack Enterprise Grid Administration & Collaboration: ... Cross-System Integrations & Process Automation: ... Operational Health, Monitoring & Escalations: ...
We need to turn each bullet into - . The subheadings could be maybe part of responsibilities but we can keep them as plain text within li? Probably better to keep as separate headings? But instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings. Within Responsibilities we can have a with items that may contain multiple sentences.
We need to preserve all substantive info. So we need to include each duty.
Let's extract responsibilities:
- Administer and maintain our enterprise Okta tenant, including Single Sign-On (SSO), Multi-Factor Authentication (MFA), SAML 2.0, and OIDC integrations.
- Implement and manage automated provisioning and de-provisioning workflows using SCIM and Okta Workflows, bridging our core HRIS (e.g., Workday) with downstream systems.
- Audit and manage role-based access control (RBAC), security groups, and identity governance policies.
- Manage and optimize core Microsoft 365 services, including Entra ID (Azure AD), Exchange Online, SharePoint Online, OneDrive, and Teams.
- Support modern endpoint management via Microsoft Intune (MDM/MAM) for Windows, macOS, and mobile devices, including compliance policies, configuration profiles, and app deployments.
- Plan, test, and implement routine platform maintenance, service updates, and security baselines.
- Administer our Slack enterprise grid environment, including workspace architecture, user access, retention policies, and security configurations.
- Review, approve, deploy, and maintain Slack third-party apps, custom bots, and integrations across business workflows.
- Leverage Slack Workflow Builder and webhook integrations to automate operational alerts and cross-functional team processes.
- Design, build, and maintain robust API- and script-driven integrations connecting M365, Okta, Slack, HRIS, and other enterprise SaaS platforms.
- Develop, maintain, and schedule PowerShell scripts and API automation (Microsoft Graph, Okta APIs, Slack APIs) to eliminate manual administration and streamline joiner/mover/leaver (JML) processes.
- Monitor infrastructure and SaaS services using IT Operations Management (ITOM) and observability tools to proactively detect outages, latency, or integration failures.
- Manage and triage incident/request queues, acting as a Tier 2/3 escalation point for complex identity, messaging, and system integration issues.
- Create, maintain, and standardize comprehensive engineering runbooks, architectural diagrams, and support documentation.
That's responsibilities.
Experience/Requirements: "Your Experience" section lists:
- 3–5+ years of hands-on experience in a Systems Engineer, Systems Administrator, or IAM Engineer role supporting enterprise-scale SaaS and cloud environments.
- Okta Administration: Proven hands-on experience configuring Okta SSO, SCIM provisioning, Okta Workflows, and integrating Okta with HR systems (e.g., Workday) and enterprise SaaS targets.
- Microsoft 365 Administration: Deep technical working knowledge of Microsoft Entra ID (Azure AD), Exchange Online, SharePoint, Teams, and Microsoft Intune.
- Slack Administration: Practical experience administering Slack in a corporate environment, including user lifecycle management, app directory governance, and native/API integrations.
- Scripting & Automation: Strong scripting proficiency with PowerShell and experience interacting with RESTful APIs (JSON, cURL, Graph API, Webhooks).
- Protocols & Standards: Solid understanding of modern authentication and directory protocols (SAML 2.0, OAuth 2.0, OIDC, SCIM, LDAP, DNS).
- Operations & Ticketing: Demonstrated experience managing ticket queues (e.g., Jira Service Management, ServiceNow), managing incident escalations, and working with ITOM monitoring platforms.
- Communication & Teamwork: Excellent interpersonal and written communication skills with the ability to collaborate with global stakeholders and translate business requirements into technical solutions.
- Education: Bachelor’s degree in Computer Science, Information Technology, Computer Engineering, or equivalent practical experience.
We could split into Requirements (experience) and Qualifications (education) and Skills (technical). But we can also combine. The instruction: prefer a few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Requirements (includes experience, skills, qualifications), Pay, Schedule.
But we need to follow heading list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. We have About the role, Responsibilities, Requirements (experience), Qualifications (education), Skills (technical). Pay and Schedule.
We'll omit Benefits as not present.
Now we need to extract content for each.
About the role: combine company description and maybe the opening about role: "We are seeking a highly motivated Systems Engineer who will be responsible for supporting and maintaining our global enterprise. This is a fantastic opportunity to grow your skills in a dynamic, remote environment. The successful candidate will be a dedicated, hardworking individual with a drive for success, looking to bring their skillset to help support and drive our organization forward. Successful hire will work hybrid schedule with 2 days/week in our Minneapolis North Loop office." Actually schedule part we will put in Schedule section, but we could mention hybrid schedule there. But we should not duplicate. We'll keep schedule separate.
Thus About the role paragraph: At Anaplan, we are a team of innovators focused on optimizing business decision-making through our leading AI-infused scenario planning and analysis platform so our customers can outpace their competition and the market. What unites Anaplanners across teams and geographies is our collective commitment to our customers’ success and to our Winning Culture. Our customers rank among the who’s who in the Fortune 50. Coca-Cola, LinkedIn, Adobe, LVMH and Bayer are just a few of the 2,400+ global companies who rely on our best-in-class platform. Our Winning Culture is the engine that drives our teams of innovators. We champion diversity of thought and ideas, we behave like leaders regardless of title, we are committed to achieving ambitious goals, and we love celebrating our wins – big and small. Supported by operating principles of being strategy-led, values-based and disciplined in execution, you’ll be inspired, connected, developed and rewarded here. Everything that makes you unique is welcome; join us and let’s build what’s next - together! We are seeking a highly motivated Systems Engineer who will be responsible for supporting and maintaining our global enterprise. This is a fantastic opportunity to grow your skills in a dynamic, remote environment. The successful candidate will be a dedicated, hardworking individual with a drive for success, looking to bring their skillset to help support and drive our organization forward.
That seems good.
Responsibilities: as list.
Requirements: maybe the experience bullet points (3-5+ years, Okta, M365, Slack, Scripting, Protocols, Operations & Ticketing, Communication & Teamwork). We'll list as .
Qualifications: Education bullet: Bachelor’s degree in Computer Science, Information Technology, Computer Engineering, or equivalent practical experience.
Skills: maybe the Nice to Haves? But those are nice-to-haves, not required. Could be considered Skills? But we could put them under Skills as optional? The instruction: include section only when posting has real, specific content for it. Nice to Haves are specific content. So we could have Skills section containing both required skills and nice-to-haves? But we already have Requirements covering required skills. Skills could be nice-to-haves. Let's treat Skills as nice-to-haves.
Thus Skills: list of nice-to-haves: Okta Certified Administrator or Okta Certified Developer; Microsoft Certified: Enterprise Administrator Expert, Azure Administrator Associate (AZ-104), or Endpoint Administrator Associate (MD-102); Slack Certified Admin; AI Tooling & MCP Engineering: Experience leveraging Enterprise AI tools and modern command-line utilities to accelerate scripting, troubleshooting, and documentation, combined with hands-on experience building, containerizing, or extending custom MCP servers/tools, integrating LLM APIs into corporate IT workflows, or orchestrating multi-agent systems; Advanced IAM Knowledge: Exposure to Okta Identity Governance (IGA), Inline Hooks, or event-driven automation; Advanced Automation: Experience with Python, Bash, or infrastructure-as-code/automation platforms (e.g., Zapier, Workato, Power Automate); A bias for action, continuous improvement mindset, and a strong problem-solving orientation.
We'll include those.
Pay: Base Salary Range:: $106,000 USD - $152,000 USD. Note there is double colon; we just
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings. Within Responsibilities we can have a with items that may contain multiple sentences.
We need to preserve all substantive info. So we need to include each duty.
Let's extract responsibilities:
- Administer and maintain our enterprise Okta tenant, including Single Sign-On (SSO), Multi-Factor Authentication (MFA), SAML 2.0, and OIDC integrations.
- Implement and manage automated provisioning and de-provisioning workflows using SCIM and Okta Workflows, bridging our core HRIS (e.g., Workday) with downstream systems.
- Audit and manage role-based access control (RBAC), security groups, and identity governance policies.
- Manage and optimize core Microsoft 365 services, including Entra ID (Azure AD), Exchange Online, SharePoint Online, OneDrive, and Teams.
- Support modern endpoint management via Microsoft Intune (MDM/MAM) for Windows, macOS, and mobile devices, including compliance policies, configuration profiles, and app deployments.
- Plan, test, and implement routine platform maintenance, service updates, and security baselines.
- Administer our Slack enterprise grid environment, including workspace architecture, user access, retention policies, and security configurations.
- Review, approve, deploy, and maintain Slack third-party apps, custom bots, and integrations across business workflows.
- Leverage Slack Workflow Builder and webhook integrations to automate operational alerts and cross-functional team processes.
- Design, build, and maintain robust API- and script-driven integrations connecting M365, Okta, Slack, HRIS, and other enterprise SaaS platforms.
- Develop, maintain, and schedule PowerShell scripts and API automation (Microsoft Graph, Okta APIs, Slack APIs) to eliminate manual administration and streamline joiner/mover/leaver (JML) processes.
- Monitor infrastructure and SaaS services using IT Operations Management (ITOM) and observability tools to proactively detect outages, latency, or integration failures.
- Manage and triage incident/request queues, acting as a Tier 2/3 escalation point for complex identity, messaging, and system integration issues.
- Create, maintain, and standardize comprehensive engineering runbooks, architectural diagrams, and support documentation.
That's responsibilities.
Experience/Requirements: "Your Experience" section lists:
- 3–5+ years of hands-on experience in a Systems Engineer, Systems Administrator, or IAM Engineer role supporting enterprise-scale SaaS and cloud environments.
- Okta Administration: Proven hands-on experience configuring Okta SSO, SCIM provisioning, Okta Workflows, and integrating Okta with HR systems (e.g., Workday) and enterprise SaaS targets.
- Microsoft 365 Administration: Deep technical working knowledge of Microsoft Entra ID (Azure AD), Exchange Online, SharePoint, Teams, and Microsoft Intune.
- Slack Administration: Practical experience administering Slack in a corporate environment, including user lifecycle management, app directory governance, and native/API integrations.
- Scripting & Automation: Strong scripting proficiency with PowerShell and experience interacting with RESTful APIs (JSON, cURL, Graph API, Webhooks).
- Protocols & Standards: Solid understanding of modern authentication and directory protocols (SAML 2.0, OAuth 2.0, OIDC, SCIM, LDAP, DNS).
- Operations & Ticketing: Demonstrated experience managing ticket queues (e.g., Jira Service Management, ServiceNow), managing incident escalations, and working with ITOM monitoring platforms.
- Communication & Teamwork: Excellent interpersonal and written communication skills with the ability to collaborate with global stakeholders and translate business requirements into technical solutions.
- Education: Bachelor’s degree in Computer Science, Information Technology, Computer Engineering, or equivalent practical experience.
We could split into Requirements (experience) and Qualifications (education) and Skills (technical). But we can also combine. The instruction: prefer a few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Requirements (includes experience, skills, qualifications), Pay, Schedule.
But we need to follow heading list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. We have About the role, Responsibilities, Requirements (experience), Qualifications (education), Skills (technical). Pay and Schedule.
We'll omit Benefits as not present.
Now we need to extract content for each.
About the role: combine company description and maybe the opening about role: "We are seeking a highly motivated Systems Engineer who will be responsible for supporting and maintaining our global enterprise. This is a fantastic opportunity to grow your skills in a dynamic, remote environment. The successful candidate will be a dedicated, hardworking individual with a drive for success, looking to bring their skillset to help support and drive our organization forward. Successful hire will work hybrid schedule with 2 days/week in our Minneapolis North Loop office." Actually schedule part we will put in Schedule section, but we could mention hybrid schedule there. But we should not duplicate. We'll keep schedule separate.
Thus About the role paragraph: At Anaplan, we are a team of innovators focused on optimizing business decision-making through our leading AI-infused scenario planning and analysis platform so our customers can outpace their competition and the market. What unites Anaplanners across teams and geographies is our collective commitment to our customers’ success and to our Winning Culture. Our customers rank among the who’s who in the Fortune 50. Coca-Cola, LinkedIn, Adobe, LVMH and Bayer are just a few of the 2,400+ global companies who rely on our best-in-class platform. Our Winning Culture is the engine that drives our teams of innovators. We champion diversity of thought and ideas, we behave like leaders regardless of title, we are committed to achieving ambitious goals, and we love celebrating our wins – big and small. Supported by operating principles of being strategy-led, values-based and disciplined in execution, you’ll be inspired, connected, developed and rewarded here. Everything that makes you unique is welcome; join us and let’s build what’s next - together! We are seeking a highly motivated Systems Engineer who will be responsible for supporting and maintaining our global enterprise. This is a fantastic opportunity to grow your skills in a dynamic, remote environment. The successful candidate will be a dedicated, hardworking individual with a drive for success, looking to bring their skillset to help support and drive our organization forward.
That seems good.
Responsibilities: as list.
Requirements: maybe the experience bullet points (3-5+ years, Okta, M365, Slack, Scripting, Protocols, Operations & Ticketing, Communication & Teamwork). We'll list as .
Qualifications: Education bullet: Bachelor’s degree in Computer Science, Information Technology, Computer Engineering, or equivalent practical experience.
Skills: maybe the Nice to Haves? But those are nice-to-haves, not required. Could be considered Skills? But we could put them under Skills as optional? The instruction: include section only when posting has real, specific content for it. Nice to Haves are specific content. So we could have Skills section containing both required skills and nice-to-haves? But we already have Requirements covering required skills. Skills could be nice-to-haves. Let's treat Skills as nice-to-haves.
Thus Skills: list of nice-to-haves: Okta Certified Administrator or Okta Certified Developer; Microsoft Certified: Enterprise Administrator Expert, Azure Administrator Associate (AZ-104), or Endpoint Administrator Associate (MD-102); Slack Certified Admin; AI Tooling & MCP Engineering: Experience leveraging Enterprise AI tools and modern command-line utilities to accelerate scripting, troubleshooting, and documentation, combined with hands-on experience building, containerizing, or extending custom MCP servers/tools, integrating LLM APIs into corporate IT workflows, or orchestrating multi-agent systems; Advanced IAM Knowledge: Exposure to Okta Identity Governance (IGA), Inline Hooks, or event-driven automation; Advanced Automation: Experience with Python, Bash, or infrastructure-as-code/automation platforms (e.g., Zapier, Workato, Power Automate); A bias for action, continuous improvement mindset, and a strong problem-solving orientation.
We'll include those.
Pay: Base Salary Range:: $106,000 USD - $152,000 USD. Note there is double colon; we just
- .
Qualifications: Education bullet: Bachelor’s degree in Computer Science, Information Technology, Computer Engineering, or equivalent practical experience.
Skills: maybe the Nice to Haves? But those are nice-to-haves, not required. Could be considered Skills? But we could put them under Skills as optional? The instruction: include section only when posting has real, specific content for it. Nice to Haves are specific content. So we could have Skills section containing both required skills and nice-to-haves? But we already have Requirements covering required skills. Skills could be nice-to-haves. Let's treat Skills as nice-to-haves.
Thus Skills: list of nice-to-haves: Okta Certified Administrator or Okta Certified Developer; Microsoft Certified: Enterprise Administrator Expert, Azure Administrator Associate (AZ-104), or Endpoint Administrator Associate (MD-102); Slack Certified Admin; AI Tooling & MCP Engineering: Experience leveraging Enterprise AI tools and modern command-line utilities to accelerate scripting, troubleshooting, and documentation, combined with hands-on experience building, containerizing, or extending custom MCP servers/tools, integrating LLM APIs into corporate IT workflows, or orchestrating multi-agent systems; Advanced IAM Knowledge: Exposure to Okta Identity Governance (IGA), Inline Hooks, or event-driven automation; Advanced Automation: Experience with Python, Bash, or infrastructure-as-code/automation platforms (e.g., Zapier, Workato, Power Automate); A bias for action, continuous improvement mindset, and a strong problem-solving orientation.
We'll include those.
Pay: Base Salary Range:: $106,000 USD - $152,000 USD. Note there is double colon; we just