Project Analyst

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, not invent. We need to parse the posting. First paragraph: "At MITRE, your passion fuels work that impacts our nation and improves lives. This is where your skills strengthen national security, cybersecurity, health, transportation, and citizen services. We’re a nonprofit engineering, applied research, and advanced technology organization working in the public interest. With objectivity and integrity at our core, we lead federally funded research and development centers for U.S. government agencies – collaborating with industry and academia to deliver integrated, high-impact solutions that advance our nation’s health, security, and prosperity. Our people tackle the toughest technical challenges, supported by competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence. Choose MITRE for a career with purpose — and help shape the future." That's general about MITRE. Could be "About the role" or maybe "About MITRE". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have a description of the department and role: "The Critical Infrastructure Protection Department (L561) sits within MITRE’s Cyber-Physical Systems Division. L561 delivers innovative solutions by bringing a multidisciplinary approach to sponsor challenges that are critical to national security and public sector missions. Our work involves researching, developing, and applying advanced technologies in protecting national critical infrastructure from non-kinetic threats and ensuring operational resiliency. Focus areas include: Infrastructure Susceptibility AnalysisSafety EngineeringCritical Infrastructure (CI) Threat Detection and AnalyticsCI Adversary EmulationOperational Technology (OT) Device SecurityCross-Sector Interdependency analysisCivilian Critical Infrastructure Sector Specific Expertise" Then "Roles & Responsibilities:" list of bullet-like sentences. Then "Basic Qualifications:" list. Then "Preferred Qualifications:" list. Then "This requisition requires the candidate to have a minimum of the following clearance(s): Not Applicable This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): None" Then "Salary compensation range and midpoint: $83,200 - $104,000 - $124,800" Then "Annual Work Location Type: Onsite" Then some legal boilerplate etc which we need to remove. We need to include sections only when there is real specific content. We have: - About the role: Could include the MITRE description and department description. Probably combine into About the role. - Responsibilities: The list under "Roles & Responsibilities:" is responsibilities. - Requirements: Could be Basic Qualifications? Usually Requirements = Basic Qualifications. We'll use Requirements heading for Basic Qualifications. - Qualifications: Could be Preferred Qualifications? Or maybe Skills? The instruction includes Skills section separate. We have skills listed in qualifications (proficiency with tools, etc). We could put skills under Skills section. But we also have Preferred Qualifications which could go under Qualifications (maybe Preferred). However we need to decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have: - About the role: description of MITRE and department. - Responsibilities: list of duties. - Requirements: Basic Qualifications (must-haves). - Qualifications: Preferred Qualifications (nice-to-haves). Could also include education etc but we already used Basic for Requirements. So Qualifications for Preferred. - Skills: Could extract specific skills like proficiency with MS Office, MS Project, Jira, Confluence, SharePoint; stakeholder coordination; technical writing; presentation development; risk management frameworks; etc. But many are already in Preferred Qualifications. Might be redundant. Perhaps better to put skills under Skills and keep Qualifications for education/certifications. But the instruction says prefer few substantive sections over many thin ones. So maybe we combine Preferred Qualifications and Skills into Qualifications section. However we have separate headings allowed; we should only include if there is real specific content. We have content for Skills (proficiency with tools, stakeholder coordination, technical writing, presentation development, risk management frameworks, quality assurance, performance measurement). That's specific. So we could have Skills section. - Benefits: The posting mentions "competitive benefits, meaningful career development" but no specific benefits list. There's a line "Benefits information may be found here." No actual benefits detail. So we should NOT create Benefits section because no specific content. - Pay: Salary compensation range given: $83,200 - $104,000 - $124,800. That's specific. So we need Pay section. - Schedule: "This position requires a minimum of 3 days a week on-site." Also "Annual Work Location Type: Onsite". So we have schedule info: onsite requirement 3 days/week. So we can create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe Preferred), Skills, Pay, Schedule. We need to ensure we don't repeat job title as heading. Not needed. We need to output only HTML fragment, no /. Use

for headings,

