Associate Solutions Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Who We Are: description of CERT Division, SEI, etc.
- What We Do: description of CERT Situational Awareness.
- Position Summary: list of responsibilities (bulleted? Actually colon then list separated by periods). We'll need to extract responsibilities as list items.
- Requirements: bullet list? It says: "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: list of abilities.
- Desired Experience: bullet? It says: "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: percentages.
- Benefits: paragraph describing benefits.
- 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 etc.
We need to decide which sections to include: About the role (maybe "About the role" corresponds to Who We Are/What We Do?), Responsibilities (Position Summary), Requirements (the Requirements block), Qualifications/Skills (Knowledge, Skills And Abilities + Desired Experience maybe combined), Benefits (Benefits paragraph), Pay (Pay Basis), Schedule (maybe not present; we have Moderate Travel (20%) but not schedule). No explicit schedule like full-time/part-time? Position Type indicates full time. Could treat that as Schedule? But schedule section is for work schedule (e.g., full-time, part-time, shift). The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. We have Position Type: Staff – Regular Full Time/Part time Full time. That's somewhat redundant but indicates full time. Could we put that under Schedule? Might be okay. But we also have Pay Basis: Salary. That's specific content for Pay.
We need to avoid filler like "commensurate with experience", "not specified", etc. We have actual content.
We need to output only HTML fragment, no /, no markdown fences.
We'll decide sections:
-
About the role
: combine Who We Are and What We Do? Could be two paragraphs.
- Responsibilities
: list from Position Summary.
- Requirements
: list from Requirements block.
- Skills
: combine Knowledge, Skills And Abilities and Desired Experience? Or separate Qualifications and Skills? The instruction says use headings like Qualifications, Skills. We could have Qualifications
for degree/experience requirements (maybe overlapping with Requirements). But we already have Requirements. Could treat Requirements as qualifications. Then Skills as abilities.
Better: Use Requirements
for the mandatory requirements (degree, travel, clearance). Use Skills
for Knowledge, Skills And Abilities and Desired Experience.
But we also have Job Function Breakdown percentages; maybe that could be under Responsibilities? Or we could add a section Job Function
but not in allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those.
Thus:
- About the role: Who We Are + What We Do.
- Responsibilities: Position Summary + Job Function Breakdown? The breakdown is about effort allocation; could be part of responsibilities.
- Requirements: BS/MS degree, travel, background check, clearance.
- Qualifications: maybe Desired Experience? Or we could treat Qualifications as the desired experience/education.
- Skills: Knowledge, Skills And Abilities.
- Benefits: Benefits paragraph.
- Pay: Pay Basis Salary.
- Schedule: Position Type (Full time) maybe.
We must avoid duplication. Ensure we preserve all substantive information.
Let's extract text.
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."
Combine into maybe two paragraphs.
Responsibilities (Position Summary):
List items:
- 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.
Note: The last item starts with "Contribute" (lowercase c) but we keep as is.
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
We could incorporate these as part of Responsibilities (maybe as sub-items). But we need to preserve all substantive info; we can add them as list items under Responsibilities.
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.
We could combine travel and moderate travel: maybe "Willingness to travel ... Moderate Travel (20%)."
Qualifications (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
Skills (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.
Benefits:
Paragraph: "Joining the CMU team opens the door to an array of exceptional benefits. Benefits eligible employees enjoy a wide array of benefits including comprehensive medical, prescription, dental, and vision insurance as well as a generous retirement savings program with employer contributions. Unlock your potential with tuition benefits, take well-deserved breaks with ample paid time off and observed holidays, and rest easy with life and accidental death and disability insurance. Additional perks include a free Pittsburgh Regional Transit bus pass, access to our Family Concierge Team to help navigate childcare needs, fitness center access, and much more! For a comprehensive overview of the benefits available, explore our Benefits page."
We should keep that as a paragraph (maybe multiple sentences). Could be one .
Pay:
- Pay Basis: Salary.
We could output
Pay
Salary
Schedule:
- Position Type: Staff – Regular Full Time/Part time Full time. Essentially full-time.
We could output Schedule
Full-time
Location: Arlington, VA, Pittsburgh, PA. Not a heading; we could include as a short maybe under About the role? But instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could fold into a short
maybe after About the role.
Job Function: Software/Applications Development/Engineering. Also minor metadata; could fold.
We need to preserve ALL substantive information; location and job function are substantive? They are details about the job. Should we keep them? Probably yes, as minor metadata in a short
. The instruction says fold minor metadata into a short
or drop it. So we can include a short
with location and job function.
We must not include boilerplate like EEO, etc.
Now construct HTML.
We'll start with
About the role
... who we are ...
... what we do ...
Location: Arlington, VA, Pittsburgh, PA. Job Function: Software/Applications Development/Engineering.
Then Responsibilities
- ... each responsibility ...
... plus job function breakdown items as li.
Then Requirements
- ... each requirement ...
Then Qualifications
- ... desired experience bullet ...
- ... experience areas sublist? Could nest ul inside li? But we can just list each area as separate li under a parent li? Simpler: list each area as separate li under Qualifications? Might lose grouping. Could do:
- Degree in Computer Science & Engineering or Systems Engineering with two (2) years of experience in cybersecurity/network operations, Model-Based Systems Engineering (MBSE), or
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Who We Are: description of CERT Division, SEI, etc. - What We Do: description of CERT Situational Awareness. - Position Summary: list of responsibilities (bulleted? Actually colon then list separated by periods). We'll need to extract responsibilities as list items. - Requirements: bullet list? It says: "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: list of abilities. - Desired Experience: bullet? It says: "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: percentages. - Benefits: paragraph describing benefits. - 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 etc. We need to decide which sections to include: About the role (maybe "About the role" corresponds to Who We Are/What We Do?), Responsibilities (Position Summary), Requirements (the Requirements block), Qualifications/Skills (Knowledge, Skills And Abilities + Desired Experience maybe combined), Benefits (Benefits paragraph), Pay (Pay Basis), Schedule (maybe not present; we have Moderate Travel (20%) but not schedule). No explicit schedule like full-time/part-time? Position Type indicates full time. Could treat that as Schedule? But schedule section is for work schedule (e.g., full-time, part-time, shift). The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. We have Position Type: Staff – Regular Full Time/Part time Full time. That's somewhat redundant but indicates full time. Could we put that under Schedule? Might be okay. But we also have Pay Basis: Salary. That's specific content for Pay. We need to avoid filler like "commensurate with experience", "not specified", etc. We have actual content. We need to output only HTML fragment, no /, no markdown fences. We'll decide sections: -
About the role
: combine Who We Are and What We Do? Could be two paragraphs. -Responsibilities
: list from Position Summary. -Requirements
: list from Requirements block. -Skills
: combine Knowledge, Skills And Abilities and Desired Experience? Or separate Qualifications and Skills? The instruction says use headings like Qualifications, Skills. We could haveQualifications
for degree/experience requirements (maybe overlapping with Requirements). But we already have Requirements. Could treat Requirements as qualifications. Then Skills as abilities. Better: UseRequirements
for the mandatory requirements (degree, travel, clearance). UseSkills
for Knowledge, Skills And Abilities and Desired Experience. But we also have Job Function Breakdown percentages; maybe that could be under Responsibilities? Or we could add a sectionJob Function
but not in allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. Thus: - About the role: Who We Are + What We Do. - Responsibilities: Position Summary + Job Function Breakdown? The breakdown is about effort allocation; could be part of responsibilities. - Requirements: BS/MS degree, travel, background check, clearance. - Qualifications: maybe Desired Experience? Or we could treat Qualifications as the desired experience/education. - Skills: Knowledge, Skills And Abilities. - Benefits: Benefits paragraph. - Pay: Pay Basis Salary. - Schedule: Position Type (Full time) maybe. We must avoid duplication. Ensure we preserve all substantive information. Let's extract text. 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." Combine into maybe two paragraphs. Responsibilities (Position Summary): List items: - 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. Note: The last item starts with "Contribute" (lowercase c) but we keep as is. 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 We could incorporate these as part of Responsibilities (maybe as sub-items). But we need to preserve all substantive info; we can add them as list items under Responsibilities. 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. We could combine travel and moderate travel: maybe "Willingness to travel ... Moderate Travel (20%)." Qualifications (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 Skills (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. Benefits: Paragraph: "Joining the CMU team opens the door to an array of exceptional benefits. Benefits eligible employees enjoy a wide array of benefits including comprehensive medical, prescription, dental, and vision insurance as well as a generous retirement savings program with employer contributions. Unlock your potential with tuition benefits, take well-deserved breaks with ample paid time off and observed holidays, and rest easy with life and accidental death and disability insurance. Additional perks include a free Pittsburgh Regional Transit bus pass, access to our Family Concierge Team to help navigate childcare needs, fitness center access, and much more! For a comprehensive overview of the benefits available, explore our Benefits page." We should keep that as a paragraph (maybe multiple sentences). Could be one. Pay: - Pay Basis: Salary. We could output
Pay
Salary
Schedule: - Position Type: Staff – Regular Full Time/Part time Full time. Essentially full-time. We could outputSchedule
Full-time
Location: Arlington, VA, Pittsburgh, PA. Not a heading; we could include as a shortmaybe under About the role? But instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could fold into a short
maybe after About the role. Job Function: Software/Applications Development/Engineering. Also minor metadata; could fold. We need to preserve ALL substantive information; location and job function are substantive? They are details about the job. Should we keep them? Probably yes, as minor metadata in a short
. The instruction says fold minor metadata into a short
or drop it. So we can include a short
with location and job function. We must not include boilerplate like EEO, etc. Now construct HTML. We'll start with
About the role
... who we are ...
... what we do ...
Location: Arlington, VA, Pittsburgh, PA. Job Function: Software/Applications Development/Engineering.
ThenResponsibilities
- ... each responsibility ... ... plus job function breakdown items as li. Then
- ... each requirement ...
- ... desired experience bullet ...
- ... experience areas sublist? Could nest ul inside li? But we can just list each area as separate li under a parent li? Simpler: list each area as separate li under Qualifications? Might lose grouping. Could do:
- Degree in Computer Science & Engineering or Systems Engineering with two (2) years of experience in cybersecurity/network operations, Model-Based Systems Engineering (MBSE), or