Senior Systems Engineer

We need to output HTML fragment with sections for headings: 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. Remove boilerplate like EEO, accommodation, copyright, etc. Also remove duplicated lines. Must not create sections with placeholder text. We need to parse the posting. Key content: - Intro paragraph about MITRE mission etc. That could be "About the role"? Actually "About the role" heading likely for description of role and department. We'll put that as

About the role

with paragraphs summarizing MITRE and department description. - Responsibilities: The bullet list under "Roles & Responsibilities:" and then "The selected candidate will be expected to:" with many bullet-like sentences (each starting with a verb). We need to convert to

• . Must preserve all details. - Basic Qualifications: list of qualifications. Should go under Requirements? Or Qualifications? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where each piece fits. We have "Basic Qualifications:" and "Preferred Qualifications:" Also there are skills mentioned within qualifications. Could treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications or Skills. But we have separate headings for Requirements, Qualifications, Skills. We need to map content accordingly. Better: Use Requirements for basic qualifications (must-have). Use Qualifications for preferred qualifications (nice-to-have). Use Skills for specific technical skills mentioned (like MBSE tools, SysML, etc.) However the preferred qualifications already list many skills. Could combine. But we must not create sections with filler. If we put content under each heading, ensure it's substantive. Let's extract: About the role: description of MITRE, department, mission. We'll write a couple paragraphs. Responsibilities: list of expected duties (the bullet list after "The selected candidate will be expected to:"). Requirements: Basic Qualifications bullet points. Qualifications: Preferred Qualifications bullet points. Skills: maybe we could extract specific technical skills from both sets, but we already have them in Preferred Qualifications. Could still have Skills section summarizing tools: SysML, Cameo, MagicDraw, Rhapsody, Sparx EA, etc. But that would duplicate. Better to put those under Qualifications (preferred). Then we might not need Skills section. However we need to follow instruction: include a section ONLY when posting has real specific content for it. If we don't have distinct skills beyond qualifications, we can omit Skills. Benefits: The posting mentions "competitive benefits, meaningful career development, and a culture of innovation..." but not specific benefits like health insurance, 401k, etc. It says "supported by competitive benefits, meaningful career development, and a culture of innovation..." That's vague but still mentions benefits. However we should not create a Benefits section with placeholder like "competitive benefits" if it's not specific? 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" which is somewhat vague but still a statement about benefits. Is that considered specific enough? It's not a list. Might be considered filler? The instruction says avoid placeholder like "not specified". "competitive benefits" is somewhat generic but still a statement. I'd lean to include Benefits section with that sentence. Pay: The posting includes "Salary compensation range and midpoint: $121,200 - $151,500 - $181,800". That's specific. So we need Pay section. Schedule: The posting includes "Annual Work Location Type: Onsite Commitment to Non-Discrimination" and earlier "This position has an on-site requirement of 5 days a week on-site". So schedule: onsite, 5 days a week. So we can include Schedule section. We must not include boilerplate like EEO, accommodation, copyright, etc. Now craft HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  ...

  Pay

  Salary compensation range: $121,200 - $151,500 - $181,800 (midpoint).

  Schedule

  On-site work required 5 days per week.

  We need to ensure we preserve all substantive information from basic and preferred qualifications. Let's extract Basic Qualifications bullet points: - Minimum of 5 years of related experience with a Bachelor’s degree; or 3 years and a Master’s degree; or a PhD with relevant experience who can immediately contribute at this job step; 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 - Ability to collaborate 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. Note: The last two sentences about clearance and citizenship are part of qualifications. Now Preferred Qualifications bullet points (each line starts with a capital letter after a dash? Actually they are sentences separated by spaces. Let's list: - Knowledge of intelligence operations, the intelligence lifecycle, and intelligence systems - Experience applying MBSE methods using modeling languages and tools, such as SysML, Cameo, MagicDraw, Rhapsody, Sparx EA, or similar platforms - Experience developing SysML diagrams, including block definition diagrams, internal block diagrams, activity diagrams, sequence diagrams, state machine diagrams, requirement diagrams, and parametric models - Experience developing or applying systems architecture frameworks, architecture views, interface models, operational models, or enterprise architecture products - Experience advising the federal government on acquisition lifecycle activities, including SOW/SOO development, market research, acquisition planning, technical evaluations, source selection support, or adoption of innovative acquisition approaches - Experience supporting system integration, test planning, verification and validation, deployment readiness planning, or technical transition of mission systems - Experience with digital engineering, mission engineering, enterprise architecture, software-intensive systems, cloud-based systems, data platforms, cybersecurity, or command-and-control systems - Experience researching, assessing, prototyping, integrating, or supporting the transition of mission technologies such as secure communication protocols, mobile devices, terrestrial and space-based networking, artificial intelligence, cybersecurity, or related technologies Also there is line: "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". That's repetitive; we already have clearance requirement in basic qualifications. We can include it but not duplicate. We'll keep mention maybe in Requirements. Now Responsibilities bullet points: The list after "The selected candidate will be expected to:" each line starts with a verb. Let's extract each: - 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 - Support 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 - Conduct engineering studies, trade analyses, and gap assessments to evaluate current-state systems, operational processes, technology limitations, interoperability challenges, and opportunities to improve mission outcomes - Support 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 - Participate in 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 - Support 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 - Collaborate with 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 Now About the role: We need to capture MITRE description 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." Paragraph 2: "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 can combine into one or two paragraphs. Now 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." So we can include a sentence about competitive benefits etc. We'll put: "MITRE offers competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence." Now Pay: Already have. Schedule: "On-site work required 5 days per