• for lists,

  for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: legal, EEO, accommodation, copyright, etc. Also remove duplicated lines. We need to include the focus areas list: "Infrastructure Susceptibility AnalysisSafety EngineeringCritical Infrastructure (CI) Threat Detection and AnalyticsCI Adversary EmulationOperational Technology (OT) Device SecurityCross-Sector Interdependency analysisCivilian Critical Infrastructure Sector Specific Expertise". This seems like a run-on list without commas. We need to preserve as is? Probably we should keep as a sentence or list. Could turn into

  • each item. But the original lacks separators; we could keep as a paragraph. However we need to preserve all substantive information; we can present as a comma-separated list for readability but that would be altering? It's not adding info, just formatting. Might be okay. Safer to keep as a paragraph with the exact string. But we need to avoid duplication: The focus areas line appears as "Focus areas include: Infrastructure Susceptibility AnalysisSafety EngineeringCritical Infrastructure (CI) Threat Detection and AnalyticsCI Adversary EmulationOperational Technology (OT) Device SecurityCross-Sector Interdependency analysisCivilian Critical Infrastructure Sector Specific Expertise". We'll keep that. Now let's extract each piece. About the role: Combine first paragraph and department description. Paragraph 1: "At MITRE, your passion fuels work that impacts our nation and improves lives. This is where your skills strengthen national security, cybersecurity, health, transportation, and citizen services. We’re a nonprofit engineering, applied research, and advanced technology organization working in the public interest. With objectivity and integrity at our core, we lead federally funded research and development centers for U.S. government agencies – collaborating with industry and academia to deliver integrated, high-impact solutions that advance our nation’s health, security, and prosperity. Our people tackle the toughest technical challenges, supported by competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence. Choose MITRE for a career with purpose — and help shape the future." Department description: "The Critical Infrastructure Protection Department (L561) sits within MITRE’s Cyber-Physical Systems Division. L561 delivers innovative solutions by bringing a multidisciplinary approach to sponsor challenges that are critical to national security and public sector missions. Our work involves researching, developing, and applying advanced technologies in protecting national critical infrastructure from non-kinetic threats and ensuring operational resiliency. Focus areas include: Infrastructure Susceptibility AnalysisSafety EngineeringCritical Infrastructure (CI) Threat Detection and AnalyticsCI Adversary EmulationOperational Technology (OT) Device SecurityCross-Sector Interdependency analysisCivilian Critical Infrastructure Sector Specific Expertise" We can combine into a few paragraphs. Responsibilities: list under "Roles & Responsibilities:" each sentence starts with a verb. We'll make
    • each. List: - Coordinate technical projects across multidisciplinary teams supporting critical infrastructure protection, cyber-physical systems, and operational technology security initiatives. - Develop and maintain project schedules, milestones, deliverables, action-item trackers, and status reports to ensure successful project execution. - Support project planning activities, including scope definition, resource coordination, risk identification, and dependency management. - Facilitate communication and collaboration among technical staff, project leaders, sponsors, and external stakeholders. - Track project progress and assist in resolving schedule, resource, and execution challenges to maintain program objectives. - Organize and coordinate technical meetings, working groups, workshops, and sponsor engagements, including documenting outcomes and follow-up actions. - Support the preparation of project documentation, technical reports, presentations, briefings, and other project artifacts. - Assist in monitoring project budgets, funding allocations, and contract-related activities as applicable. - Collect, analyze, and communicate project performance metrics to support informed decision-making. - Coordinate configuration management, document control, and information-sharing activities across project teams. - Support continuous improvement efforts by identifying opportunities to enhance project management processes, tools, and workflows. - Ensure project activities comply with organizational policies, quality standards, and sponsor requirements. That's 13 items. Requirements (Basic Qualifications): - Bachelor's degree in project management, Business Administration, Engineering, Computer Science, Cybersecurity, Information Systems, or a related technical field; or a combination of relevant education, training, and professional experience that demonstrates comparable knowledge and skills. - Minimum 2 years of experience coordinating technical projects, programs, technical initiatives, or related operational activities. - Familiarity with technical environments involving systems engineering, cybersecurity, cyber-physical systems, operational technology, critical infrastructure, or research and development activities. - Demonstrated ability to manage project schedules, deliverables, action items, and project documentation. - Strong organizational, communication, and stakeholder coordination skills in a multidisciplinary team environment. - Proficiency with common project management and collaboration tools (e.g., Microsoft Office, Microsoft Project, Jira, Confluence, SharePoint, or similar). - Ability to obtain and maintain any required government security clearances. - Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance. - This position requires a minimum of 3 days a week on-site. Wait the on-site requirement is also in Schedule; but it's also a requirement. We'll keep it in Requirements? Might duplicate. Better to put onsite in Schedule section only. But the basic qualifications includes "This position requires a minimum of 3 days a week on-site." That's a requirement. However we also have Schedule section for onsite. To avoid duplication, we could keep it in Requirements and not repeat in Schedule. But the instruction says include Schedule section only if posting actually states them. It does state onsite requirement. So we need Schedule section. We could keep the onsite mention in Schedule and remove from Requirements to avoid duplication. However the requirement list includes it; removing might lose info. But we could keep it in Requirements as well; duplication is allowed? The instruction says remove duplicated lines. So we should avoid duplicating the same sentence. So we should place the onsite requirement only in Schedule section, not in Requirements. So we will omit that line from Requirements. Thus Requirements list excludes the onsite line. Qualifications (Preferred Qualifications): - Master’s degree in project management, Business Administration, Engineering, Cybersecurity, or a related discipline. - Project Management Professional (PMP), Certified associate in project management (CAPM), Agile, Scrum, or related project management certification. - Experience supporting projects within systems engineering, cyber-physical systems, critical infrastructure protection, operational technology (OT), industrial control systems (