Next-Generation Data Platform PM

We need to output HTML fragment with sections only when posting has real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. Need to parse the posting. Let's extract sections: - About the role: The first paragraph(s) describing impact: "What Impact You'll Have ..." includes description of role. Could be "About the role". We'll put that content. - Responsibilities: The bullet list under "What You'll Be Owning". That's a list of duties. So we can put under Responsibilities. - Requirements: The "What You Must Have" list. - Qualifications: maybe combine with Requirements? But we have separate sections: Requirements and Qualifications. Usually Requirements are mandatory, Qualifications are nice-to-have. The posting has "What You Must Have" (mandatory) and "What Would Be Nice To Have" (nice). So we can map: Requirements = mandatory list. Qualifications = nice-to-have list. - Skills: maybe not explicit; but we could include skills from requirements like "Strong written communication", "Working fluency in modern software and cloud delivery", etc. Could be separate Skills section. However we should only create sections if posting has real specific content. There is content about skills: "Strong written communication; able to produce customer-ready deliverables without a rewrite", "Working fluency in modern software and cloud delivery — enough to run a technical discussion, challenge an estimate, and translate between engineers and the customer". Also "Experience working directly with a government PMO". Those could be considered skills. But we already have Requirements and Qualifications covering many. Might be okay to not create Skills if content overlaps. But we could create Skills section for those skill statements not captured elsewhere. However we must not duplicate content. Better to keep Requirements and Qualifications and maybe Skills for things like "Strong written communication", "Working fluency in modern software and cloud delivery". But those are already in Requirements list? Let's see Requirements list items: - Active TS/SCI clearance - Bachelor's degree in engineering, computer science, business, or a related field; equivalent experience considered - 15+ years of relevant experience, including 5+ years managing DoD software, data, or IT programs as a PM, deputy PM, or technical lead - Prior support to CPE ISW / PEO IEW&S, PM IS&A, INSCOM, or other Army intelligence programs - Demonstrated ownership of cost, schedule, staffing, risk, and contract deliverable (CDRL or equivalent) performance on a government contract - Experience working directly with a government PMO and government engineering counterparts - Familiarity with modern DoD software acquisition authorities — Software Acquisition Pathway, Other Transaction Agreements, BAA/Commercial Solutions Opening — not only traditional FAR-based contracting. - Working fluency in modern software and cloud delivery — enough to run a technical discussion, challenge an estimate, and translate between engineers and the customer - Strong written communication; able to produce customer-ready deliverables without a rewrite Thus many skill-like items are already in Requirements. So we may not need separate Skills section. - Benefits: The posting mentions benefits: "GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off." Then later "Why Choose GRVTY" includes list: Robust health plan including medical, dental, and vision; Health Savings Account with company contribution; Annual Paid Time Off and Paid Holidays; Paid Parental Leave; 401k with generous company match; Training and Development Opportunities; Award Programs; Variety of Company Sponsored Events. So we have benefits content. - Pay: The posting includes "The pay range for this is $180,000.00 to $220,000.00." So we have Pay section. - Schedule: No explicit schedule info (like full-time, remote, etc). Not present. So we should not create Schedule section. - About the role: we have description. Now we need to output HTML fragment with headings

and content using

for prose,

