Project Analyst
MITRE · McLean, VA · 1 mo ago
Business Development$83k–$104k/yrFull-time
We need to output HTML fragment with headings for 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 as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about MITRE: "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 about the organization, could be "About the role"? Actually "About the role" maybe includes description of role and department. There's a paragraph: "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 Analysis Safety Engineering Critical Infrastructure (CI) Threat Detection and Analytics CI Adversary Emulation Operational Technology (OT) Device Security Cross-Sector Interdependency analysis Civilian Critical Infrastructure Sector Specific Expertise"
That's about the role/department. So we can put that under
for 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 as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about MITRE: "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 about the organization, could be "About the role"? Actually "About the role" maybe includes description of role and department. There's a paragraph: "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 Analysis Safety Engineering Critical Infrastructure (CI) Threat Detection and Analytics CI Adversary Emulation Operational Technology (OT) Device Security Cross-Sector Interdependency analysis Civilian Critical Infrastructure Sector Specific Expertise"
That's about the role/department. So we can put that under About the role
.
Then "Roles & Responsibilities:" list of bullet points. Those go under Responsibilities
with - .
Then "Basic Qualifications:" list. That's under
Requirements
(or Qualifications?). The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map.
Basic Qualifications -> Requirements (maybe). Preferred Qualifications -> Qualifications (maybe). Skills maybe from proficiency with tools etc. Could be separate Skills section.
We have "Proficiency with common project management and collaboration tools (e.g., Microsoft Office, Microsoft Project, Jira, Confluence, SharePoint, or similar)." That's a skill. Also "Strong organizational, communication, and stakeholder coordination skills". Also "Ability to obtain and maintain any required government security clearances." Also "Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance." Also "This position requires a minimum of 3 days a week on-site." That's schedule.
Also "Preferred Qualifications:" list includes many items: Master's degree, certifications, experience supporting projects within systems engineering, etc., experience coordinating large multi-disciplinary team initiatives or tracking complex project finances, experience supporting federal government programs, knowledge of project lifecycle management methodologies, strong technical writing and presentation development skills, familiarity with risk management frameworks, experience coordinating geographically distributed teams, active government security clearance.
Also "This requisition requires the candidate to have a minimum of the following clearance(s): Not Applicable" and "This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): None". That's clearance info but we can maybe include under Requirements? But it's basically none.
Also "Salary compensation range and midpoint: $83,200 - $104,000 - $124,800". That's Pay.
"Annual Work Location Type: Onsite". That's Schedule? Actually schedule is about onsite days. We have "This position requires a minimum of 3 days a week on-site." That's schedule. Also "Annual Work Location Type: Onsite" maybe also schedule/location.
Benefits: The posting mentions "competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence." Also "Benefits information may be found here." No specific benefits listed. So we should not create Benefits section unless specific content. The instruction: never create Benefits section unless posting actually states them. It mentions competitive benefits but not specifics. Likely we should not include Benefits section because no specific benefits listed. However "competitive benefits" is a statement but not specific. The rule: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive benefits" is vague but not placeholder; still it's a statement. Might be okay to include Benefits with that sentence? But they said "include a section ONLY when the posting has real, specific content for it". "competitive benefits" is not specific. I'd skip Benefits.
Pay: we have specific range: $83,200 - $104,000 - $124,800. So include Pay.
Schedule: we have "This position requires a minimum of 3 days a week on-site." and "Annual Work Location Type: Onsite". That's specific enough for Schedule.
Requirements: Basic Qualifications list.
Qualifications: Preferred Qualifications list.
Skills: Could extract skills like proficiency with tools, strong organizational communication, stakeholder coordination, ability to obtain security clearance, US citizenship, etc. But many of those are already in Requirements/Qualifications. Might be better to have Skills section for things like "Proficiency with common project management and collaboration tools (e.g., Microsoft Office, Microsoft Project, Jira, Confluence, SharePoint, or similar)." and "Strong organizational, communication, and stakeholder coordination skills". Also "Strong technical writing and presentation development skills". Also "Familiarity with risk management frameworks, quality assurance processes, and performance measurement techniques". Those are from Preferred Qualifications but could be considered skills. However we already have Qualifications section for preferred qualifications; maybe we should not duplicate. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have content for Requirements (basic) and Qualifications (preferred). So we can include both.
Skills: Could be omitted if we feel it's thin. But we have some skill statements not captured elsewhere: "Proficiency with common project management and collaboration tools", "Strong organizational, communication, and stakeholder coordination skills", "Strong technical writing and presentation development skills", "Familiarity with risk management frameworks, quality assurance processes, and performance measurement techniques". Those are not in Basic or Preferred? Actually Preferred includes "Strong technical writing and presentation development skills, plus experience preparing executive-level briefings, sponsor communications, and technical project reports." and "Familiarity with risk management frameworks, quality assurance processes, and performance measurement techniques." So those are in Preferred Qualifications. So Skills may be redundant. Could still include Skills but might be thin. I'd omit Skills.
Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Pay, Schedule.
Check for any other sections: Benefits? skip.
Now we need to format.
About the role: include the paragraph about MITRE intro? Actually that's more about MITRE overall. The role-specific paragraph is the Critical Infrastructure Protection Department description. Should we include both? The instruction: preserve ALL substantive information. So we need to include the intro about MITRE as well. Where to put? Could be part of About the role. So combine both paragraphs.
Thus About the role content:
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."
Paragraph 2: "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 Analysis, Safety Engineering, Critical Infrastructure (CI) Threat Detection and Analytics, CI Adversary Emulation, Operational Technology (OT) Device Security, Cross-Sector Interdependency analysis, Civilian Critical Infrastructure Sector Specific Expertise."
We need to preserve the list of focus areas as they appear. Could be a maybe but they are currently in a sentence separated by commas. The instruction: Use - for any list of duties/requirements/benefits. Focus areas is a list; we could make a list. But it's not duties/requirements/benefits; it's focus areas. Still it's a list. Safer to keep as prose? The rule says use
- for any list of duties/requirements/benefits. Not explicitly for focus areas. Could keep as prose with commas. I'll keep as prose.
Now Responsibilities: list of bullet points after "Roles & Responsibilities:".
We need to capture each bullet.
Let's extract them:
- 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.
Now 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
Requirements
(or Qualifications?). The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map. Basic Qualifications -> Requirements (maybe). Preferred Qualifications -> Qualifications (maybe). Skills maybe from proficiency with tools etc. Could be separate Skills section. We have "Proficiency with common project management and collaboration tools (e.g., Microsoft Office, Microsoft Project, Jira, Confluence, SharePoint, or similar)." That's a skill. Also "Strong organizational, communication, and stakeholder coordination skills". Also "Ability to obtain and maintain any required government security clearances." Also "Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance." Also "This position requires a minimum of 3 days a week on-site." That's schedule. Also "Preferred Qualifications:" list includes many items: Master's degree, certifications, experience supporting projects within systems engineering, etc., experience coordinating large multi-disciplinary team initiatives or tracking complex project finances, experience supporting federal government programs, knowledge of project lifecycle management methodologies, strong technical writing and presentation development skills, familiarity with risk management frameworks, experience coordinating geographically distributed teams, active government security clearance. Also "This requisition requires the candidate to have a minimum of the following clearance(s): Not Applicable" and "This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): None". That's clearance info but we can maybe include under Requirements? But it's basically none. Also "Salary compensation range and midpoint: $83,200 - $104,000 - $124,800". That's Pay. "Annual Work Location Type: Onsite". That's Schedule? Actually schedule is about onsite days. We have "This position requires a minimum of 3 days a week on-site." That's schedule. Also "Annual Work Location Type: Onsite" maybe also schedule/location. Benefits: The posting mentions "competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence." Also "Benefits information may be found here." No specific benefits listed. So we should not create Benefits section unless specific content. The instruction: never create Benefits section unless posting actually states them. It mentions competitive benefits but not specifics. Likely we should not include Benefits section because no specific benefits listed. However "competitive benefits" is a statement but not specific. The rule: "never emit a heading followed by filler/placeholder text (e.g., 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive benefits" is vague but not placeholder; still it's a statement. Might be okay to include Benefits with that sentence? But they said "include a section ONLY when the posting has real, specific content for it". "competitive benefits" is not specific. I'd skip Benefits. Pay: we have specific range: $83,200 - $104,000 - $124,800. So include Pay. Schedule: we have "This position requires a minimum of 3 days a week on-site." and "Annual Work Location Type: Onsite". That's specific enough for Schedule. Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Skills: Could extract skills like proficiency with tools, strong organizational communication, stakeholder coordination, ability to obtain security clearance, US citizenship, etc. But many of those are already in Requirements/Qualifications. Might be better to have Skills section for things like "Proficiency with common project management and collaboration tools (e.g., Microsoft Office, Microsoft Project, Jira, Confluence, SharePoint, or similar)." and "Strong organizational, communication, and stakeholder coordination skills". Also "Strong technical writing and presentation development skills". Also "Familiarity with risk management frameworks, quality assurance processes, and performance measurement techniques". Those are from Preferred Qualifications but could be considered skills. However we already have Qualifications section for preferred qualifications; maybe we should not duplicate. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have content for Requirements (basic) and Qualifications (preferred). So we can include both. Skills: Could be omitted if we feel it's thin. But we have some skill statements not captured elsewhere: "Proficiency with common project management and collaboration tools", "Strong organizational, communication, and stakeholder coordination skills", "Strong technical writing and presentation development skills", "Familiarity with risk management frameworks, quality assurance processes, and performance measurement techniques". Those are not in Basic or Preferred? Actually Preferred includes "Strong technical writing and presentation development skills, plus experience preparing executive-level briefings, sponsor communications, and technical project reports." and "Familiarity with risk management frameworks, quality assurance processes, and performance measurement techniques." So those are in Preferred Qualifications. So Skills may be redundant. Could still include Skills but might be thin. I'd omit Skills. Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Pay, Schedule. Check for any other sections: Benefits? skip. Now we need to format. About the role: include the paragraph about MITRE intro? Actually that's more about MITRE overall. The role-specific paragraph is the Critical Infrastructure Protection Department description. Should we include both? The instruction: preserve ALL substantive information. So we need to include the intro about MITRE as well. Where to put? Could be part of About the role. So combine both paragraphs. Thus About the role content: 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." Paragraph 2: "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 Analysis, Safety Engineering, Critical Infrastructure (CI) Threat Detection and Analytics, CI Adversary Emulation, Operational Technology (OT) Device Security, Cross-Sector Interdependency analysis, Civilian Critical Infrastructure Sector Specific Expertise." We need to preserve the list of focus areas as they appear. Could be a- maybe but they are currently in a sentence separated by commas. The instruction: Use
- for any list of duties/requirements/benefits. Focus areas is a list; we could make a list. But it's not duties/requirements/benefits; it's focus areas. Still it's a list. Safer to keep as prose? The rule says use
- for any list of duties/requirements/benefits. Not explicitly for focus areas. Could keep as prose with commas. I'll keep as prose. Now Responsibilities: list of bullet points after "Roles & Responsibilities:". We need to capture each bullet. Let's extract them: - 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. Now 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