Lead Systems Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the posting. First, there is introductory paragraph about MITRE, mission, etc. That could be "About the role" or maybe "About the role" is not present; but we can treat the initial description as "About the role" or maybe "About MITRE". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections accordingly. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Commitment to Non-Discrimination", "Benefits information may be found here.", copyright, etc. We need to include Pay section only if posting actually states them. The posting includes: "Salary compensation range and midpoint: $146,400 - $183,000 - $219,600". So we have Pay. Schedule: "Annual Work Location Type: Onsite". Also earlier: "This position has an on-site requirement of 5 days a week on-site". So schedule: onsite, 5 days a week. Benefits: The posting mentions "supported by competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence." Also later: "Benefits information may be found here." But we should not include placeholder "Benefits information may be found here." but we have mention of competitive benefits. However we need specific benefits? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive benefits". That's somewhat vague but it's a statement. Is that enough? It says "supported by competitive benefits". That's a statement about benefits existing. It's not specific like health insurance, 401k, etc. But it's still a statement about benefits. The instruction says never create Benefits sections unless the posting actually states them. It does state that there are competitive benefits. So we can include a Benefits section with that sentence. But we need to avoid filler like "competitive benefits" maybe considered vague but it's still a statement. I'd include it. Now we need to structure content. We have: - Intro paragraph about MITRE mission etc. Could be "About the role" or maybe "About MITRE". Since they said "About the role" as example, we can use that heading for the introductory descriptive paragraph about the role and organization. - Then "Roles & Responsibilities:" section with bullet list of duties. We'll convert to

