ORG DEVELOPMENT REP 2
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop
5. Preserve ALL substantive information
4. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions)
5. Include section ONLY when posting has real specific content - never emit heading with filler/placeholder text
6. Never create Pay/Schedule/Benefits sections unless posting actually states them
7. Prefer few substantive sections over many thin ones
8. Output ONLY HTML fragment - no /, no markdown code fences
Let me analyze the posting:
- Req ID: 50392, Team: O44 LDR PROF & ORG DEV, Entity: Newport News Shipbuilding - this is metadata, fold into a short
or drop
- US Citizenship Required: Yes
- Full-Time Shift: 1st
- Relocation: No relocation assistance available
- Virtual/Telework: Yes - Occasional or hybrid telework available
- Travel Requirements: Yes, 10%-25% of the time
- Clearance Required: No - Clearance Not Required to Start
- Salary Range: $72,000.00 to $91,000.00 with note about final compensation
Then there's "Meet HII's Newport News Shipbuilding" - this is company description, could be "About the company" or similar
"The Role" section describes responsibilities - this is "About the role" or "Responsibilities"
"Must Have" - this is Requirements/Qualifications
"Nice to Have" - this is Preferred Qualifications or Skills
"Why HII" - company benefits and culture - this is Benefits section
"We offer comprehensive benefits including:" - lists specific benefits
Then there's EEO statement, accommodation info - this is boilerplate to remove
So sections I should include:
1. About the role (or Responsibilities) - from "The Role" paragraph
2. Requirements (or Qualifications) - from "Must Have"
3. Preferred Qualifications (or Skills) - from "Nice to Have"
4. Benefits - from "Why HII" and benefits list
5. Pay - salary range is given
6. Schedule/Work Arrangement - shift, telework, travel, relocation info
I should fold the metadata (Req ID, Team, Entity, Citizenship, Clearance) into a short
at the top or in a "Position Details" section.
Let me structure:
- Opening
with key metadata: Req ID, Team, Entity, Citizenship, Shift, Relocation, Telework, Travel, Clearance
- About the role (h3) - the paragraph under "The Role"
- Responsibilities (h3) - could combine with above or separate. The "The Role" paragraph lists duties, so maybe "Responsibilities" as h3 with ul
- Requirements (h3) - "Must Have" as ul
- Preferred Qualifications (h3) - "Nice to Have" as ul
- Benefits (h3) - from "Why HII" and benefits list
- Pay (h3) - salary range
- Schedule (h3) - shift, telework, travel
Wait, the rules say use specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use these standard headings.
"The Role" content is responsibilities, so I'll use "Responsibilities" heading.
"Must Have" is Requirements.
"Nice to Have" could be "Qualifications" or "Skills". Since it's preferred qualifications, I'll use "Qualifications" for Must Have and "Preferred Qualifications" for Nice to Have? But the rule says headings like "Qualifications" and "Skills". I think "Requirements" for must-have, "Preferred Qualifications" for nice-to-have.
But the rule lists: "Requirements, Qualifications, Skills" as possible headings. I'll use "Requirements" for must-have, and "Preferred Qualifications" for nice-to-have (though not in the list, but it's a real section). Or maybe "Qualifications" for must-have and "Skills" for nice-to-have? The nice-to-have includes experience and skills.
I think:
- Requirements (h3) - Must Have
- Preferred Qualifications (h3) - Nice to Have
But the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should stick to those examples. "Preferred Qualifications" isn't listed but it's a real section. I could use "Qualifications" for must-have and "Skills" for nice-to-have? But nice-to-have includes more than skills.
Actually, looking at the posting: "Must Have" is education/experience requirements. "Nice to Have" is experience and skills. So:
- Requirements (h3) for Must Have
- Qualifications (h3) for Nice to Have? Or Skills?
I'll use "Requirements" for Must Have and "Preferred Qualifications" for Nice to Have, even though not in the example list, because it's substantive content. The rule says "e.g." so it's not exhaustive.
But to be safe, I'll use "Requirements" and "Qualifications" as the two headings.
Now, for the metadata: I'll create a short
at the beginning with the key details.
Let me draft the HTML:
Req ID: 50392 | Team: O44 LDR PROF & ORG DEV | Entity: Newport News Shipbuilding | US Citizenship Required: Yes | Full-Time Shift: 1st | Relocation: No relocation assistance available | Virtual/Telework: Occasional or hybrid telework available | Travel: 10%–25% | Clearance: Not required to start
About the role
Designs and implements development training programs to enhance the effectiveness of managers and teams to increase organization productivity and customer satisfaction. Assesses critical business issues and designs organization development and strategic plans to enhance company performance. Facilitates design and implementation of reengineering and/or reorganization efforts. Advises on team design and performance. Provides development, coaching and training managers on leadership skills.
Responsibilities
- Design and implement development training programs to enhance manager and team effectiveness
- Assess critical business issues and design organization development and strategic plans
- Facilitate design and implementation of reengineering and/or reorganization efforts
- Advise on team design and performance
- Provide development, coaching, and training to managers on leadership skills
Wait, the "About the role" and "Responsibilities" would be duplicative. The posting has "The Role" section with a paragraph that describes the role and lists duties. I should either have "About the role" with the prose paragraph, or "Responsibilities" with a list. Not both. The rule says "Prefer a few substantive sections over many thin ones." So I'll combine: use "Responsibilities" with a list extracted from the paragraph.
But the paragraph is prose. I could keep it as prose under "About the role" and not have a separate Responsibilities. Or make Responsibilities with bullet points. Since the rule says use - for any list of duties, and the paragraph lists duties, I'll convert to a list under "Responsibilities".
Similarly, "Must Have" is a list of requirements - use
- under "Requirements".
"Nice to Have" is a list - use
- under "Preferred Qualifications" or "Qualifications".
Benefits: "Why HII" has a paragraph and then a list of benefits. I'll include both: a prose paragraph under "Benefits" and then a list.
Pay: salary range given - include "Pay" section.
Schedule: shift, telework, travel - include "Schedule" section.
Now, the company description "Meet HII's Newport News Shipbuilding" - this is about the company. Could be "About the company" but not in the example headings. The rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". No "About the company". But it's substantive content. I could include it as a prose paragraph at the top under a heading "About the company" or fold into Benefits? The rule says "include a section ONLY when the posting has real, specific content for it". It does have content. But the example headings don't include it. However, the rule says "e.g." so it's not exhaustive. I think I should include it as "About the company" or "Company overview". But to stick to the examples, maybe omit or fold into a brief intro. The user said "Preserve ALL substantive information". So I should include it. I'll add a heading "About the company" even though not in examples, because it's real content.
But the rule: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not an exhaustive list. So I can use other headings if needed.
I'll include "About the company" for the Meet HII section.
Now, the EEO and accommodation info is boilerplate - remove.
Also, the "Do You Need Assistance?" section - remove.
Now, let me write the HTML.
I need to be careful: no markdown code fences, just HTML fragment.
Let me structure:
Req ID: 50392 | Team: O44 LDR PROF & ORG DEV | Entity: Newport News Shipbuilding | US Citizenship Required: Yes | Full-Time Shift: 1st | Relocation: No relocation assistance available | Virtual/Telework: Occasional or hybrid telework available | Travel: 10%–25% | Clearance: Not required to start
About the company
With more than 25,000 employees – including third-, fourth- and even fifth-generation shipbuilders – HII's Newport News Shipbuilding (NNS) division is the largest industrial employer in Virginia. We're the sole designer, builder and refueler of U.S. Navy nuclear aircraft carriers and one of two providers of U.S. Navy nuclear submarines. Our diverse and innovative team of professionals ranges from skilled trades to project managers, engineers and software developers to solution architects, technical subject matter experts, and system users. We collaborate together at the forefront of technology, manufacturing, and integration of the most powerful and survivable naval ships in the world.
Responsibilities
- Design and implement development training programs to enhance the effectiveness of managers and teams to increase organization productivity and customer satisfaction
- Assess critical business issues and design organization development and strategic plans to enhance company performance
- Facilitate design and implementation of reengineering and/or reorganization efforts
- Advise on team design and performance
- Provide development, coaching, and training to managers on leadership skills
Requirements
- Bachelor's Degree and 3 years of relevant exempt experience; or Master's Degree and 1 year of relevant professional experience
- One of the following may be used as equivalent to
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings - fold into short
or drop 5. Preserve ALL substantive information 4. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) 5. Include section ONLY when posting has real specific content - never emit heading with filler/placeholder text 6. Never create Pay/Schedule/Benefits sections unless posting actually states them 7. Prefer few substantive sections over many thin ones 8. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the posting: - Req ID: 50392, Team: O44 LDR PROF & ORG DEV, Entity: Newport News Shipbuilding - this is metadata, fold into a short
or drop - US Citizenship Required: Yes - Full-Time Shift: 1st - Relocation: No relocation assistance available - Virtual/Telework: Yes - Occasional or hybrid telework available - Travel Requirements: Yes, 10%-25% of the time - Clearance Required: No - Clearance Not Required to Start - Salary Range: $72,000.00 to $91,000.00 with note about final compensation Then there's "Meet HII's Newport News Shipbuilding" - this is company description, could be "About the company" or similar "The Role" section describes responsibilities - this is "About the role" or "Responsibilities" "Must Have" - this is Requirements/Qualifications "Nice to Have" - this is Preferred Qualifications or Skills "Why HII" - company benefits and culture - this is Benefits section "We offer comprehensive benefits including:" - lists specific benefits Then there's EEO statement, accommodation info - this is boilerplate to remove So sections I should include: 1. About the role (or Responsibilities) - from "The Role" paragraph 2. Requirements (or Qualifications) - from "Must Have" 3. Preferred Qualifications (or Skills) - from "Nice to Have" 4. Benefits - from "Why HII" and benefits list 5. Pay - salary range is given 6. Schedule/Work Arrangement - shift, telework, travel, relocation info I should fold the metadata (Req ID, Team, Entity, Citizenship, Clearance) into a short
at the top or in a "Position Details" section. Let me structure: - Opening
with key metadata: Req ID, Team, Entity, Citizenship, Shift, Relocation, Telework, Travel, Clearance - About the role (h3) - the paragraph under "The Role" - Responsibilities (h3) - could combine with above or separate. The "The Role" paragraph lists duties, so maybe "Responsibilities" as h3 with ul - Requirements (h3) - "Must Have" as ul - Preferred Qualifications (h3) - "Nice to Have" as ul - Benefits (h3) - from "Why HII" and benefits list - Pay (h3) - salary range - Schedule (h3) - shift, telework, travel Wait, the rules say use specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use these standard headings. "The Role" content is responsibilities, so I'll use "Responsibilities" heading. "Must Have" is Requirements. "Nice to Have" could be "Qualifications" or "Skills". Since it's preferred qualifications, I'll use "Qualifications" for Must Have and "Preferred Qualifications" for Nice to Have? But the rule says headings like "Qualifications" and "Skills". I think "Requirements" for must-have, "Preferred Qualifications" for nice-to-have. But the rule lists: "Requirements, Qualifications, Skills" as possible headings. I'll use "Requirements" for must-have, and "Preferred Qualifications" for nice-to-have (though not in the list, but it's a real section). Or maybe "Qualifications" for must-have and "Skills" for nice-to-have? The nice-to-have includes experience and skills. I think: - Requirements (h3) - Must Have - Preferred Qualifications (h3) - Nice to Have But the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should stick to those examples. "Preferred Qualifications" isn't listed but it's a real section. I could use "Qualifications" for must-have and "Skills" for nice-to-have? But nice-to-have includes more than skills. Actually, looking at the posting: "Must Have" is education/experience requirements. "Nice to Have" is experience and skills. So: - Requirements (h3) for Must Have - Qualifications (h3) for Nice to Have? Or Skills? I'll use "Requirements" for Must Have and "Preferred Qualifications" for Nice to Have, even though not in the example list, because it's substantive content. The rule says "e.g." so it's not exhaustive. But to be safe, I'll use "Requirements" and "Qualifications" as the two headings. Now, for the metadata: I'll create a short
at the beginning with the key details. Let me draft the HTML:
Req ID: 50392 | Team: O44 LDR PROF & ORG DEV | Entity: Newport News Shipbuilding | US Citizenship Required: Yes | Full-Time Shift: 1st | Relocation: No relocation assistance available | Virtual/Telework: Occasional or hybrid telework available | Travel: 10%–25% | Clearance: Not required to start
About the role
Designs and implements development training programs to enhance the effectiveness of managers and teams to increase organization productivity and customer satisfaction. Assesses critical business issues and designs organization development and strategic plans to enhance company performance. Facilitates design and implementation of reengineering and/or reorganization efforts. Advises on team design and performance. Provides development, coaching and training managers on leadership skills.
Responsibilities
- Design and implement development training programs to enhance manager and team effectiveness
- Assess critical business issues and design organization development and strategic plans
- Facilitate design and implementation of reengineering and/or reorganization efforts
- Advise on team design and performance
- Provide development, coaching, and training to managers on leadership skills
- for any list of duties, and the paragraph lists duties, I'll convert to a list under "Responsibilities".
Similarly, "Must Have" is a list of requirements - use
- under "Requirements".
"Nice to Have" is a list - use
- under "Preferred Qualifications" or "Qualifications".
Benefits: "Why HII" has a paragraph and then a list of benefits. I'll include both: a prose paragraph under "Benefits" and then a list.
Pay: salary range given - include "Pay" section.
Schedule: shift, telework, travel - include "Schedule" section.
Now, the company description "Meet HII's Newport News Shipbuilding" - this is about the company. Could be "About the company" but not in the example headings. The rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". No "About the company". But it's substantive content. I could include it as a prose paragraph at the top under a heading "About the company" or fold into Benefits? The rule says "include a section ONLY when the posting has real, specific content for it". It does have content. But the example headings don't include it. However, the rule says "e.g." so it's not exhaustive. I think I should include it as "About the company" or "Company overview". But to stick to the examples, maybe omit or fold into a brief intro. The user said "Preserve ALL substantive information". So I should include it. I'll add a heading "About the company" even though not in examples, because it's real content.
But the rule: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not an exhaustive list. So I can use other headings if needed. I'll include "About the company" for the Meet HII section. Now, the EEO and accommodation info is boilerplate - remove. Also, the "Do You Need Assistance?" section - remove. Now, let me write the HTML. I need to be careful: no markdown code fences, just HTML fragment. Let me structure:
Req ID: 50392 | Team: O44 LDR PROF & ORG DEV | Entity: Newport News Shipbuilding | US Citizenship Required: Yes | Full-Time Shift: 1st | Relocation: No relocation assistance available | Virtual/Telework: Occasional or hybrid telework available | Travel: 10%–25% | Clearance: Not required to start
About the company
With more than 25,000 employees – including third-, fourth- and even fifth-generation shipbuilders – HII's Newport News Shipbuilding (NNS) division is the largest industrial employer in Virginia. We're the sole designer, builder and refueler of U.S. Navy nuclear aircraft carriers and one of two providers of U.S. Navy nuclear submarines. Our diverse and innovative team of professionals ranges from skilled trades to project managers, engineers and software developers to solution architects, technical subject matter experts, and system users. We collaborate together at the forefront of technology, manufacturing, and integration of the most powerful and survivable naval ships in the world.
Responsibilities
- Design and implement development training programs to enhance the effectiveness of managers and teams to increase organization productivity and customer satisfaction
- Assess critical business issues and design organization development and strategic plans to enhance company performance
- Facilitate design and implementation of reengineering and/or reorganization efforts
- Advise on team design and performance
- Provide development, coaching, and training to managers on leadership skills
Requirements
- Bachelor's Degree and 3 years of relevant exempt experience; or Master's Degree and 1 year of relevant professional experience
- One of the following may be used as equivalent to
- under "Preferred Qualifications" or "Qualifications".
Benefits: "Why HII" has a paragraph and then a list of benefits. I'll include both: a prose paragraph under "Benefits" and then a list.
Pay: salary range given - include "Pay" section.
Schedule: shift, telework, travel - include "Schedule" section.
Now, the company description "Meet HII's Newport News Shipbuilding" - this is about the company. Could be "About the company" but not in the example headings. The rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". No "About the company". But it's substantive content. I could include it as a prose paragraph at the top under a heading "About the company" or fold into Benefits? The rule says "include a section ONLY when the posting has real, specific content for it". It does have content. But the example headings don't include it. However, the rule says "e.g." so it's not exhaustive. I think I should include it as "About the company" or "Company overview". But to stick to the examples, maybe omit or fold into a brief intro. The user said "Preserve ALL substantive information". So I should include it. I'll add a heading "About the company" even though not in examples, because it's real content.
But the rule: "use
- under "Requirements".
"Nice to Have" is a list - use