• for lists. We must not include boilerplate like EEO statement, application instructions, etc. Remove those. We need to preserve all substantive information. So we need to include all the content from sections: About the role (impact description), Responsibilities (list of duties), Requirements (mandatory list), Qualifications (nice-to-have list), Benefits (list), Pay (range). Possibly also include a short paragraph about "Why Choose GRVTY" as part of Benefits? Actually Benefits section already includes those bullet points. The "Why Choose GRVTY" also includes motivational paragraphs about company mission. That could be considered part of About the role? But we already have About the role describing impact. The "Why Choose GRVTY" is more about company culture; could be considered part of Benefits or maybe a separate section like "About the company". But we only allowed headings from list; we could put that under Benefits? Not ideal. Could we create an "About the role" section that includes both impact and why choose? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role for the initial impact description. The "Why Choose GRVTY" could be considered part of Benefits? Not really. Could be part of About the role as well (company description). But we must not invent sections; we can include additional prose under About the role if relevant. The "Why Choose GRVTY" is about company values, not directly about the role but still substantive. We could include it as a paragraph under About the role after the impact description. That seems okay. We must not include EEO statement, application instructions, etc. Now let's extract content precisely. **About the role** (Impact description): Original: "What Impact You'll Have You will own delivery for GRVTY's scope on a U.S. government customer's next-generation data platform program. This is a hands-on program management role on a fast-moving program with a high rate of enhancements — the person in this seat needs to keep cost, schedule, and contract deliverables under control while staying close enough to the technical work to make decisions in real time. This program delivers flexible, adaptable intelligence analysis capability spanning multiple security domains, echelons, and partner environments. The program provides a consistent analyst experience from Top Secret (TS) through Secret, with globally accessible data and common analytic tools, built on a modern cloud architecture. You are the primary interface to the government PM and the government engineering team, and the connective tissue across GRVTY engineering, data, security, and support staff." We'll put that as a paragraph(s). Could be one

  containing all sentences. **Responsibilities** (What You'll Be Owning): List items: - Serve as the day-to-day point of contact for the customer PM and customer engineering teams; build the working relationships that let issues get resolved before they become problems - Coordinate complex technical situations across multiple stakeholders — cross-domain data flows, integration dependencies, ATO and security accreditation timelines, and competing priorities between government and contractor teams - Manage delivery dependencies where GRVTY's scope interfaces with other contractor teams or an established platform vendor on the program, including data-layer and integration handoffs - Lead and align GRVTY team members across functions and locations, making sure work is sequenced, staffed, and unblocked - Manage cost and schedule performance, including forecasting, variance analysis, and monthly reporting - Own staffing: forecast demand, drive requisitions and clearance processing, and manage onboarding against a moving delivery plan - Identify, track, and mitigate risks and issues; maintain the risk register and drive it in program reviews - Author, review, and deliver contract data deliverables — CDRLs or the award vehicle's equivalent — on time and to spec; maintain the deliverable calendar and quality-control submissions before they go to the government - Run program cadence — sprint and PI ceremonies, technical interchange meetings, program management reviews, and in-progress reviews - Manage scope on a program with frequent enhancement requests: triage incoming work, assess cost and schedule impact, and surface trade-offs to the customer early - Support new work capture, change proposals, and ROM development as the program grows We'll put each as

  . **Requirements** (What You Must Have): List: - Active TS/SCI clearance - Bachelor's degree in engineering, computer science, business, or a related field; equivalent experience considered - 15+ years of relevant experience, including 5+ years managing DoD software, data, or IT programs as a PM, deputy PM, or technical lead - Prior support to CPE ISW / PEO IEW&S, PM IS&A, INSCOM, or other Army intelligence programs - Demonstrated ownership of cost, schedule, staffing, risk, and contract deliverable (CDRL or equivalent) performance on a government contract - Experience working directly with a government PMO and government engineering counterparts - Familiarity with modern DoD software acquisition authorities — Software Acquisition Pathway, Other Transaction Agreements, BAA/Commercial Solutions Opening — not only traditional FAR-based contracting. - Working fluency in modern software and cloud delivery — enough to run a technical discussion, challenge an estimate, and translate between engineers and the customer - Strong written communication; able to produce customer-ready deliverables without a rewrite **Qualifications** (What Would Be Nice To Have): List: - PMP certification; Agile certification (SAFe, CSM, or equivalent) - Familiarity with Army intelligence systems and the Intelligence Warfighting Function - Experience with multi-domain and cross-domain solutions, and with accreditation across TS/SCI and Secret enclaves - Experience with accredited cloud environments (C2E, cARMY, IL5/IL6, JWICS) - Experience operating in a multi-contractor or teaming environment where another vendor holds a significant piece of the technical stack, such as a data platform or integration layer - Earned Value Management (EVM) experience, most relevant if the awarded vehicle carries formal EVMS reporting requirements - Proficiency with Jira, Confluence, and standard DoD program management tooling **Benefits**: From text: "GRVTY provides competitive pay, comprehensive benefits, and meaningful opportunities for professional growth. Our benefits package is designed to support the well-being of our employees and their families, and includes coverage in areas such as healthcare, financial wellness, retirement planning, family assistance, continued education, and paid time off." Then later list: - Robust health plan including medical, dental, and vision - Health Savings Account with company contribution - Annual Paid Time Off and Paid Holidays - Paid Parental Leave - 401k with generous company match - Training and Development Opportunities - Award Programs - Variety of Company Sponsored Events We could combine into a Benefits section with a brief paragraph then list. **Pay**: "The pay range for this is $180,000.00 to $220,000.00." We'll put as a paragraph. Now ensure we don't include any boilerplate like EEO statement, etc. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  ...

  ...

  Pay

  The pay range for this is $180,00