- Company Name
- TEAM International
- Job Title
- Business Analyst
- Job Description
-
<think>
Okay, let me take a look at this query. The user wants me to normalize a job description into a concise mini-job profile for job matching. They specified excluding company details, location, benefits, and fluff. The output needs to be in English, factual, concise, ATS-friendly, and globally neutral. The required sections are Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. Max 500 words.
First, I need to parse the original job description. The job title is Business Analyst. The location and contract details are there, but those should be excluded. The company is looking for someone detail-oriented and adaptable, supporting operational and technical projects. The key responsibilities include gathering requirements, process mapping, documentation, project support, UAT, reporting, and administrative support. Skills required are experience as a BA or similar role, communication, cross-functional project experience, business process analysis, proficiency in tools. Preferred qualifications include project management methodologies and change management experience.
Now, translate the "About the Role" into a Role Summary. The summary should capture the essence: supporting operational and technical projects, clarifying needs, improving processes. Expectations would be the contract length and work permit info? Wait, the user said to exclude contract length and work permits. Wait, no, the user said to exclude company details, location, benefits, or fluff. So contract length and work permits are under the job description but need to be excluded. So focus on what's necessary for the role.
The Key Responsibilities should be bullet points from the job description. The Required Skills include the must-have skills. Education and certifications aren't mentioned in the original job description, so maybe leave that as "Not specified" or exclude it. But the user wants Required Education & Certifications. Since the job description doesn't mention educational requirements, perhaps just state it as not specified. Or maybe assume a bachelor's degree is typical for a Business Analyst role? Hmm, but the user wants to be factual. Since the original doesn't mention education, it's better not to add assumptions. So maybe leave it blank or note as not specified. However, the user included "Required Education & Certifications" as a section, so perhaps if there's nothing in the original, just omit or put N/A.
Wait, the original job description under Skills and Experience Required doesn't mention education. So Required Education & Certifications would be N/A. But the user wants that section included. So I need to include it as "Not specified" or leave it out. The example in the problem included "Required Education & Certifications," even if blank? The user says, "Output only:..." so maybe even if there's nothing, still include the section. But perhaps the original job description didn't specify, so in that case, leave it as blank or N/A?
Also, need to check if any certifications are required. The original job description under "Required Skills" doesn't mention any certifications. So under "Required Education & Certifications," probably just note that none are required or not specified.
Now, structuring the Role Summary: "Supports operational and technical projects by clarifying business needs, improving processes, and ensuring project delivery through stakeholder collaboration and requirement documentation."
Expectations: "Contract-based role requiring 4 months of service; work permits limited to US citizens and green card holders." Wait, but the user said to exclude location and work permits. Hmm, the work permits are part of the contract details, but the user said to exclude that. The user included in the job description the contract length and work permits, but those are considered under "exclude company details, location, benefits, or fluff." So contract length is part of "fluff"? The user said to exclude contract length. Wait, the user says "Exclude company details, location, benefits, or fluff." The contract length is part of the job post but not part of the role itself. So perhaps it's considered "fluff" and should be excluded. So in the Expectations section, maybe not include the contract length. But the original user provided "Contract Length: 4 month contract" under the job description, but per the instructions, that's fluff and should be excluded. Therefore, the Expectations section should not include contract length. So maybe the Expectations would focus on the day-to-day expectations based on the role. Wait, the user said "Expactations" which might be a typo for "Expectations," and the instruction says "Expactations" (probably meant Expectations). Let me check again.
In the initial query, the user wrote "Expactations, Key Responsibilities," probably a typo for "Expectations." So I should use "Expectations" correctly. But the user's own typo is in their query, but I should correct it in the output. Wait, no: the user instructed to output "Expactations," which is a typo. Wait, no, the user wrote in the instruction: "Expactations, Key Responsibilities," which is a typo for "Expectations," but the user wants the output to include that section. Wait, maybe the user actually meant "Expectations," but mistyped it. As an assistant, should I follow the exact typo or correct it? The user might be using a different language, so perhaps the correct term is "Expectations." However, since the user explicitly wrote "Expactations," maybe that's a typo. But since the user might have intended "Expectations," perhaps the correct approach is to correct the typo to "Expectations" in the output. However, the user may have specific formatting, so maybe follow exactly as written. Hmm. Let me check the user's original query again.
The user says: "Provide a concise summary... Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So the user wrote "Expactations." That's a typo. But the correct term is "Expectations." However, the user might want the output to mirror exactly what they wrote. But maybe the assistant should correct it. Since the user provided the typo, perhaps it's best to follow exactly. Alternatively, the user might have intended "Expectations," and it's a mistake. But the user might be using a non-native language. In this case, the correct approach is to output "Expectations" as the correct term. Otherwise, the output would have a typo. So I'll use "Expectations" correctly even though the user wrote a typo.
So, moving forward, the structure is:
Job Title: Business Analyst
Role Summary: [Summary as above]
Expectations: [What are the expectations? The original says "3 days a week onsite required" as part of the hybrid location, but the user wants to exclude location. However, the "hybrid 3 days a week onsite required" is part of the location. Wait, the user said to exclude location, but the "hybrid 3 days a week onsite required" is part of the job requirements. The user might consider that part of location, which should be excluded. However, the "3 days a week onsite required" is an expectation of the role, not just location. So maybe include the work schedule expectation: "Hybrid work model requiring 3 days per week onsite." But the user might consider location (Anchorage, AK) as to be excluded, but the work schedule (3 days in-office) could be part of the expectations. However, the user's instruction says to exclude location, but the work schedule is a separate aspect. Since the user wants to exclude location, Anchorage, AK is excluded. The "Hybrid 3 days a week onsite required" is a work requirement, so perhaps that is part of expectations. But the user's instruction says "exclude location" and "hybrid 3 days a week onsite required" includes location details. So maybe the part after the location is the work schedule, but since the location is Anchorage, AK, we cannot include that. Therefore, maybe just state "Hybrid work model with required onsite days as needed" without specifying the location. However, the original job description might have that, but since location is to be excluded, perhaps we can't say Anchorage. So the Expectations would need to include "Hybrid work model requiring three days per week onsite" but since the location is excluded, just say "Hybrid work model requiring three days per week onsite" without mentioning Anchorage, AK.
But the user said to exclude location. So Anchorage, AK is to be excluded, but the requirement to be onsite three days a week is part of the expectations. So in the Expectations section, include the hybrid work requirement without the location.
Now, the other part of the job description is "Contract Length: 4 month contract" and "Work permits accepted..." which are considered fluff and should be excluded. So the Expectations section would include the hybrid work requirement.
Putting it all together:
Role Summary: Supports operational and technical projects by clarifying business needs, improving processes, and ensuring project delivery through stakeholder collaboration and requirement documentation.
Expectations: Hybrid work model requiring three days per week onsite. Contract duration and work permit details excluded as per user instructions.
Key Responsibilities: 1. Collaborate with business units... etc., as bullet points.
Required Skills: As listed.
Required Education & Certifications: None specified in original job description.
Wait, but the user wants Required Education & Certifications even if it's not mentioned? The original job description didn't specify education or certifications, so under "Required Education & Certifications," we can note that it's not specified. But the user wants the section to be included. So perhaps write "Not specified" in the output. But the user might expect if there's a standard for Business Analyst. However, since the original didn't mention it, it's best to state "Not specified