Principal EVMS Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove generic filler like "commensurate with experience" etc. We need to parse the posting. Key content: Description: Leidos has an immediate opening for a Principal Program EVMS Analyst to support a portfolio of programs within the Leidos Defense Systems Sector. This exciting role provides direct Earned Value Management Systems (EVMS) leadership and contribution to critical programs and related portfolios of work. The ideal candidate is recognized as professional EVM analyst, with a strong understanding of inter-company functional relationships, who can successfully interface with individual contributors, program finance analysts (PFAs), Schedulers, Control Account Managers (CAMs), Program Managers, and division executives. The position provides hands-on EVM support and guidance, while ensuring compliance with contractual requirements and company policy and procedures. In this role, you will be expected to establish, maintain, and grow key government customer relationships and help drive program growth and execution of the business rhythm. The Principal EVMS Analyst position will be an integral part of the larger enterprise-wide Leidos Corporate Earned Value Management (EVM) Center of Excellence (COE), a team-leading and executing the core responsibilities of scheduling, planning, EVMS, the associated infrastructure and tools, implementations, training, and surveillance for Leidos. Key Responsibilities: list bullet points. Basic Qualifications: list. Preferred Qualifications: list. Pay Range: $116,350.00 - $210,325.00. Benefits: "Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." Schedule: Not mentioned. So we should not include Schedule section. About Leidos: description of company. Could be "About the role"? Actually "About Leidos" is company overview. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. "About the role" could be the description paragraph. "Responsibilities" from Key Responsibilities. "Requirements" maybe Basic Qualifications. "Qualifications" maybe Preferred Qualifications? Or we could combine Requirements and Qualifications? The instruction says use those headings; we should include sections only when posting has real specific content. So we can have About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe from preferred qualifications like OPDEC IPM, Power BI, PMP certification), Benefits, Pay. No Schedule. We must not invent or summarize away detail. Must preserve all substantive info. So we need to list each bullet exactly as given, not paraphrase. Let's extract bullets. Key Responsibilities (as listed): - Responsible for execution of program EVMS policies and practices. - In coordination with the Director of Surveillance, supports internal and external surveillance, audits and reviews. - Responsible for supporting the organization's EVMS talent development, performance management, and business strategy. - Supports programs in operational decisions and provides advice on enhancing the performance of the portfolio. - Aligning and integrating material management and manufacturing practices with traditional scheduling and EVMS best practices for improved program management solutions. - Utilizes expert domain knowledge, professional principles and theories to develop advanced concepts, techniques, solutions and standards. - Supports EVM Team by providing a thorough understanding of EVMS, deliverable content, issue identification/resolution, etc. - Regularly interacts with senior executive leadership (internally or client) regarding matters of strategic importance to the organization/project. - Typically negotiates and develop shared solutions to convince internal and external parties to accept concepts, practices and approaches of the area. - Significant interface with Program Managers, Contracts and Senior Technical Personnel, as well as other organizations. - May participate in new business proposals through EVMS requirements, schedule support, and providing input for cost volumes to management. Basic Qualifications: - Requires a BA degree and 12+ years of prior relevant experience or Masters with 10+ years within DOD as a Prime Contractor - Must have advanced expertise using OPDEC IPM/Deltek Cobra EVM tools - IPMDAR Formats - Leading Variance Narrative efforts - Subcontractor data Integration - Must be able to obtain and maintain a Secret Clearance.(U.S Citizenship is required) - Must be willing and able to work onsite in Huntsville Alabama as needed, local candidates highly preferred as this is not a 100% remote opportunity. Preferred Qualifications: - OPDEC IPM - Active and current DoD Secret clearance - Experience in a Manufacturing/Production/Prototyping environment - Power BI - Program Management Professional (PMP) certification Skills: Could extract from preferred qualifications and maybe from responsibilities? But we should not invent. We could create a Skills section listing OPDEC IPM, Power BI, PMP certification, etc. However the instruction says prefer a few substantive sections over many thin ones. Might combine Skills into Qualifications? But we have both Requirements and Qualifications headings. Could treat Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. Skills maybe not needed if we can incorporate into Qualifications. But we need to follow headings list; we can omit Skills if no specific content beyond what's already covered. However the posting does mention specific skills: OPDEC IPM, Power BI, PMP certification, etc. Those are in Preferred Qualifications. So we could put them under Qualifications. That's fine. Benefits: we have description: Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at URL. That's substantive. Pay: Pay Range $116,350.00 - $210,325.00. Schedule: none. About the role: we need a paragraph summarizing the role description. Must preserve all substantive information; we cannot invent or summarize away detail. But we can condense? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we should keep them. However we can rephrase? It says do NOT summarize away detail. So we should keep the details, maybe as a paragraph that includes all the description sentences. We can keep the description as is, maybe split into multiple paragraphs but keep all info. Thus About the role section will contain the description paragraph(s) from the posting: "Leidos has an immediate opening for a Principal Program EVMS Analyst to support a portfolio of programs within the Leidos Defense Systems Sector. This exciting role provides direct Earned Value Management Systems (EVMS) leadership and contribution to critical programs and related portfolios of work. The ideal candidate is recognized as professional EVM analyst, with a strong understanding of inter-company functional relationships, who can successfully interface with individual contributors, program finance analysts (PFAs), Schedulers, Control Account Managers (CAMs), Program Managers, and division executives. The position provides hands-on EVM support and guidance, while ensuring compliance with contractual requirements and company policy and procedures. In this role, you will be expected to establish, maintain, and grow key government customer relationships and help drive program growth and execution of the business rhythm. The Principal EVMS Analyst position will be an integral part of the larger enterprise-wide Leidos Corporate Earned Value Management (EVM) Center of Excellence (COE), a team-leading and executing the core responsibilities of scheduling, planning, EVMS, the associated infrastructure and tools, implementations, training, and surveillance for Leidos." We should not include the "Original Posting September 18, 2026" etc. That's metadata; we can drop. Also "For U.S. Positions: While subject to change..." is boilerplate about posting duration; we can drop as it's not substantive about the job. The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "For U.S. Positions..." is not exactly boilerplate but maybe considered metadata; but it's not about job content. Safer to drop. Also "Pay And Benefits" heading appears; we will create Benefits and Pay sections. Now construct HTML. We need

