Systems Engineer

We need to output HTML fragment with sections: h3 headings for sections present: About the role (maybe "Job Description" but we should use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include only sections with real specific content. We have content: Job Description paragraph (intro). That could be "About the role". Use

About the role

then

with description. Responsibilities: list of responsibilities. Use

Responsibilities

then

• ... each bullet. Requirements: maybe "Essential Skills" includes Bachelor's degree etc. Could be Requirements. Also Additional Skills & Qualifications. Could combine into Requirements and Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements, Qualifications, Skills separate if content exists. We have "Essential Skills" which includes Bachelor's degree, proficiency, etc. That could be Skills. Also "Additional Skills & Qualifications" could be Qualifications. We have Pay And Benefits: includes pay range and benefits list. So we need Pay section (maybe just pay range) and Benefits section (list). Also Work Environment includes location, onsite, etc. Could be Schedule? Not exactly. There's no explicit schedule besides "100% onsite". Could be Workplace Type. But we only have headings list; Schedule is optional if we have schedule info. We have "Work Environment" describing onsite, cubicle, test lab. Not schedule. Could omit Schedule if no specific schedule info (like hours). The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits stated, so include those. Schedule not stated (no hours/shift). So omit Schedule. We also have "Job Type & Location" which could be part of About the role or maybe we could include location in About the role. But we shouldn't create extra headings not in list unless needed. Could incorporate location into About the role paragraph. We need to preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove those. We must output only HTML fragment, no /, no markdown fences. Let's extract substantive content: Job Description paragraph: "We are seeking a Senior Lead Systems Engineer to drive system architecture definition, requirements development, and end-to-end integration and verification efforts across a portfolio of complex, interconnected systems. This role is responsible for ensuring system-level consistency, performance, and compliance with program objectives, while coordinating execution across multidisciplinary engineering teams. The ideal candidate will bring deep experience in complex systems development within regulated or mission-critical environments, strong expertise in interface control and lifecycle systems engineering, and a proven ability to lead technical execution in schedule-driven programs. Experience supporting government or defense-related programs is highly desirable." Responsibilities list: each bullet separated by periods? The text: "Lead end-to-end systems engineering activities across multiple related systems, including architecture definition, requirements development, interface management, risk assessment, verification planning, and formal design reviews.Establish, decompose, and maintain system-level requirements with full traceability to customer specifications, derived constraints, verification methods, and subsystem allocations.Coordinate technical execution across internal teams and external partners, ensuring consistent system architecture, controlled interfaces, aligned schedules, and delivery of verified, compliant system capabilities.Develop and maintain key system artifacts, including system block diagrams, interface control documents, data flow diagrams, verification matrices, integration strategies, and detailed test plans.Lead and facilitate technical interchange meetings, cross-functional design reviews, peer reviews, and supplier technical assessments, with a focus on verification readiness and system completeness.Collaborate closely with software, hardware, test engineering, manufacturing, configuration management, and program management teams to ensure cohesive system behavior and robust lifecycle verification.Provide leadership in configuration control, requirements management, and verification processes, supporting continuous improvement initiatives and adherence to industry quality standards.Mentor and guide junior engineers, contributing to the development and maturity of systems engineering practices across the organization." We need to split into list items. Each sentence before a period that starts a new responsibility. We'll split at periods that are followed by capital letter (or start of new sentence). We'll produce
• for each. Essential Skills: "Bachelor's degree in a relevant field with 8+ years of experience.Strong proficiency in full lifecycle systems engineering for embedded systems, with the ability to operate effectively in fixed-price, schedule-driven environments while supporting Agile development practices.Hands-on experience defining, refining, and maintaining traceable requirements baselines, including system modeling, analysis, and verification aligned to program commitments.Demonstrated capability to support system architecture definition, decomposition, design reviews, and configuration-controlled updates throughout the hardware/software lifecycle.Experience managing program and engineering workflows using tools such as Jira.Deep understanding of embedded systems, hardware/software integration, interface control, and data-driven decision-making across complex system interactions.Ability to obtain a clearance." We'll split similarly. Additional Skills & Qualifications: "Experience supporting government or defense-related research, development, or acquisition programs.Familiarity with requirements management tools such as DOORS or similar platforms.Experience coordinating multidisciplinary engineering teams and aligning Agile development with fixed-price contractual deliverables.Knowledge of environmental qualification standards and testing methods such as MIL-STD-461 and MIL-STD-810." Work Environment: "Current work includes space communication devices, working on navy cleared contracts, and even a few with major defense contractors. The position is 100% onsite due to the nature of the work. The work environment is cubicle-based with a small test lab. The team is diverse, with some members enjoying socializing after work and others focusing more on family life." Job Type & Location: "This is a Contract to Hire position based out of Greenville, SC." Pay And Benefits: includes pay range and benefits list. Pay range: "The pay range for this position is $55.00 - $84.13/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors." Benefits list: "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)" We need to output Benefits as
  • items. Should we split each benefit? The list includes multiple items separated by spaces. We'll parse: "Medical, dental & vision", "Critical Illness, Accident, and Hospital", "401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available", "Life Insurance (Voluntary Life & AD&D for the employee and dependents)", "Short and long-term disability", "Health Spending Account (HSA)", "Transportation benefits", "Employee Assistance Program", "Time Off/Leave (PTO, Vacation or Sick Leave)". We'll create li for each. Workplace Type: "This is a fully onsite position in Greenville,SC." This is similar to Job Type & Location. Could be part of About the role or we could add a section "Work Environment" but not in allowed headings. We could incorporate location into About the role or maybe we could add a "Qualifications" section for location? Not needed. We'll keep location in About the role paragraph. We must not repeat job title as heading. Good. We must not include boilerplate like EEO, legal, etc. Remove all that after "About Actalent" etc. Now produce HTML:

    About the role

    We are seeking a Senior Lead Systems Engineer to drive system architecture definition, requirements development, and end-to-end integration and verification efforts across a portfolio of complex, interconnected systems. This role is responsible for ensuring system-level consistency, performance, and compliance with program objectives, while coordinating execution across multidisciplinary engineering teams. The ideal candidate will bring deep experience in complex systems development within regulated or mission-critical environments, strong expertise in interface control and lifecycle systems engineering, and a proven ability to lead technical execution in schedule-driven programs. Experience supporting government or defense-related programs is highly desirable. This is a Contract to Hire position based out of Greenville, SC. The position is 100% onsite due to the nature of the work. The work environment is cubicle-based with a small test lab. The team is diverse, with some members enjoying socializing after work and others focusing more on family life.

    But we might be mixing too much. Perhaps better to keep About the role as the introductory paragraph only, and put location/work environment in a separate section? Not in allowed headings. Could add a "Work Environment" heading but not in list; maybe we should avoid. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. So we need to fit location/work environment into one of those sections. Could put location in About the role or maybe in Qualifications? Probably About the role is fine. Now Responsibilities section. We'll create

    • for each responsibility sentence. Let's split responsibilities: 1. Lead end-to-end systems engineering activities across multiple related systems, including architecture definition, requirements development, interface management, risk assessment, verification planning, and formal design reviews. 2. Establish, decompose, and maintain system-level requirements with full traceability to customer specifications, derived constraints, verification methods, and subsystem allocations. 3. Coordinate technical execution across internal teams and external partners, ensuring consistent system architecture, controlled interfaces, aligned schedules, and delivery of verified, compliant system capabilities. 4. Develop and maintain key system artifacts, including system block diagrams, interface control documents, data flow diagrams, verification matrices, integration strategies, and detailed test plans. 5. Lead and facilitate technical interchange meetings, cross-functional design reviews, peer reviews, and supplier technical assessments, with a focus on verification readiness and system completeness. 6. Collaborate closely with software, hardware, test engineering, manufacturing, configuration management, and program management teams to ensure cohesive system behavior and robust lifecycle verification. 7. Provide leadership in configuration control, requirements management, and verification processes, supporting continuous improvement initiatives and adherence to industry quality standards. 8. Mentor and guide junior engineers, contributing to the development and maturity of systems engineering practices across the organization. Now Requirements: maybe we can treat "Essential Skills" as Requirements? But we also have Skills heading. Let's assign: - Requirements: Bachelor's degree in a relevant field with 8+ years of experience. Ability to obtain a clearance. (maybe also experience supporting government/defense programs? That's in Additional Skills & Qualifications). But we need to not lose info. Better: Use Requirements for mandatory basics: Bachelor's degree, 8+ years experience, ability to obtain clearance. Use Skills for technical proficiencies. Use Qualifications for additional skills. Let's parse Essential Skills sentences: 1. Bachelor's degree in a relevant field with 8+ years of experience. 2. Strong proficiency in full lifecycle systems engineering for embedded systems, with the ability to operate effectively in fixed-price, schedule-driven environments while supporting Agile development practices. 3. Hands-on experience defining, refining