Deputy Project Lead
KBR Careers · Greenbelt, MD · 1 mo ago
Project Management$163k–$244k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description: "Title Deputy Project Lead Belong. Connect. Grow. with KBR! Around here, we define the future...". We need to not repeat job title as heading. Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only when posting has real specific content.
We have content: description (intro) maybe as About the role. Then Responsibilities list. Then Minimum Requirements (qualifications). Then Basic Compensation (Pay range). Additional Compensation (bonus etc). Benefits description. Also mention "KBR Benefits" with list.
We need to avoid boilerplate: EEO, equal opportunity, etc. Remove duplicated lines. Also remove navigation, cookie, legal, application instructions. There's no explicit application instructions besides maybe "Click here to learn more: KBR Benefits". That's a link; maybe we keep as part of Benefits? It's a link; but we can keep as part of Benefits paragraph? The instruction: remove application instructions. "Click here to learn more: KBR Benefits" is not an application instruction but a link to benefits; maybe keep as part of Benefits? It's not essential but could be considered navigation. Safer to drop that line.
We need to preserve all substantive info. So we need to include the description paragraph(s) about KBR mission etc. That's about the role/company.
We need to format:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only when posting has real specific content.
We have content: description (intro) maybe as About the role. Then Responsibilities list. Then Minimum Requirements (qualifications). Then Basic Compensation (Pay range). Additional Compensation (bonus etc). Benefits description. Also mention "KBR Benefits" with list.
We need to avoid boilerplate: EEO, equal opportunity, etc. Remove duplicated lines. Also remove navigation, cookie, legal, application instructions. There's no explicit application instructions besides maybe "Click here to learn more: KBR Benefits". That's a link; maybe we keep as part of Benefits? It's a link; but we can keep as part of Benefits paragraph? The instruction: remove application instructions. "Click here to learn more: KBR Benefits" is not an application instruction but a link to benefits; maybe keep as part of Benefits? It's not essential but could be considered navigation. Safer to drop that line.
We need to preserve all substantive info. So we need to include the description paragraph(s) about KBR mission etc. That's about the role/company.
We need to format:
About the role
... (intro text)
Then Responsibilities: list items. Then Requirements: maybe combine Minimum Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills. We have Minimum Requirements (Bachelor's degree, 15 years experience, ability to work with diverse teams). Could put underRequirements
with- .
We also have "Basic Compensation" and "Additional Compensation". Pay range is specific. So we need a Pay section. According to rules: include Pay section only if posting actually states them. Yes, we have pay range. So
- ... ...
- ... ...
- ... ...
Pay
withcontaining the range and note. Additional compensation: maybe could be part of Pay or separate Benefits? The instruction: prefer a few substantive sections over many thin ones. Could combine Pay and Additional compensation into Pay section? But they are distinct: base pay range and additional compensation (bonuses, etc). Could still be under Pay heading with both. Benefits: we have KBR Benefits list. So
Benefits
with- .
Schedule: not mentioned, so omit.
We must not repeat job title as heading. So no heading for Deputy Project Lead.
We must not put Job ID/requisition numbers as headings; we have R2130048 at end; drop it.
We must not include boilerplate like EEO, equal opportunity, etc. Remove those paragraphs.
We must not include duplicated lines: there are duplicate paragraphs about Belong, Connect and Grow etc. We need to keep only one copy.
Let's extract substantive content:
Intro: "Title Deputy Project Lead Belong. Connect. Grow. with KBR! Around here, we define the future. We are a company of innovators, thinkers, creators, explorers, volunteers, and dreamers. But we all share one goal: to improve the world responsibly and safely. KBR is seeking a Deputy Project Lead to support KBR and governments customer at NASA Goddard. The Deputy Project lead will directly work with the Project Lead to oversee the execution of the OMES III (Omnibus Multidiscipline Engineering Service) contract for the LEO (Low Earth Observations) program. Manage task performance, financial and staffing to ensure project milestones."
That's the intro.
Then "Responsibilities" heading followed by list:
- Collaborate with teams including Group leads, Project Lead, Program Managers, Teammates, and customer to ensure project execution.
- Plan, coordinate, and execute task orders to meet the customers objectives, timelines, and requirements.
- Manage and supervise employees, resolve issues, gather technical inputs, and evaluate reports.
- Perform Business activities including proposal evaluations, staffing, and financial analysis.
- Analyze and review budgets, identify resources shortfall and make corrective recommendations.
- Manage and supervise employees, teams, and projects.
- Coordinate and monitor teammates activities.
- Guide and supervise project activities and schedules.
Note there is duplicate "Manage and supervise employees" appears twice; we can keep both but maybe deduplicate? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines are substantive? They are repeated; we could keep both but it's redundant. Might be considered duplicated lines; instruction: remove duplicated lines. So we should deduplicate. So keep one instance of "Manage and supervise employees, resolve issues, gather technical inputs, and evaluate reports." and one instance of "Manage and supervise employees, teams, and projects." They are slightly different; keep both.
Now Minimum Requirements:
- Bachelor’s degree in related field such as Business Administration, Engineering, or Project Management.
- Minimum of 15 years of experience in Systems Engineering, Project management or related fields.
- Ability to work with diverse teams and Stakeholders
Now Basic Compensation: "Jobs on this contract range from $162,800- $244,200 . Pay range is specific to the Greenbelt, MD area. The offered rate will be based on the position, contract affordability, the selected candidate’s working location, knowledge, skills, abilities, experience, and in consideration of internal parity."
Additional Compensation: "KBR may offer bonuses, commissions, or other forms of compensation to certain job titles or levels, per internal policy or contractual designation. Additional compensation may be in the form of sign on bonus, relocation benefits, short-term incentives, long-term incentives, or discretionary payments for exceptional performance."
Benefits: "At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to an ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together. KBR Benefits KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development."
Also there is repeated paragraph about Belong etc earlier; we need to keep only one copy. We have that paragraph earlier in intro? Actually the intro includes "Belong. Connect. Grow. with KBR!" and later there is a paragraph about Belong etc. We'll keep one copy maybe in Benefits section? But the Benefits section already includes a sentence about Belong etc. We could keep that as part of Benefits paragraph. The earlier duplicate about Belong etc appears after Additional Compensation: "At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to an ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together." That's duplicated later in Benefits section. We should keep only one instance. Let's keep it in Benefits section (makes sense). So we will not repeat that paragraph elsewhere.
Thus Benefits section will have that paragraph plus the list of benefits.
Now we need to output HTML fragment only.
Structure:
About the role
...
Responsibilities
Requirements
Pay
...
(include base range and additional compensation details)Benefits
...