Automation Engineer
for each section. Use - for lists. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate.
We need to preserve all substantive information. Let's extract:
About the role: The first paragraph: "Varmoda is seeking a highly motivated Automation Engineer to design and implement automation solutions for OpenID Connect (OIDC) and SAML 2.0 integrations across approximately 900 systems for Minnesota agencies. The ideal candidate will have 5+ years of experience with OAuth 2.0/OIDC, Azure DevOps CI/CD pipelines, and identity workflows spanning Azure AD B2C and Oracle IAM technologies. This role will collaborate with business analysts and the State team to build repeatable onboarding processes, configure Azure Monitor and Log Analytics for workflow tracking, and design improved ChatBot and identity access management capabilities supporting the LoginMN Enhancements initiative."
That's about the role.
Responsibilities: list from "Roles And Responsibilities" bullet points.
Let's list them:
- Collaborate with business analysts to produce automation design method.
- Create program specifications and prototypes.
- Transform designs and specifications to create and test functions, scripts and high functioning code required to automate Open ID Connect (OIDC) and SAML 2.0 integrations.
- Test code to ensure it produces the desirable results and perform debugging, when necessary.
- Document clear and repeatable processes for onboarding applications that agencies can use.
- Assist with implementation of automation with approximately 900 systems across Minnesota agencies.
- Provide support and assistance on resolution of issues.
- Configure Azure Monitor and Application Insights for all automation workflows and custom policies to be able to track latency and errors.
- Configure Log Analytics to capture required logs to adequately monitor and troubleshoot automation workflows.
- Document and implement AI capabilities, necessary to automate integrations.
- Design and implement technical security controls to prevent compromising any programming, scripts or AI integrated technologies.
- Design improved ChatBot capabilities for the ChatBot can use machine learning to improve the customer experience and assistance.
- Design and implement method to correlate application logs to provide reporting capabilities to the customer and faster troubleshooting for the enterprise support team.
- Review current release management processes and procedures.
- Recommend and implement any improved efficiencies with utilization of the State's Github and Azure DevOps.
- Document any changes required to the constituent identity and access management standard resulting from the new design.
- Create knowledge articles and complete knowledge transfer to State team so they can support and modify capabilities implemented.
We need to keep them as list items.
Requirements: maybe they have "Desired Qualifications" which is more like requirements. Also "Education" and "Certifications". Could combine into Requirements and Qualifications sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have:
- About the role (intro)
- Responsibilities (list)
- Requirements (maybe experience requirements: 5+ years' knowledge of OAuth 2.0/OIDC, Azure DevOps CI/CD pipelines, etc.)
- Qualifications (education, certifications)
- Skills (maybe specific technical skills: IEF XML policy, MSAL, Oracle IAM, etc.)
- Benefits (competitive benefits etc.)
We need to avoid filler. Ensure each section has real content.
Let's parse the "Desired Qualifications" bullet list:
- 5+ years' knowledge of OAuth 2.0, OpenID Connect (OIDC), and authorization code flows used by Azure AD B2C and Oracle OAG experience.
- 5+ years' experience with Azure DevOps CI/CD pipelines for automating app registrations and API resource deployments.
- 5+ years' experience implementing custom orchestration steps, claims transformations, REST API integrations, and Microsoft Graph API–based operations.
- Hands-on experience building and securing APIs for identity workflows.
- Expertise in Identity Experience Framework (IEF) XML policy development and debugging.
- Experience integrating applications using MSAL for various platforms.
- Familiarity with Oracle IAM technologies including OAG, OUD, and Oracle Apex.
- Two (2) engagements lasting more than six (6) months in Developer/Programmer role using Azure B2C, Oracle OAG, Oracle OUD or Strata Maverics.
- Education Bachelor's degree in Computer Science, Information Systems, Software Engineering, or a related technical field required. Equivalent combination of relevant professional experience may substitute for the degree requirement on a year-for-year basis.
- Certifications (any one) SC-300 (Microsoft Certified: Identity and Access Administrator Associate) AZ-400 (Microsoft Certified: DevOps Engineer Expert) AZ-104 (Microsoft Certified: Azure Administrator Associate) Oracle Identity and Access Management Certified Implementation Specialist (or equivalent Oracle IAM credential, given OAG/OUD/Apex requirement)
We could split: Requirements = years of experience, core tech; Qualifications = education and certifications; Skills = specific expertise like IEF XML, MSAL, Oracle IAM, etc. But there is overlap.
Better: Requirements: the 5+ years experience items. Qualifications: Education and Certifications. Skills: Expertise in IEF XML, MSAL, Oracle IAM, building/securing APIs, etc. However the "Desired Qualifications" includes both experience and education. We'll follow the instruction: include sections only when posting has real specific content. We have content for each.
Let's craft:
About the role
Varmoda is seeking a highly motivated Automation Engineer to design and implement automation solutions for OpenID Connect (OIDC) and SAML 2.0 integrations across approximately 900 systems for Minnesota agencies. The ideal candidate will have 5+ years of experience with OAuth 2.0/OIDC, Azure DevOps CI/CD pipelines, and identity workflows spanning Azure AD B2C and Oracle IAM technologies. This role will collaborate with business analysts and the State team to build repeatable onboarding processes, configure Azure Monitor and Log Analytics for workflow tracking, and design improved ChatBot and identity access management capabilities supporting the LoginMN Enhancements initiative.
Responsibilities
- Collaborate with business analysts to produce automation design method.
- Create program specifications and prototypes.
- Transform designs and specifications to create and test functions, scripts and high functioning code required to automate Open ID Connect (OIDC) and SAML 2.0 integrations.
- Test code to ensure it produces the desirable results and perform debugging, when necessary.
- Document clear and repeatable processes for onboarding applications that agencies can use.
- Assist with implementation of automation with approximately 900 systems across Minnesota agencies.
- Provide support and assistance on resolution of issues.
- Configure Azure Monitor and Application Insights for all automation workflows and custom policies to be able to track latency and errors.
- Configure Log Analytics to capture required logs to adequately monitor and troubleshoot automation workflows.
- Document and implement AI capabilities, necessary to automate integrations.
- Design and implement technical security controls to prevent compromising any programming, scripts or AI integrated technologies.
- Design improved ChatBot capabilities for the ChatBot can use machine learning to improve the customer experience and assistance.
- Design and implement method to correlate application logs to provide reporting capabilities to the customer and faster troubleshooting for the enterprise support team.
- Review current release management processes and procedures.
- Recommend and implement any improved efficiencies with utilization of the State's Github and Azure DevOps.
- Document any changes required to the constituent identity and access management standard resulting from the new design.
- Create knowledge articles and complete knowledge transfer to State team so they can support and modify capabilities implemented.
Requirements
- 5+ years' knowledge of OAuth 2.0, OpenID Connect (OIDC), and authorization code flows used by Azure AD B2C and Oracle OAG.
- 5+ years' experience with Azure DevOps CI/CD pipelines for automating app registrations and API resource deployments.
- 5+ years' experience implementing custom orchestration steps, claims transformations, REST API integrations, and Microsoft Graph API–based operations.
- Hands-on experience building and securing APIs for identity workflows.
Qualifications
- Bachelor's degree in Computer Science, Information Systems, Software Engineering, or a related technical field required. Equivalent combination of relevant professional experience may substitute for the degree requirement on a year-for-year basis.
- Certifications (any one): SC-300 (Microsoft Certified: Identity and Access Administrator Associate), AZ-400 (Microsoft Certified: DevOps Engineer Expert), AZ-104 (Microsoft Certified: Azure Administrator Associate), Oracle Identity and Access Management Certified Implementation Specialist (or equivalent Oracle IAM credential).
Skills
- Expertise in Identity Experience Framework (IEF) XML policy development and debugging.
- Experience integrating applications using MSAL for various platforms.
- Familiarity with Oracle IAM technologies including OAG, OUD, and Oracle Apex.
- Two (2) engagements lasting more than six (6) months in Developer/Programmer role using Azure B2C, Oracle OAG, Oracle OUD or Strata Maverics.
Benefits
- Competitive benefits including 401k, health insurance, Paid Time Off, Life Insurance and others — customizable per role/location.
- Growth opportunity within a fast‑scaling federal IT firm.
- Direct impact on citizen‑facing federal programs.
- Veteran‑friendly (V3) workplace culture.
We should not include Pay or Schedule sections.
Check for any boilerplate: we removed "About Varmoda" description? Actually we included some of that in Benefits? The "About Varmoda" paragraph about company background could be considered "About the company" but not requested headings. The instruction says to include sections only when posting has real specific content for headings list. There's no heading for "About Varmoda". We could incorporate that into About the role? But we already have About the role describing the role. The company description could be omitted as not required headings. However we might want to keep it as part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." It didn't forbid including company description in About the role paragraph. But we already have a paragraph about the role; we could add a sentence about Varmoda. However the instruction says "Prefer a few substantive sections over many thin ones." It's okay to keep About the role as is. The company description could be considered minor metadata; we could fold into About the role paragraph. Let's add a sentence: "Varmoda is a federal IT solutions provider founded in
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive information. Let's extract: About the role: The first paragraph: "Varmoda is seeking a highly motivated Automation Engineer to design and implement automation solutions for OpenID Connect (OIDC) and SAML 2.0 integrations across approximately 900 systems for Minnesota agencies. The ideal candidate will have 5+ years of experience with OAuth 2.0/OIDC, Azure DevOps CI/CD pipelines, and identity workflows spanning Azure AD B2C and Oracle IAM technologies. This role will collaborate with business analysts and the State team to build repeatable onboarding processes, configure Azure Monitor and Log Analytics for workflow tracking, and design improved ChatBot and identity access management capabilities supporting the LoginMN Enhancements initiative." That's about the role. Responsibilities: list from "Roles And Responsibilities" bullet points. Let's list them: - Collaborate with business analysts to produce automation design method. - Create program specifications and prototypes. - Transform designs and specifications to create and test functions, scripts and high functioning code required to automate Open ID Connect (OIDC) and SAML 2.0 integrations. - Test code to ensure it produces the desirable results and perform debugging, when necessary. - Document clear and repeatable processes for onboarding applications that agencies can use. - Assist with implementation of automation with approximately 900 systems across Minnesota agencies. - Provide support and assistance on resolution of issues. - Configure Azure Monitor and Application Insights for all automation workflows and custom policies to be able to track latency and errors. - Configure Log Analytics to capture required logs to adequately monitor and troubleshoot automation workflows. - Document and implement AI capabilities, necessary to automate integrations. - Design and implement technical security controls to prevent compromising any programming, scripts or AI integrated technologies. - Design improved ChatBot capabilities for the ChatBot can use machine learning to improve the customer experience and assistance. - Design and implement method to correlate application logs to provide reporting capabilities to the customer and faster troubleshooting for the enterprise support team. - Review current release management processes and procedures. - Recommend and implement any improved efficiencies with utilization of the State's Github and Azure DevOps. - Document any changes required to the constituent identity and access management standard resulting from the new design. - Create knowledge articles and complete knowledge transfer to State team so they can support and modify capabilities implemented. We need to keep them as list items. Requirements: maybe they have "Desired Qualifications" which is more like requirements. Also "Education" and "Certifications". Could combine into Requirements and Qualifications sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where. We have: - About the role (intro) - Responsibilities (list) - Requirements (maybe experience requirements: 5+ years' knowledge of OAuth 2.0/OIDC, Azure DevOps CI/CD pipelines, etc.) - Qualifications (education, certifications) - Skills (maybe specific technical skills: IEF XML policy, MSAL, Oracle IAM, etc.) - Benefits (competitive benefits etc.) We need to avoid filler. Ensure each section has real content. Let's parse the "Desired Qualifications" bullet list: - 5+ years' knowledge of OAuth 2.0, OpenID Connect (OIDC), and authorization code flows used by Azure AD B2C and Oracle OAG experience. - 5+ years' experience with Azure DevOps CI/CD pipelines for automating app registrations and API resource deployments. - 5+ years' experience implementing custom orchestration steps, claims transformations, REST API integrations, and Microsoft Graph API–based operations. - Hands-on experience building and securing APIs for identity workflows. - Expertise in Identity Experience Framework (IEF) XML policy development and debugging. - Experience integrating applications using MSAL for various platforms. - Familiarity with Oracle IAM technologies including OAG, OUD, and Oracle Apex. - Two (2) engagements lasting more than six (6) months in Developer/Programmer role using Azure B2C, Oracle OAG, Oracle OUD or Strata Maverics. - Education Bachelor's degree in Computer Science, Information Systems, Software Engineering, or a related technical field required. Equivalent combination of relevant professional experience may substitute for the degree requirement on a year-for-year basis. - Certifications (any one) SC-300 (Microsoft Certified: Identity and Access Administrator Associate) AZ-400 (Microsoft Certified: DevOps Engineer Expert) AZ-104 (Microsoft Certified: Azure Administrator Associate) Oracle Identity and Access Management Certified Implementation Specialist (or equivalent Oracle IAM credential, given OAG/OUD/Apex requirement) We could split: Requirements = years of experience, core tech; Qualifications = education and certifications; Skills = specific expertise like IEF XML, MSAL, Oracle IAM, etc. But there is overlap. Better: Requirements: the 5+ years experience items. Qualifications: Education and Certifications. Skills: Expertise in IEF XML, MSAL, Oracle IAM, building/securing APIs, etc. However the "Desired Qualifications" includes both experience and education. We'll follow the instruction: include sections only when posting has real specific content. We have content for each. Let's craft:
About the role
Varmoda is seeking a highly motivated Automation Engineer to design and implement automation solutions for OpenID Connect (OIDC) and SAML 2.0 integrations across approximately 900 systems for Minnesota agencies. The ideal candidate will have 5+ years of experience with OAuth 2.0/OIDC, Azure DevOps CI/CD pipelines, and identity workflows spanning Azure AD B2C and Oracle IAM technologies. This role will collaborate with business analysts and the State team to build repeatable onboarding processes, configure Azure Monitor and Log Analytics for workflow tracking, and design improved ChatBot and identity access management capabilities supporting the LoginMN Enhancements initiative.
Responsibilities
- Collaborate with business analysts to produce automation design method.
- Create program specifications and prototypes.
- Transform designs and specifications to create and test functions, scripts and high functioning code required to automate Open ID Connect (OIDC) and SAML 2.0 integrations.
- Test code to ensure it produces the desirable results and perform debugging, when necessary.
- Document clear and repeatable processes for onboarding applications that agencies can use.
- Assist with implementation of automation with approximately 900 systems across Minnesota agencies.
- Provide support and assistance on resolution of issues.
- Configure Azure Monitor and Application Insights for all automation workflows and custom policies to be able to track latency and errors.
- Configure Log Analytics to capture required logs to adequately monitor and troubleshoot automation workflows.
- Document and implement AI capabilities, necessary to automate integrations.
- Design and implement technical security controls to prevent compromising any programming, scripts or AI integrated technologies.
- Design improved ChatBot capabilities for the ChatBot can use machine learning to improve the customer experience and assistance.
- Design and implement method to correlate application logs to provide reporting capabilities to the customer and faster troubleshooting for the enterprise support team.
- Review current release management processes and procedures.
- Recommend and implement any improved efficiencies with utilization of the State's Github and Azure DevOps.
- Document any changes required to the constituent identity and access management standard resulting from the new design.
- Create knowledge articles and complete knowledge transfer to State team so they can support and modify capabilities implemented.
Requirements
- 5+ years' knowledge of OAuth 2.0, OpenID Connect (OIDC), and authorization code flows used by Azure AD B2C and Oracle OAG.
- 5+ years' experience with Azure DevOps CI/CD pipelines for automating app registrations and API resource deployments.
- 5+ years' experience implementing custom orchestration steps, claims transformations, REST API integrations, and Microsoft Graph API–based operations.
- Hands-on experience building and securing APIs for identity workflows.
Qualifications
- Bachelor's degree in Computer Science, Information Systems, Software Engineering, or a related technical field required. Equivalent combination of relevant professional experience may substitute for the degree requirement on a year-for-year basis.
- Certifications (any one): SC-300 (Microsoft Certified: Identity and Access Administrator Associate), AZ-400 (Microsoft Certified: DevOps Engineer Expert), AZ-104 (Microsoft Certified: Azure Administrator Associate), Oracle Identity and Access Management Certified Implementation Specialist (or equivalent Oracle IAM credential).
Skills
- Expertise in Identity Experience Framework (IEF) XML policy development and debugging.
- Experience integrating applications using MSAL for various platforms.
- Familiarity with Oracle IAM technologies including OAG, OUD, and Oracle Apex.
- Two (2) engagements lasting more than six (6) months in Developer/Programmer role using Azure B2C, Oracle OAG, Oracle OUD or Strata Maverics.
Benefits
- Competitive benefits including 401k, health insurance, Paid Time Off, Life Insurance and others — customizable per role/location.
- Growth opportunity within a fast‑scaling federal IT firm.
- Direct impact on citizen‑facing federal programs.
- Veteran‑friendly (V3) workplace culture.
or drop it." It didn't forbid including company description in About the role paragraph. But we already have a paragraph about the role; we could add a sentence about Varmoda. However the instruction says "Prefer a few substantive sections over many thin ones." It's okay to keep About the role as is. The company description could be considered minor metadata; we could fold into About the role paragraph. Let's add a sentence: "Varmoda is a federal IT solutions provider founded in