Systems Engineer (FORECASTED)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. From posting: - Description: "This Position is Contingent on Contract Award** Description Columbia Technology Partners is seeking Systems Engineers to support the full system lifecycle, from concept development through retirement. Our Systems Engineers collaborate with customers, program personnel, and government stakeholders to develop innovative solutions, manage technical risks, and ensure the successful delivery of mission-critical capabilities. Opportunities are available for experienced engineers ranging from Level 2 through Level 6, with responsibilities spanning technical execution, project leadership, enterprise engineering, and subject matter expertise." That's about the role. - Key Responsibilities - SE Level 2 list bullet points. - Additional Responsibilities - SE Level 3 etc. - Additional Responsibilities - SE Level 4 etc. - Additional Responsibilities - SE Level 5 etc. - Additional Responsibilities - SE Level 6 etc. Thus responsibilities content. - Qualifications: Bachelor's degree ... etc. Also includes level-specific experience requirements. - Preferred Qualifications: list. - Requirements: U.S. Citizenship required, etc. Also includes security clearance, polygraph, drug testing, background investigation. - About Us: description of company. - Salary Range Transparency: description of how salary determined but no actual numbers. No explicit salary range given. So we should NOT create Pay section because no specific pay numbers. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: there is a "Really Good Benefits, For Really GREAT People" section describing benefits: medical plans, vision+dental free, retirement 401k 6% company contribution, PTO, career growth up to $10k, life insurance, profit sharing, referral bonus. So we have benefits content. - Schedule: not mentioned. So no Schedule section. - Skills: maybe we can infer from Preferred Qualifications? But we need a Skills section only if posting has real specific content for it. There's no explicit "Skills" heading, but we could treat Preferred Qualifications as skills? The instruction: Use sections only when posting has real, specific content for it. There's no explicit Skills section, but we could include a Skills section if we can extract skill-related content. However, we might combine Preferred Qualifications into Requirements or Qualifications. Safer to not create a Skills section unless there is explicit skill list. There is "Strong communication skills", "Experience leading engineering teams", etc. That's skill-like. But we could put them under Responsibilities or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could combine skills into Qualifications or Responsibilities. Probably better to have sections: About the role, Responsibilities, Qualifications, Requirements, Benefits. No Skills, Pay, Schedule. Check if there is any explicit "Pay" content: Salary Range Transparency describes how they determine salary but no numbers. That's not specific pay info, so we should not create Pay section. Now we need to format: - Use

for section headings. - Use