for each section heading. Inside each section, we put

for prose,

• for lists. We must not include or . Let's craft. About the role: one

  containing the description. Responsibilities:

  with each bullet as
  • . Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Benefits:

    with benefits description. Pay:

    with pay range. We might also include a note about Pay range being guideline; but that's part of the posting. Should we include that sentence? It's substantive: "The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered..." We should preserve all substantive info, so include that as well. Thus Pay section:

    Pay Range $116,350.00 - $210,325.00. The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law.

    Benefits:

    Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits.

    We might also include the earlier sentence about Pay and benefits being fundamental... but that's fluff; we can keep? It's part of the posting but maybe considered boilerplate? It's generic but still part of the posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That sentence is not exactly boilerplate but could be considered generic. However it's part of the "Pay And Benefits" section. To be safe, we can include the substantive benefits list and the link. The earlier sentence "Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers." is somewhat generic but still part of the posting. I'd include it to preserve all substantive info? It's not really substantive detail about the job; it's more marketing. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is substantive? It's not specific to the job; it's generic. Might be considered boilerplate. I'd drop it to keep sections thin. But we need to be careful not to remove substantive info. The substantive info about benefits is the list and the link. So we keep that. Now check for any other sections: "About Leidos" company overview. Should we include that? The headings list includes "About the role", not "About Leidos". The company overview could be considered "About the role"? Not really. But we could include it under About the role? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect About the role to describe the role, not the company. The company overview is not requested