Senior Workforce / Organizational Design SME

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. First, we need to identify sections: The posting includes: - Intro: "Steampunk is seeking a Senior Workforce / Organizational Design SME to lead development of an enterprise IT workforce modernization strategy for a large federal client, applying a zero-based design approach to position management, job architecture, and career pathing." - Then "Contributions" bullet list (list of duties/responsibilities). That's responsibilities. - Then "Required Qualifications" bullet list. - Then "Preferred Experience" bullet list. - Then "About Steampunk" paragraph. - Then EEO boilerplate etc which we need to remove. - Also mention "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week" - that could be part of Requirements or maybe Schedule? It's location and onsite requirement. Could be considered under Requirements (location) or maybe Schedule (2 days a week onsite). The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. There's mention of schedule: "willing to go on client site at least 2 days a week". That's a schedule expectation (onsite days). So we could include a Schedule section with that detail. - Benefits: Not mentioned. Pay: Not mentioned. So we omit those. - Skills: Could be derived from qualifications but we have Required Qualifications and Preferred Experience. Could combine into Qualifications section. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have: - About the role: maybe a brief description of the role (the intro). Could be "About the role". That seems appropriate. - Responsibilities: the "Contributions" list. - Requirements: maybe the required qualifications (including security clearance, degree, experience, etc). Could be "Requirements". - Qualifications: maybe the preferred experience? Or we could combine required and preferred into Qualifications. But we have both Required Qualifications and Preferred Experience. Could make two sections: Requirements (required) and Qualifications (preferred). Or we could have Requirements for required, and Skills for preferred? The instruction says we can use Skills section. But we need to preserve all substantive info. Let's map: - About the role: intro paragraph. - Responsibilities: the contributions bullet list. - Requirements: Required Qualifications bullet list. - Qualifications: Preferred Experience bullet list. - Schedule: "Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week". Could be location and schedule. Could be under Schedule (onsite days) and maybe location in Requirements? But we already used Requirements for qualifications. Could add location as part of Requirements? But we already used Requirements for required qualifications. Could add a separate section for Location? Not in allowed headings. Could fold location into Schedule or Requirements. Since schedule includes onsite days, we can include location there: "Located in Baltimore, MD metro area; required to be on client site at least 2 days per week." - Benefits: none. - Pay: none. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Check if any other content: "Build workforce personas and career journey maps..." etc are responsibilities. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat the job title as a heading. The job title is "Senior Workforce / Organizational Design SME". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: EEO, E-Verify, equal opportunity, etc. Also remove "About Steampunk" maybe? Actually "About Steampunk" is substantive about the company; we could include that as a section maybe "About the company". But allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About the company. However we could incorporate that into About the role? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. But we could also add other headings if needed? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be implying those are the allowed headings. Safer to stick to those. Thus we need to fit "About Steampunk" somewhere. Could be part of About the role? But About the role is about the role, not company. However we could treat About the role as including company description. Or we could omit it? But we must preserve ALL substantive information. So we need to include the About Steampunk paragraph somewhere. Could we put it under About the role as a prose paragraph? That would be mixing role and company but still substantive. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding extra info in About the role. So we can include the About Steampunk paragraph in About the role section. Thus About the role section will contain: introductory sentence about the role plus the About Steampunk paragraph. Now Responsibilities: list of contributions. Requirements: Required Qualifications bullet list. Qualifications: Preferred Experience bullet list. Schedule: location and onsite expectation. Now we need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now produce HTML. Let's extract the content. Intro: "Steampunk is seeking a Senior Workforce / Organizational Design SME to lead development of an enterprise IT workforce modernization strategy for a large federal client, applying a zero-based design approach to position management, job architecture, and career pathing." About Steampunk paragraph: "Steampunk is a Change Agent in the Federal contracting industry, bringing new thinking to clients in the Homeland, Federal Civilian, Health and DoD sectors. Through our Human-Centered delivery methodology, we are fundamentally changing the expectations our Federal clients have for true shared accountability in solving their toughest mission challenges. As an employee owned company, we focus on investing in our employees to enable them to do the greatest work of their careers – and rewarding them for outstanding contributions to our growth. If you want to learn more about our story, visit http://www.steampunk.com ." We should remove the EEO line after that. Also remove "We are an equal opportunity employer..." and "Steampunk participates in the E-Verify program." Now Responsibilities (Contributions) list: - Deliver an Enterprise IT Workforce Modernization Strategy, covering current-state assessment, target operating model, and a prioritized implementation roadmap - Apply a zero-based design approach: question existing position-management processes and identify work to eliminate, simplify, standardize, consolidate, automate, or reassign before proposing any technology change - Build workforce personas and career journey maps to identify where staff stall or cannot advance, shaping visible technical, product, program, and leadership career paths - Establish a common taxonomy for IT job families, titles, occupational series, career levels, and competencies, and build a governed library of standardized, OPM-mapped position descriptions - Develop a crosswalk identifying comparable work, inconsistencies, and duplication across titles/series/grades, with recommended dispositions - Complete a workforce capability and skills-gap assessment - Design and deliver an AI-enabled future-state position management workflow with appropriate human review, controls, and data protections, usability-tested with HR practitioners and hiring managers - Build and maintain a succession-planning registry covering 100% of identified mission-critical IT roles - Validate all framework elements in co-design workshops with stakeholders, preserving their statutory authority Now Required Qualifications: - Ability to obtain and maintain a U.S. government security clearance - Bachelor's degree - 10+ years of federal workforce planning, HR strategy, or organizational design experience - Demonstrated experience with OPM position classification standards and position description development - Experience building job family taxonomies and competency frameworks at enterprise scale - Experience applying zero-based or process-elimination design approaches to organizational or position-management redesign - Experience designing or evaluating AI-enabled HR/workforce management tools or workflows, including human-review and data-protection considerations - Strong stakeholder management skills, including working directly with HR/classification officials - Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week Wait the last bullet about location is actually part of Required Qualifications? In the posting it's under Required Qualifications? Let's check: The posting shows: "Required Qualifications Ability to obtain and maintain a U.S. government security clearance Bachelor's degree 10+ years of federal workforce planning, HR strategy, or organizational design experience Demonstrated experience with OPM position classification standards and position description development Experience building job family taxonomies and competency frameworks at enterprise scale Experience applying zero-based or process-elimination design approaches to organizational or position-management redesign Experience designing or evaluating AI-enabled HR/workforce management tools or workflows, including human-review and data-protection considerations Strong stakeholder management skills, including working directly with HR/classification officials Local to Baltimore, MD metro area and willing to go on client site at least 2 days a week" Yes, location is included in Required Qualifications. Then after that there is "Preferred Experience with succession planning and mission-critical role risk assessment Experience covering IT, cybersecurity, data, or digital-services position types specifically" Thus we should keep location in Required Qualifications. Then Schedule section may be redundant. But we already have location in Required Qualifications; we could still have a Schedule section for the onsite days. However the location bullet includes both location and onsite days. If we move location to Required Qualifications, we could still have Schedule for onsite days only. But we might duplicate. Better to keep location in Required Qualifications and not create a separate Schedule section unless we have additional schedule info beyond that. The posting does not have separate schedule info; the onsite days is part of that bullet. So we could omit Schedule section. However the instruction says include Schedule section only if posting actually states them. It does state "willing to go on client site at least 2 days a week". That's a schedule expectation. So we could include Schedule section with that detail, but we would need to avoid duplicating the location bullet. We could split the bullet: location part goes to Requirements, schedule part goes to Schedule. That's acceptable as we are not duplicating; we are dividing the content. Thus Required Qualifications will include all except the schedule part. We'll extract "Local to Baltimore, MD metro area" as location requirement. The schedule part "willing to go on client site at least 2 days a week" goes to Schedule. Now Preferred Experience: - Experience with succession planning and mission-critical role risk assessment - Experience covering IT, cybersecurity, data, or digital-services position types specifically Now we need to ensure we preserve all substantive info. The About Steampunk paragraph includes a URL; we should keep it. Now we need to format. HTML:

  About the role

  Steampunk is seeking a Senior Workforce / Organizational Design SME to lead development of an enterprise IT workforce modernization strategy for a large federal client, applying a zero-based design approach to position management, job architecture, and career pathing.

  Steampunk is a Change Agent in the Federal contracting industry, bringing new thinking to clients in the Homeland, Federal Civil