Associate Solutions Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Who We Are: description of CERT Division, SEI, etc. Could be "About the role"? Actually "Who We Are" is about organization. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - Who We Are: description of SEI, CERT Division. Could be "About the role"? Might be better as "About the role" describing the team and mission. - What We Do: description of CERT Situational Awareness team tasks. Could be "Responsibilities"? Actually responsibilities are listed later in Position Summary bullet list. So "What We Do" could be part of "About the role" or maybe "Responsibilities"? But we have a Position Summary with bullet list of responsibilities. Thus we can have sections: - About the role: combine Who We Are and What We Do? Or separate? The instruction says prefer few substantive sections over many thin ones. So we could have About the role (organization + mission), Responsibilities (the bullet list), Requirements (education/experience, travel, clearance), Qualifications (maybe desired experience?), Skills (Knowledge, Skills And Abilities), Benefits (maybe mention benefits link? but we should not include boilerplate like "Click here to view a listing of employee benefits" - that's a link to benefits but not actual benefit details. The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. It mentions "More Information Please visit “Why Carnegie Mellon” to learn more... Click here to view a listing of employee benefits". That's not stating benefits, just a link. So we should not create Benefits section. Pay: mentions "Pay Basis Salary". That's stating pay basis but not amount. It says "Pay Basis Salary". That is a statement about pay basis. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Pay Basis Salary". That's a statement about pay basis, though not amount. It's still stating pay basis. So we could include a Pay section with that line. However we need to avoid filler like "commensurate with experience". "Pay Basis Salary" is not filler; it's a specific statement. So include Pay section with
Pay Basis: Salary
maybe. Schedule: not mentioned. So no Schedule. Benefits: not specific, just link. So omit. Qualifications: we have Requirements (BS/MS etc) and Desired Experience. Could treat Requirements as Requirements section, and Desired Experience as Qualifications? Or combine? The instruction: Use headings like Requirements, Qualifications, Skills. So we can have Requirements (education/experience, travel, clearance). Qualifications (desired experience). Skills (Knowledge, Skills And Abilities). That seems appropriate. Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details. Let's extract details: Who We Are: - You will work within the CERT Division of the Software Engineering Institute (SEI). - Carnegie Mellon University’s SEI researches complex software engineering, cyber, and AI problems; creates and tests innovative technologies; and transitions mature solutions into practice for the Department of War (DoW) and federal government. What We Do: - The CERT Situational Awareness helps organizations, particularly those within the DoW, federal government, and critical infrastructure sectors, develop and maintain awareness of their cyber hybrid environments (cloud, on-premises, mobile), identify risks, and make informed decisions concerning cybersecurity, cyber resiliency, and cyber survivability. - The team applies cybersecurity, systems engineering, and operational analysis techniques to understand complex architectures and the relationships among systems, missions, workflows, data, and stakeholders. Position Summary (responsibilities bullet list): - Providing technical support as a team member in the development of security architectures, particularly to support cybersecurity operations and cybersecurity systems. - Supporting mission engineering, system of systems (SoS) architectures, systems requirements development, engineering, analysis, technology evaluation and deployment guidance. - Advancing the state of the art in cybersecurity and cybersecurity architectures. - Developing and evaluating advanced analytical techniques, including artificial intelligence (AI), machine learning (ML), behavioral analytics, and data-driven approaches for cyber operations. - Documenting current-state architectures, identifying capability and coverage gaps, evaluating technology integration strategies, recommending security solutions, and developing mission threads/workflows. - Supporting organizations in planning, assessing, and implementing Zero Trust and cyber resilience strategies. - Evaluating, piloting, and transitioning new technologies into operational environments. - Contribute to diverse teams composed of colleagues, customers, and subject matter experts to deliver projects. Requirements: - BS degree with three (3) years or MS with one (1) year or equivalent combination of training and experience. - Willingness to travel to various locations to support the SEI’s overall mission. This includes within the SEI and CMU community, sponsor sites, conferences, and offsite meetings on occasion. - Moderate Travel (20%). - You will be subject to a background check and must be eligible to obtain and maintain a Department of War security clearance. Knowledge, Skills And Abilities: - Ability to present technical topics to audiences from senior leadership to technical experts. - Ability to work with multiple stakeholders to promote practical solutions to tough security problems. - Strong understanding of networking, security, systems administration, programming, and/or cloud. - Ability to work at the SoS architecture level to identify and understand tradeoffs of various approaches. - Strong research and writing skills. Desired Experience: - Degree in Computer Science & Engineering or Systems Engineering with two (2) years of experience in cybersecurity/network operations, Model-Based Systems Engineering (MBSE), or workflow/process analysis; or equivalent combination of training and experience. - Experience in one or more of the following areas: - Enterprise/system-of-systems/system/security architecture - Security operations - Security research - Programming or software engineering - Networking - Testing Job Function Breakdown: - 75% Support to government program offices in the areas of strategy; process/policies; requirements elicitation; design and architecture; operations; outreach; and training. - 15% Enable the transition and appropriate focus of situational awareness analysis and engineering approaches and tools into operational environments. - 10% Design, prototype, and transition tactical analysis studies and tools appropriate for operational use in situational awareness. - 100% total effort Location: Arlington, VA, Pittsburgh, PA Job Function: Software/Applications Development/Engineering Position Type: Staff – Regular Full time/Part time Full time Pay Basis: Salary More Information: link to benefits etc (boilerplate). We'll ignore. Now we need to output HTML fragment with headings and appropriate content.
We need to decide which sections to include:
- About the role: combine Who We Are and What We Do? Could be two paragraphs.
- Responsibilities: the bullet list from Position Summary.
- Requirements: the bullet list (BS/MS, travel, clearance). Could be .
- Qualifications: Desired Experience (degree + experience areas). Could be .
- Skills: Knowledge, Skills And Abilities bullet list.
- Pay: Pay Basis Salary.
We should not include Location, Job Function, Position Type as headings because not in list. Could we include them as part of About the role? Probably not needed; but we must preserve ALL substantive information. If we omit location, that's substantive info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include location, job function, position type somewhere. Since we cannot create arbitrary headings not in the allowed list, we could embed them in existing sections as paragraphs. For example, add a paragraph under About the role that includes location and job function. Or we could create a separate section like "Details" but not allowed. So we need to fit them somewhere.
We could add a paragraph after About the role: "Location: Arlington, VA, Pittsburgh, PA. Job Function: Software/Applications Development/Engineering. Position Type: Staff – Regular Full time.
" That preserves info.
Similarly, we might include the Job Function Breakdown percentages. That's substantive. Where to put? Could be under Responsibilities as additional detail, or maybe under About the role. Could add a paragraph under Responsibilities after the list.
We must not create sections with filler. So we can add paragraphs inside sections.
Thus final HTML:
About the role
You will work within the CERT Division of the Software Engineering Institute (SEI). Carnegie Mellon University’s SEI researches complex software engineering, cyber, and AI problems; creates and tests innovative technologies; and transitions mature solutions into practice for the Department of War (DoW) and federal government.
The CERT Situational Awareness helps organizations, particularly those within the DoW, federal government, and critical infrastructure sectors, develop and maintain awareness of their cyber hybrid environments (cloud, on-premises, mobile), identify risks, and make informed decisions concerning cybersecurity, cyber resiliency, and cyber survivability. The team applies cybersecurity, systems engineering, and operational analysis techniques to understand complex architectures and the relationships among systems, missions, workflows, data, and stakeholders.
Location: Arlington, VA, Pittsburgh, PA. Job Function: Software/Applications Development/Engineering. Position Type: Staff – Regular Full time.
Responsibilities
- Providing technical support as a team member in the development of security architectures, particularly to support cybersecurity operations and cybersecurity systems.
- Supporting mission engineering, system of systems (SoS) architectures, systems requirements development, engineering, analysis, technology evaluation and deployment guidance.
- Advancing the state of the art in cybersecurity and cybersecurity architectures.
- Developing and evaluating advanced analytical techniques, including artificial intelligence (AI), machine learning (ML), behavioral analytics, and data-driven approaches for cyber operations.
- Documenting current-state architectures, identifying capability and coverage gaps, evaluating technology integration strategies, recommending security solutions, and developing mission threads/workflows.
- Supporting organizations in planning, assessing, and implementing Zero Trust and cyber resilience strategies.
- Evaluating, piloting, and transitioning new technologies into operational environments.
- Contribute to diverse teams composed of colleagues, customers, and subject matter experts to deliver projects.
Job Function Breakdown: 75% Support to government program offices in the areas of strategy; process/policies; requirements elicitation; design and architecture; operations; outreach; and training. 15% Enable the transition and appropriate focus of situational awareness analysis and engineering approaches and tools into operational environments. 10% Design, prototype, and transition tactical analysis studies and tools appropriate for operational use in situational awareness. 100% total effort.
Requirements
- BS degree with three (3) years or MS with one (1) year or equivalent combination of training and experience.
- Willingness to travel to various locations to support the SEI’s overall mission. This includes within the SEI and CMU community, sponsor sites, conferences, and offsite meetings on occasion.
- Moderate Travel (20%).
- You will be subject to a background check and must be eligible to obtain and maintain a Department of War security clearance.
Qualifications
- Degree in Computer Science & Engineering or
- .
- Skills: Knowledge, Skills And Abilities bullet list.
- Pay: Pay Basis Salary.
We should not include Location, Job Function, Position Type as headings because not in list. Could we include them as part of About the role? Probably not needed; but we must preserve ALL substantive information. If we omit location, that's substantive info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include location, job function, position type somewhere. Since we cannot create arbitrary headings not in the allowed list, we could embed them in existing sections as paragraphs. For example, add a paragraph under About the role that includes location and job function. Or we could create a separate section like "Details" but not allowed. So we need to fit them somewhere.
We could add a paragraph after About the role: "
- Providing technical support as a team member in the development of security architectures, particularly to support cybersecurity operations and cybersecurity systems.
- Supporting mission engineering, system of systems (SoS) architectures, systems requirements development, engineering, analysis, technology evaluation and deployment guidance.
- Advancing the state of the art in cybersecurity and cybersecurity architectures.
- Developing and evaluating advanced analytical techniques, including artificial intelligence (AI), machine learning (ML), behavioral analytics, and data-driven approaches for cyber operations.
- Documenting current-state architectures, identifying capability and coverage gaps, evaluating technology integration strategies, recommending security solutions, and developing mission threads/workflows.
- Supporting organizations in planning, assessing, and implementing Zero Trust and cyber resilience strategies.
- Evaluating, piloting, and transitioning new technologies into operational environments.
- Contribute to diverse teams composed of colleagues, customers, and subject matter experts to deliver projects.
- BS degree with three (3) years or MS with one (1) year or equivalent combination of training and experience.
- Willingness to travel to various locations to support the SEI’s overall mission. This includes within the SEI and CMU community, sponsor sites, conferences, and offsite meetings on occasion.
- Moderate Travel (20%).
- You will be subject to a background check and must be eligible to obtain and maintain a Department of War security clearance.
- Degree in Computer Science & Engineering or
Location: Arlington, VA, Pittsburgh, PA. Job Function: Software/Applications Development/Engineering. Position Type: Staff – Regular Full time.
" That preserves info. Similarly, we might include the Job Function Breakdown percentages. That's substantive. Where to put? Could be under Responsibilities as additional detail, or maybe under About the role. Could add a paragraph under Responsibilities after the list. We must not create sections with filler. So we can add paragraphs inside sections. Thus final HTML:About the role
You will work within the CERT Division of the Software Engineering Institute (SEI). Carnegie Mellon University’s SEI researches complex software engineering, cyber, and AI problems; creates and tests innovative technologies; and transitions mature solutions into practice for the Department of War (DoW) and federal government.
The CERT Situational Awareness helps organizations, particularly those within the DoW, federal government, and critical infrastructure sectors, develop and maintain awareness of their cyber hybrid environments (cloud, on-premises, mobile), identify risks, and make informed decisions concerning cybersecurity, cyber resiliency, and cyber survivability. The team applies cybersecurity, systems engineering, and operational analysis techniques to understand complex architectures and the relationships among systems, missions, workflows, data, and stakeholders.
Location: Arlington, VA, Pittsburgh, PA. Job Function: Software/Applications Development/Engineering. Position Type: Staff – Regular Full time.
Responsibilities
Job Function Breakdown: 75% Support to government program offices in the areas of strategy; process/policies; requirements elicitation; design and architecture; operations; outreach; and training. 15% Enable the transition and appropriate focus of situational awareness analysis and engineering approaches and tools into operational environments. 10% Design, prototype, and transition tactical analysis studies and tools appropriate for operational use in situational awareness. 100% total effort.