• . - Then "Basic Qualifications:" section with list of qualifications. - Then "Preferred Qualifications:" section. - Then maybe "Clearance Requirements:" but not in headings list; we could incorporate into Requirements or Qualifications. Since we have only those headings, we could put clearance under Requirements or Qualifications. Probably under Requirements (Basic Qualifications). But we already have Basic Qualifications heading; we could rename to Requirements? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Basic Qualifications (minimum experience, etc.) and Preferred Qualifications. Those could go under Requirements and Qualifications respectively. Or we could have Requirements for basic, Qualifications for preferred. Skills maybe from preferred qualifications like knowledge of MBSE tools etc. But we can also put skills under Skills section. Better: Use sections: - About the role (intro paragraph) - Responsibilities (the bullet list under Roles & Responsibilities) - Requirements (Basic Qualifications) - Qualifications (Preferred Qualifications) - Skills (maybe extract specific skills from preferred qualifications: knowledge of intelligence operations, MBSE methods using tools, developing SysML diagrams, architecture frameworks, advising on acquisition, supporting integration/test, digital engineering, mission engineering, etc.) - Benefits (competitive benefits statement) - Pay (salary range) - Schedule (onsite 5 days a week) We must not repeat job title as heading. No job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from Basic Qualifications and Preferred Qualifications exactly as written, but we can format as list items. We need to avoid duplication: there are duplicated lines about clearance etc. We'll include once. We need to remove boilerplate: "Commitment to Non-Discrimination", "All qualified applicants will receive consideration...", "MITRE intends to maintain a website...", "If you are unable to search or apply...", "This service is for individuals requiring reasonable accommodation requests.", "Please note that vendor solicitations will not receive a reply.", "Benefits information may be found here.", copyright, trademark, etc. Also remove duplicated lines like "This requisition requires the candidate to have a minimum of the following clearance(s): Top Secret/SCI/Polygraph" and "This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Top Secret/SCI/Polygraph". We can keep one statement about clearance requirement. Now produce HTML. We'll start with

  About the role

  then

  with the introductory paragraph(s). The introductory paragraph includes multiple sentences: "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. The Systems and Operations Department (L626) within MITRE’s Systems Engineering Division in the Center for Engineering and Analysis delivers innovative, mission-focused solutions using a multidisciplinary systems engineering approach to address sponsor challenges critical to national security missions. We advance engineering rigor, operational relevance, and mission effectiveness across complex systems and enterprises, with core focus areas in Domain Systems Engineering, Lifecycle Systems Engineering, and Acquisition Systems Engineering. Our teams develop, assess, and transition engineering solutions, provide strategic technical vision, and deliver data-informed recommendations that enable sponsor mission success from tactical through enterprise levels." We need to keep all that. Then

  Responsibilities

  then
  with each bullet from "Roles & Responsibilities:" and the bullet list after "The selected candidate will be expected to:" and the subsequent bullet points. We need to capture each bullet line. Let's extract them: - Apply systems engineering principles across the system development lifecycle, including mission analysis, concept development, system design, architecture definition, requirements development, integration, verification, validation, deployment planning, and technical transition - Lead system design and architecture activities by translating sponsor mission needs, operational constraints, and capability gaps into system concepts, functional designs, technical approaches, and implementation options - Develop, assess, and refine system architectures for complex mission systems, including operational views, functional architectures, logical and physical architectures, interfaces, data flows, dependencies, and integration points - Apply TSE and MBSE methods to capture system behavior, structure, requirements, interfaces, constraints, verification relationships, trade space, risks, and technical decisions - Conduct stakeholder engagements, workshops, interviews, and technical working groups to elicit, analyze, document, and validate clear, testable, and traceable mission, system, product, interface, performance, security, and operational requirements - Perform engineering studies, trade analyses, and gap assessments to evaluate current-state systems, operational processes, technology limitations, interoperability challenges, and opportunities to improve mission outcomes - Steer integration, test, verification, validation, deployment planning, and technical transition activities for complex systems, including integration sequencing, test objectives, success criteria, interface dependencies, and deployment readiness considerations - Perform alternative analysis for government sponsors and program managers on mission context, capability needs, technical priorities, system roadmaps, technology insertion opportunities, acquisition strategies, and engineering approaches that support program objectives - Lead acquisition planning and execution by contributing to Statements of Work, Statements of Objectives, Performance Work Statements, market research, acquisition strategies, evaluation criteria, technical evaluation plans, source selection documentation, and vendor assessments - Facilitate multidisciplinary teams to develop and present technical artifacts, architecture briefings, decision papers, trade study results, requirements packages, interface documentation, and engineering recommendations for sponsor and leadership review - Serve as a mentor to junior staff by providing guidance, feedback, and knowledge-sharing to support their professional growth and strengthen team capabilities We need to ensure we keep all. Now

  Requirements

  for Basic Qualifications. Basic Qualifications text: "Minimum of 8 years of related experience with a Bachelor’s degree; or 6 years and a Master’s degree; or a PhD with 3 years’ experience; or equivalent combination of related education and work experience Experience applying systems engineering practices to complex technical, operational, or mission-focused systems Experience with system design, system architecture modeling, requirements development, interface analysis, integration planning, verification and validation, and technical documentation Familiarity with both MBSE and traditional systems engineering approaches, including requirements analysis, functional decomposition, interface control, trade studies, risk analysis, technical reviews, and engineering decision support Ability to develop or review architecture products, requirements specifications, trade studies, technical plans, acquisition artifacts, and engineering recommendations Experience leading technical tasks, facilitating stakeholder workshops, coordinating multidisciplinary engineering teams, or advising senior technical and program leadership Ability to collaborate directly with government sponsors, program managers, technical teams, acquisition stakeholders, and mission users Strong analytical, verbal, and written communication skills, including the ability to define ambiguous problems, structure technical options, and brief technical concepts to both technical and non-technical audiences Ability to work both collaboratively and independently in a dynamic sponsor environment Willingness to work at various sponsor locations in the Northern Virginia area as needed Must have an active Top Secret/SCI with Polygraph U.S Government issued Security Clearance. Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance. This position has an on-site requirement of 5 days a week on-site" Note: The on-site requirement also appears later; we might duplicate. We'll keep it once maybe under Schedule. But it's also a requirement. We'll keep it under Requirements as part of basic qualifications, but we also need Schedule section. To avoid duplication, we could mention it only under Schedule and not duplicate under Requirements. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we remove it from Requirements, we are omitting that detail. So we need to keep it somewhere. We could keep it in Requirements and also mention in Schedule? That would be duplication. Better to keep it in Requirements and not have a separate Schedule section? But we have schedule info also from "Annual Work Location Type: Onsite Commitment". That's also schedule. So we could combine: schedule: onsite, 5 days a week. We can keep that detail in Schedule section and not duplicate in Requirements. However the Basic Qualifications includes "Willingness to work at various sponsor locations in the Northern Virginia area as needed" and "Must have an active Top Secret/SCI with Polygraph..." and "This position has an on-site requirement of 5 days a week on-site". If we move the onsite requirement to Schedule, we still have the willingness to work at various sponsor locations in Northern Virginia area as