- Company Name
- Vista Applied Solutions Group Inc
- Job Title
- Governance, Risk, and Compliance Analyst
- Job Description
-
<think>
Okay, let's tackle this query step by step. The user wants a mini-job profile for a Governance, Risk, and Compliance Analyst position. The main focus is on normalizing the job description into a concise summary for job matching.
First, I need to extract the key elements. The job title is clear, so that's straightforward. The role summary should encapsulate the main purpose. The given description mentions responsibilities related to governance, risk management, compliance, and using specific frameworks like NIST 800-53R5 and RMF. I should make sure these are included in the summary.
Next, expectations. The candidate needs to be local to Phoenix, within a 1-hour drive, and an in-person interview is required. However, the user specified to exclude company details, location, benefits, or fluff. Wait, the original instructions say to exclude location, but the job description has that requirement. Hmm, the user says "Exclude company details, location, benefits, or fluff." So even though the location is a requirement, we should omit it. Interesting. Same with the in-person interview—it's part of the process but maybe considered fluff? Wait, maybe the in-person interview is part of the process but not necessary for the job profile. The user probably wants to focus on the core responsibilities and requirements. So I'll exclude both location and in-person interview.
Now, required skills are NIST 800-53R5 and Risk Management Framework, plus Windows/Unix experience. Preferred skills include Project Management experience and certain certifications. But the user wants Required Skills and Required Education & Certifications. Since CISSP, CCSP, GSTRT, GSNA, or CAP are listed as preferred, maybe they should be in the required certifications if they're mandatory. Wait, the description says "Preferred Skills" for those certifications, but the user's instructions say to include "Required Education & Certifications." So perhaps only the required ones go there. But the user didn't mention any required certifications—only preferred. The required skills here are NIST, RMF, and Windows/Unix. So in Required Skills, include those. In the Required Education... the original job doesn't specify education, so maybe it's not necessary to include unless the user's example includes it. Wait, in the example output, they have "Required Education & Certifications." Since the job description doesn't mention education, maybe we leave it as just a bullet with nothing? But the user says "Required Education & Certifications." The original job doesn't specify education, but in the preferred skills, there are certifications. Since they are preferred, but not required, maybe they don't go into Required Certifications. So the Required Education & Certifications section might be empty. Wait, maybe the user expects it to be present regardless. Let me check the query again. The user says "Exclude company details, location, benefits, or fluff." The original job description doesn't mention education, so maybe we can omit that section if it's blank, but the user's example output includes it. Wait, looking back, the user says: "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications." So even if there's no education, we need to include the header and maybe leave it empty or not. But the user's example in their own query shows they didn't include education in their sample. Let me check the sample they provided in the user's question: under "Required Education & Certifications," they had "Bachelor’s degree in [relevant field] or equivalent experience." Wait no, in the user's example job description, the required skills are listed, but in the output they want, they include Required Education & Certifications. But in the given job description here, there's no education mentioned. So perhaps in this case, we should leave it blank. But the user's sample output (from their own example) includes it, so maybe we need to include it even if there's no info. For example, if there's no education requirement, perhaps we can state "Not specified" or omit it. However, the user's instructions say "Exclude... benefits or fluff." Since the job doesn't mention education, perhaps we can leave that section as is, maybe blank. But in the structure they outlined, they want all those sections. So I need to include all the headers, even if some are empty. Let me check again.
The user's output structure includes:
Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
The job description provided does not mention education or certifications as required. The required certifications are part of the preferred skills. So in Required Education & Certifications, if there's nothing required, perhaps we can leave it blank. However, the user might prefer to list the preferred certifications under "Required Education & Certifications" if they are desired but not mandatory. Wait, no—the user specifies "Required Education & Certifications" as a separate category. The preferred certifications are under preferred skills, so they should not be included in Required.
So the final step is to structure each section factually and concisely, using only the required information. The key responsibilities would be about performing risk assessments, ensuring compliance, analyzing governance frameworks, etc. The expectations are the ones about being local and in-person interview, but since location is excluded, maybe the expectations section is just the in-person interview, but the user said to exclude fluff. Wait, the original job says "Candidate has to be local to Phoenix meaning 1 hour drive max. In-Person Interview Required." However, the user instruction says to exclude location and benefits, etc. So maybe the expectations section should not include the location requirement. What about the in-person interview? The user says to exclude company details, location, benefits, or fluff. The in-person interview could be considered part of the application process, so maybe it's fluff. Therefore, the expectations section might not include anything else. Wait, maybe the expectations here are the core expectations for the role, like experience or skills, but the original job's expectations are about location and interview. Since we have to exclude location and it's part of the application process, maybe the expectations section is about the candidate's experience. Hmm. The user's example for expectations in their own example output was perhaps not present, but in the current case, the job description has "Candidate has to be local..." and "In-Person Interview Required." But since we have to exclude location and maybe the interview is part of the process, which is fluff, we omit both. Therefore, the expectations section might be omitted or left blank. But the user's desired output structure includes "Expectations," so maybe in this case, it's left blank. Alternatively, maybe the expectations refer to what the company expects from the candidate, not about the candidate's prerequisites. Wait, the user wrote "Expactations"—maybe a typo for Expectations. So perhaps the Expectations section is about what the role requires from the candidate. But the job description's expectations for the role are the required skills, which are already covered in the Required Skills section. So maybe in this case, the Expectations section is not needed, but the user's structure requires it. Hmm. To adhere to the structure, perhaps the Expectations section can be omitted if there's nothing else. But the user says "Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So even if some sections are empty, they still need to be included. So for the current job, since there's no other expectations except the location and interview which are excluded, maybe the Expectations section is left blank. But the user's example shows that in their sample job description, the expectations included something. However, in the current case, there's nothing else to include. Therefore, perhaps the Expectations section is left as is, with no entries. Alternatively, maybe the Expectations are about the candidate having experience in certain areas, but those are covered in Required Skills. So to avoid redundancy, maybe the Expectations section is omitted. But the user's instruction says to include all the mentioned sections. Therefore, even if it's empty, include it. But that might look odd. Alternatively, maybe the Expectations are about the experience level, like "X years of experience," but the job description doesn't mention that. Therefore, perhaps the Expectations section is empty. Hmm. I need to make sure I'm following the user's instructions precisely.
Putting it all together:
Job Title: Governance, Risk, and Compliance Analyst
Role Summary: Conduct risk assessments and ensure compliance with governance standards and regulatory frameworks. Develop and implement strategies to mitigate risks and maintain organizational compliance.
Expactations: [If there's nothing to include, but the structure requires it. Wait, maybe the user made a typo for "Expectations," wrote "Expactations." I'll go with "Expectations" as intended. Since there's no other expectations provided (experience years, etc.), perhaps leave it blank. But the user's example in the initial query might have included something. Wait, the original job description does not mention experience years. Therefore, maybe the Expectations section is blank. However, if the user expects it to be there, even without entries, include it. But perhaps the user intended "Expectations" to relate to what the candidate should expect, but since the user said to exclude fluff, maybe it's omitted. This is a bit ambiguous. To comply with the user's exact output structure, include the Expectations section but leave it empty if there's nothing to include. Alternatively, maybe the Expectations are derived from the key responsibilities, but that seems redundant.
After considering