• for any list of duties/requirements/benefits. - Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can structure them. We need to avoid repeating job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement; we should remove that. Also "Columbia Technology Partners is an Equal Opportunity Employer." etc. Remove. Also remove "This Position is Contingent on Contract Award**" maybe keep as part of description? It's a note; we can keep as prose. We need to preserve all substantive information: description, responsibilities per level, qualifications per level, preferred qualifications, requirements (citizenship, security clearance, drug testing, background investigation, polygraph), about us, benefits details. We must not include duplicated lines. Ensure we don't repeat same bullet across levels? The responsibilities for each level include previous level responsibilities plus additional. We could list them as separate subsections per level, but we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we remove duplication, we might lose detail? But we could keep each level's full responsibilities (including previous). That would duplicate content but it's still preserving detail. However we could also note that each level includes previous responsibilities plus additional. But that would be summarizing. Safer to keep each level's full list as given, even if duplicated. Thus we will have:

  About the role

  This Position is Contingent on Contract Award** Columbia Technology Partners is seeking Systems Engineers to support the full system lifecycle, from concept development through retirement. Our Systems Engineers collaborate with customers, program personnel, and government stakeholders to develop innovative solutions, manage technical risks, and ensure the successful delivery of mission-critical capabilities. Opportunities are available for experienced engineers ranging from Level 2 through Level 6, with responsibilities spanning technical execution, project leadership, enterprise engineering, and subject matter expertise.

  Then responsibilities: maybe a heading

  Responsibilities

  and then subheadings for each level? But we only allowed

  for section headings. Could we use

  ? Not allowed. So we must stick to

  for section headings only. We could use

  with bold? Not allowed? The instruction only says use

  for section headings. It doesn't forbid other headings, but to be safe we can just use

  for each major section and within that use

  • for lists. For sub-sections we could use

    with strong text? Not prohibited. We'll just use

    to label each level. Thus:

    Responsibilities

    SE Level 2

    • Apply systems engineering principles across the system lifecycle, including concept, development, production, utilization, support, and retirement.
    • Support systems engineering activities within ISO/IEC 15288 Technical, Project, Agreement, and Enterprise Process Areas.
    • Perform technical analyses and evaluate engineering alternatives to support project objectives.
    • Develop and deliver systems engineering work products and technical documentation.
    • Assist with requirements analysis, architecture development, integration, verification, validation, transition, operations, and maintenance activities.
    • Communicate technical issues, risks, and recommendations to project stakeholders.
    Then

    SE Level 3

    and list includes previous responsibilities plus additional. We'll need to list all items as given: "In addition to the responsibilities above, SE 3 candidates will: Independently analyze technical solutions and recommend alternatives for project design decisions.Develop and deliver engineering products across Technical, Project, and Enterprise Process Areas.Support engineering efforts across a broader range of ISO/IEC 15288 processes with minimal supervision.Contribute to more complex systems engineering activities and project-level technical planning." We need to split into list items. The original text is a run-on sentence; we can separate by periods. Let's parse: - Independently analyze technical solutions and recommend alternatives for project design decisions. - Develop and deliver engineering products across Technical, Project, and Enterprise Process Areas. - Support engineering efforts across a broader range of ISO/IEC 15288 processes with minimal supervision. - Contribute to more complex systems engineering activities and project-level technical planning. Also we need to include the responsibilities from Level 2? The phrase "In addition to the responsibilities above" implies they also do Level 2 responsibilities. To preserve all detail, we should include Level 2 responsibilities again? Could duplicate. We'll include them again to be safe. Thus for Level 3 we will list Level 2 bullets plus the additional bullets. Similarly for Level 4,5,6. That will be large but okay. Now Qualifications: we have a paragraph describing degree requirements and then level-specific experience. We'll need to preserve all detail. We'll present as

    for general qualification, then maybe

    Level 2: ...

    etc. Preferred Qualifications: list bullet points. Requirements: U.S. Citizenship required, CTP is equal opportunity employer (remove EEO), all applicants subject to random drug testing per EO 12564, employment contingent upon successful completion of security background investigation and polygraph. Certification Requirements: N/A (we can drop as it's not substantive). Also "This position requires an active Security Clearance with appropriate Polygraph." That's a requirement. We need to remove EEO boilerplate and equal opportunity lines. So we will keep: "U.S. Citizenship is required for all applicants." "All applicants and employees are subject to random drug testing in accordance with Executive Order 12564." "Employment is contingent upon successful completion of a security background investigation and polygraph." "This position requires an active Security Clearance with appropriate Polygraph." Also maybe note "Certification Requirements:N/A" we can drop. About Us: we need to keep the description of company, but remove EEO lines at end. The About Us paragraph includes: "Founded in 2007, Columbia Technology Partners is a Service-Disabled Veteran Owned Small Business with a specialization in technology and management consulting committed to solving intricate and sensitive technology issues facing corporations and federal agencies. Since its inception, CTP has been instrumental in the technical design, engineering development, operational deployment, and support of key systems. With a proven track record in information security, project management, systems/network engineering, security risk management, vulnerability assessments, and mobile security implementation; our employees have the experience, expertise, and innovative thinking our customers need for results that exceed expectations. CTP staff have worked closely with both government engineers and management to gather mission requirements, develop the architecture to deliver the needed functionality and assess tools available to meet or exceed the needs of the mission. At Columbia Technology Partners (CTP), we are united in being the best that we can be as individuals, but our core belief is that we can be better together. Together we will take on each mission with an execution process that authentically represents who we are. Our success relies on our team values, the foundation we built around them, and the Partners we become along the way. That's why our pay is competitive, our missions are critical, and our benefits represent what matters most to CTP: Our People." We should keep that. Then Salary Range Transparency: we will not create Pay section because no specific numbers. However the text includes "That's why our pay is competitive..." but that's not specific. So we skip Pay. Then Benefits: "Really Good Benefits, For Really GREAT People" etc. We'll capture all benefit details. We need to remove EEO statement at end. Now produce HTML. Let's craft. We'll need to escape any special characters? Not needed. We'll produce:

    About the role

    This Position is Contingent on Contract Award** Columbia Technology Partners is seeking Systems Engineers to support the full system lifecycle, from concept development through retirement. Our Systems Engineers collaborate with customers, program personnel, and government stakeholders to develop innovative solutions, manage technical risks, and ensure the successful delivery of mission-critical capabilities. Opportunities are available for experienced engineers ranging from Level 2 through Level 6, with responsibilities spanning technical execution, project leadership, enterprise engineering, and subject matter expertise.

    Responsibilities

    SE Level 2

    • Apply systems engineering principles across the system lifecycle, including concept, development, production, utilization, support, and retirement.
    • Support systems engineering activities within ISO/IEC 15288 Technical, Project, Agreement, and Enterprise Process Areas.
    • Perform technical analyses and evaluate engineering alternatives to support project objectives.
    • Develop and deliver systems engineering