- Company Name
- VTRAC Consulting Corporation (WBE)
- Job Title
- URGENT – Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid
- Job Description
-
<think>
Okay, let's tackle this query. The user wants to normalize a job description into a concise mini-job profile for job matching. They specified to exclude company details, location, benefits, and fluff. The output should include only Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, RequiredEducation & Certifications.
First, I need to parse the job description. The title is "Senior IAM Analyst (Okta, NIST, Azure AD)". The main responsibilities involve things like managing IAM systems, working with Okta, Azure AD, Auth0, integrating with enterprise systems, compliance with regulations, and supporting incident resolution.
The key points to extract are around IAM systems, specific tools like Okta, Auth0, Azure AD, integration with other systems like Salesforce, Active Directory, etc., compliance with frameworks like SOX, PIPEDA, and technical skills such as SAML, OAuth, Zero Trust. The required certifications are Okta certification, Microsoft SC-300, plus security certifications like CISSP, CISA. Education in Computer Science or related.
They want it factual and ATS-friendly, so using keywords is important. Need to condense responsibilities into bullet points without fluff. Make sure to avoid any company-specific details or locations. Also, the user mentioned "urgently", but since company details are to be excluded, maybe just include the position title without that.
Check if there's any overlap in responsibilities. For example, integrating identity platforms is mentioned in both IAM Management and Internal team responsibilities, so need to combine similar points. Also, the skills should list experience with specific IAM platforms, protocols, compliance standards, automation tools like Terraform, scripting.
Education and certifications: degree in Computer Science, required certifications are Okta and a security one. Need to list them under the appropriate sections.
Need to ensure the language is concise, under 500 words, and globally neutral. Use active verbs and past tense for responsibilities. Avoid any markdown formatting as per the user's request.
Wait, the user said "exclude location", so even though GTA is mentioned, it's location detail and should be omitted. Same with company details like VTRAC Consulting. Also, the hybrid work environment is under Position Description, but maybe not necessary to mention work type unless it's specified in the role summary. However, the user didn't mention excluding hybrid work, but the instruction says to exclude fluff. Maybe just keep it if it's relevant. Wait, the instruction says "exclude company details, location, benefits, or fluff." So if the hybrid is part of the position's structure, but maybe not necessary for the job matching summary. Hmm. Let me check the example. The original job description says hybrid, but the user wants to exclude fluff. Maybe the hybrid is part of the position type (Permanent, Hybrid). But in the job title, it's included. The user's example output should include the position type as part of the job title, so the output's job title should include "Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid" but the user wants to exclude company details. Wait, the job title is "URGENT – Senior IAM Analyst..." but the user wants to exclude fluff. So maybe remove "URGENT" from the job title since it's fluff. The user's instruction says: "Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So the job title should be "Senior IAM Analyst (Okta, NIST, Azure AD)" since "URGENT" is considered fluff. Also, the position type is Permanent and Hybrid, which can be included in the job title or in the role summary. The example in the user's mind may want the job title to include Permanent, Hybrid. The original job title has "Permanent, Hybrid", so maybe include that in the job title. However, the user's instruction says "URGENT..." should be excluded. So final job title: "Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid" but the "URGENT" is removed. Wait, the user might not want to include "Permanent" if it's considered part of the position type but not job title. Hmm. The original instruction says to output only the specific sections. The job title is given as "Senior IAM Analyst (Okta, NIST, Azure AD)", but in the job description, the position type is Permanent and hybrid. The user wants the job title as per the original, but minus the urgent. So the job title would be "Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid". Alternatively, maybe separate the job title and role summary. The user's example output shows the job title as "Senior IAM Analyst (Okta, NIST, Azure AD)" without "Permanent, Hybrid". Let me check the example given. Wait, the user hasn't provided an example, but the instruction says to output the job title as part of the structured sections. So the job title is part of the output. Since the job description's title includes "URGENT – Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid", the user wants to exclude fluff. So remove "URGENT" and perhaps "Permanent, Hybrid" if not part of the job title. However, the position type isPermanent and hybrid, which might be important for job matching. Maybe include it in the role summary instead of the title. For example, Role Summary can mention that it's a permanent, hybrid position. But the user wants the job title first. The original job title says "URGENT – Senior IAM Analyst...", so the actual title should be "Senior IAM Analyst (Okta, NIST, Azure AD)" without the "URGENT". Position type (Permanent, Hybrid) can be part of the role summary. Let me check the user's instructions again. They say "exclude company details, location, benefits, or fluff." The "URGENT" is considered fluff, so remove that. The position type (Permanent, Hybrid) is a detail about the job but is part of the job title in the original. However, the user might want to keep it in the job title for clarity. So, the job title would be "Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid" without "URGENT". Then, in the role summary, perhaps mention that it's a hybrid position. But the user wants to exclude location, but not work type. Wait, the user said exclude location, but hybrid is a work arrangement, not location. So need to include hybrid. Hmm, the instruction says "exclude company details, location, benefits, or fluff". Location is to be excluded, but work arrangement (hybrid) is allowed. So, the job title can have Permanent and Hybrid, as they are part of the position's work model, not location. So the job title is "Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid". Then in the Role Summary, perhaps mention working in a hybrid environment.
Now, for the Role Summary: Needs to be concise. The original describes the role as managing IAM systems for workforce, dealers, customers, ensuring secure access. So a summary might be: "Manages and enhances IAM systems to ensure secure, compliant access across enterprise platforms."
Expectations: These are probably the key skills and certifications required. Wait, the user's example uses "Expectations" as a section. The user's instruction says "Key Responsibilities" and "Expectations". Need to clarify. Wait, in the output sections, it's: Role Summary, Expectations, Key Responsibilities. The user's example includes "Expectations" as a section. Need to make sure each section is correctly filled.
Expectations might refer to the required experience and skills. But looking at the example provided by the user's job description, the "skills and requirements" section includes things like minimum 8 years of experience, which would fit under "Expectations" in the output. However, the user's instruction says to have "Expected Skills" but the user's own example here has "Expectations" as a separate section. So perhaps the "Expectations" section is where the candidate's experience and education requirements go. Let me check the user's instruction again:
They want: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
But in the example given by the user's job description, the "skills and requirements" include both skills and education. The user might want "Expectations" to include the experience required (minimum 8 years), and "Required Skills" to include the technical skills.
Wait, the user's instruction says to have six sections: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So "Expectations" is a section where you list the experience, maybe years required, etc. So in the user's example, the "skills and requirements" part has "Minimum 8 years of progressive experience...", which would go under "Expectations".
So for the "Expectations" section, we list the experience (minimum 8 years in IAM roles, etc.), and maybe the education requirement? Or is education under the Required Education section? The instruction says "Required Education & Certifications" as a separate section. So "Expectations" would be the experience and maybe other expectations like collaboration.
In the user's example, under Key Responsibilities, they have governance, integration, configuration, support. The "Expectations" section would include things like the 8-year requirement.
Putting it all together:
Job Title: Senior IAM Analyst (Okta, NIST, Azure AD), Permanent, Hybrid
Role Summary: Manages and enhances IAM systems to