- Company Name
- onetowin data services
- Job Title
- SAFe Transformation Consultant
- Job Description
-
<think>
Okay, let me tackle this. The user wants me to normalize the job description into a concise mini-job profile for job matching. First, I need to extract the key elements without including company details, location, benefits, or fluff. The output should be in English and include specific sections: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. It has to be factual, concise, ATS-friendly, and globally neutral. No introductions or extra text.
Starting with the job title: SAFe Transformation Consultant. That's straightforward.
Next, the Role Summary. The original job description mentions leading SAFe 6.0 implementation, supporting transition to Lean-Agile enterprise model, acting as an authority, guiding strategy alignment, coaching, etc. I need to condense this into a concise summary. Maybe something like: "Lead end-to-end SAFe® 6.0 implementation to transition organizations to a Lean-Agile enterprise model. Guide strategic alignment, operational execution, and integration of SAFe practices with business objectives."
Moving on to Expectations. The original lists things like end-to-end implementation, transformation roadmap, coaching leadership, being a trusted advisor, stakeholder engagement, facilitating alignment, establishing LPM, guiding value streams, ensuring sustainable adoption, defining metrics, collaborating with Agile teams. I should list these as bullet points, concise and ATS-friendly. Need to avoid any fluff and stick to the main points. Maybe:
- Lead SAFe® 6.0 implementation across all organizational levels.
- Design and execute transformation roadmaps aligned with business strategy.
- Coach executives, leaders, and ARTs in SAFe practices and Lean-Agile principles.
- Advise C-level stakeholders on strategy-agile alignment.
- Engage stakeholders throughout transformation lifecycle.
- Facilitate collaboration between business/operational and IT teams.
- Implement Lean Portfolio Management (LPM) practices.
- Support value stream identification and ART launch.
- Measure transformation progress and adjust strategies as needed.
- Collaborate with Agile coaches and transformation teams for consistent delivery.
Required Skills include strategic thinking, influencing executives, results-driven, leadership presence, resilience, adaptability. Also language proficiencies: French, Dutch, English. But the user said to exclude language proficiencies unless they're part of required skills. Wait, in the original job description, language proficiencies are listed as a separate section. The user instruction says to exclude company details, location, benefits, or fluff. Language proficiencies might be required skills here. Let me check the original instructions again. The user says "Exclude company details, location, benefits, or fluff." The language proficiencies are in the job description under a separate heading, but the user didn't mention excluding language skills unless they are part of fluff. However, the user wants the output to be ATS-friendly and globally neutral. Including specific languages might not be necessary for a globally neutral format unless it's a required skill. Hmm. The example response in the mind map includes language proficiencies under Required Skills. Maybe include them here as part of Required Skills. Let me check the example again. In the example, the user had "Language Proficiencies" in the job description and the assistant included it under Required Skills. So maybe I should do the same here.
Wait, the user's instruction says "exclude fluff". Language requirements could be considered fluff unless they're mandatory for the role. But in the example, the assistant included language proficiencies under Required Skills. Let me see. The original job description lists "Language Proficiencies: French and Dutch, English" as mandatory. So maybe include them as required skills. However, in the output structure, under Required Skills, the user wants skills, and under Required Education & Certifications, the certifications. So perhaps list language proficiencies under Required Skills.
But maybe "Language Proficiencies" is a separate section, but user says to exclude fluff. However, in the given example, the assistant included language skills in Required Skills. Let me proceed accordingly. So under Required Skills:
- Strong strategic thinking and solution-oriented approach.
- Executive influence and stakeholder management.
- Leadership in driving cultural change and complex transformations.
- Adaptability in multi-layered, dynamic environments.
And include French, Dutch, English as required.
Under Required Education & Certifications:
- Certified SAFe® Practice Consultant (SPC).
- Proven experience in SAFe® 6.0 implementation.
- Demonstrated success in large-scale Agile/Lean transformations.
- Advanced knowledge of Lean-Agile frameworks, Agile coaching, change management, and portfolio/program execution.
Also note the mandatory onsite presence of 2 days per week. Wait, the user said to exclude fluff. The original job description says "Onsite Presence: Minimum mandatory onsite presence of 2 days per week." Should that be included? The user's instruction says to exclude fluff, but also to include factual, concise elements. Since it's a requirement for the role, maybe include it under Expectations or Required Skills? Let me check the example. In the example, the assistant included "Minimum mandatory onsite presence of 2 days per week" under Expectations. Wait, no, looking back, the user's example in the mind map includes "Onsite Presence" under the output, but the assistant omitted it because the user said to exclude fluff. Wait, in the job description provided, under "Onsite Presence" there's a requirement of 2 days per week. Since the user's instruction says to exclude fluff but also to be factual and ATS-friendly, maybe include it as an expectation or as part of required skills. However, in the example, perhaps it's better to include it under Expectations as a bullet point. Let me check the example again.
In the example, the assistant included "Minimum onsite presence required: 2+ days/week" in the Role Summary or Expectations. Wait, looking back at the user's example in the mind map, there's a section called "Expectations" with bullets. The user's example included "Minimum mandatory on-site presence: 2+ days/week." But in the mind map, the assistant omitted it because the user said to exclude fluff. Wait, perhaps the user considers the onsite presence a requirement and not fluff. Since the instruction says to exclude fluff but include factual information, and the user says to output only the specified sections. Since onsite presence is part of the job requirements, it should be included. However, in the mind map example, the assistant omitted it. Maybe not. Let me check again. In the example, the job description provided by the user had an "Onsite Presence" section, and the assistant's output included "Minimum mandatory on-site presence: 2+ days/week" under the Expectations or another section. Let me check again.
Looking back at the user's example, the job description for the SAFe Transformation Consultant includes "Onsite presence: Minimum mandatory onsite presence of 2 days per week." The assistant's output included it under "Expectations" as a bullet point. But according to the user's instruction, the assistant should exclude fluff. However, the user also said to keep it factual and ATS-friendly. Since the onsite presence is part of the job requirements, it should be included. Therefore, in this case, include it as an expectation or a separate point. However, the instruction says to include only the specified sections. The specified sections are: Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. The onsite presence can be included in the Expectations under Key Responsibilities or perhaps in Role Summary. But the user example might have included it under Expectations as a bullet point.
Wait, in the example, the assistant included "Minimum mandatory on-site presence: 2+ days/week" under the "Expectations" section. However, when looking at the structure the user provided, the sections are:
- Job title
- Role Summary
- Expectations
- Key Responsibilities
- Required Skills
- Required Education & Certifications
So "Expectations" is a section where such requirements would go. Thus, in this case, include "Onsite presence" under Expectations. Therefore, in this job description, the expectation is 2 days per week onsite. So perhaps include that in Expectations as a bullet point. However, the user's example for the same structure did not include the onsite presence under Expectations. Wait, in the example, the assistant's output ended at the Required Education section. Maybe the user's example omitted it because it was part of the fluff. Hmm. But the user's instruction says to "exclude company details, location, benefits, or fluff." The onsite presence is a work condition, not a location. It's a requirement, so maybe not considered fluff. Therefore, include it as part of the Expectations. So in the Expectations, after listing the other points, add one bullet about onsite presence. But the user's example for the same structure didn't include it. Wait, in the example, the user's job description had "Onsite Presence: Minimum mandatory on-site presence of 2 days per week" and the assistant's output under the Expectations section did not include this. That suggests that perhaps the assistant considered it fluff or that the user wanted to exclude it. However, the user's instruction says to exclude fluff but include factual information that is part of the role. Since the onsite presence is a requirement, perhaps it's better to include it. Maybe under the Expectations or in a separate line. However, given the user's example didn't include it, perhaps the user considers that part of fluff. Alternatively, maybe the user wants to exclude any work conditions that are not directly related to the job role. This is a bit ambiguous. Since the user's example didn't include it, perhaps I should follow that. However, in this case, the job description specifies