Technical Design 3 (contract)

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: contract assignment statement, etc? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the first sentence about contract assignment? It's maybe relevant but it's not a section; it's a statement about contract. Might be considered boilerplate? It's part of posting but not a heading. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep substantive info like responsibilities, qualifications, etc. The contract assignment statement is substantive? It says "This posting is for a contract assignment and is not a full-time employment offer with Boeing. Candidates selected for roles will be employed as contract workers through a Boeing approved 3rd party for the duration of the specified project." That's relevant info about employment type. Should we keep it? It's not under a heading; we could put it in a

before sections. It's not boilerplate. So keep. We need sections: About the role (maybe a summary). Responsibilities: list bullet points. Requirements: maybe Basic Qualifications. Qualifications: Preferred Qualifications. Skills: maybe combine? The instruction says use headings for those categories if content exists. We have Basic Qualifications (Required Skills/Experience) and Preferred Qualifications (Desired Skills/Experience). Could map Basic Qualifications to Requirements or Qualifications. Preferred Qualifications to Qualifications or Skills. We need to avoid thin sections. Let's decide: - About the role: short paragraph summarizing role (develops, maintains drawings etc). Could be from first paragraph after contract statement. - Responsibilities: list of responsibilities (the bullet list under "Position Responsibilities"). - Requirements: Basic Qualifications (required skills/experience). Could be called Requirements. - Qualifications: Preferred Qualifications (desired). Could be called Qualifications. - Skills: maybe not needed if we covered. - Benefits: we have Benefits Information: Optional Benefits: Medical, Dental, Vision, 401K. That's specific, so include Benefits section. - Pay: Pay Rate Range 36 - 41 USD hourly. Include Pay section. - Schedule: not mentioned; no schedule info, so omit. We must not include sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /. Use

for each section heading. Use

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

  for prose. We need to preserve all substantive info. Let's extract details. First paragraph after contract statement: "Develops, maintains and releases electrical/mechanical drawings, systems designs or engineering documentation and data by applying company, industry and governmental standards. Using design tools prepares documentation and incorporates design changes. Creates, develops and maintains systems designs by preparing design layouts, modifying existing designs and assisting in identifying design discrepancies. Supports engineering system design and functionality validation activities. Develops and maintains product installation designs and part designs ranging from simple to moderately complex. Coordinates activities and products with internal partners and external suppliers. Plan, conduct and document tests on products, Locate source data from the applicable files and systems. Perform analysis from either pre set-up packages or from original source data. Perform production roles as assigned. Follows desktop procedures, publications standards and government/customer specifications for authoring. When required, programs documents for multiple SGML outputs by applying applicability rules within the structure of the text. Determines proper effectivity and applicability for each authoring job. Verify information and check for discrepancies. Make changes as required. Marks up illustrations and submits using established procedures. Performs a thorough self-check of authored material. Develops solutions to routine technical problems of limited scope. Creates system theory descriptions of operations of limited scope and complexity by analyzing product designs and engineering principles to provide understanding of technical systems and components to ensure product reliability and safety. Develops maintenance, repair & retrofit procedures and techniques of limited scope and complexity that guide end-users to change, maintain and restore product into usable condition. Utilizes engineering data knowledge, maintenance operational knowledge and pertinent regulations that guarantee product reliability, safety and efficiency. Design, fabricate, build and analyzes test systems, components, materials, and manufacturing processes and technologies Works under general direction. Training will be provided post start. Team is looking for a technical/technician to fill this role, not looking for engineers." That's a lot of prose; we can keep as

  under About the role. Then "Position Responsibilities" list: each line starts with a verb. We'll make

  • each. List: - Develops, maintains and releases electrical/mechanical drawings, systems designs or engineering documentation and data by applying company, industry and governmental standards - Using design tools prepares documentation and incorporates design changes - Creates, develops and maintains systems designs by preparing design layouts, modifying existing designs and assisting in identifying design discrepancies - Supports engineering system design and functionality validation activities - Develops and maintains product installation designs and part designs ranging from simple to moderately complex - Coordinates activities and products with internal partners and external suppliers - Works under general direction (Note: The list also includes "Plan, conduct and document tests on products, Locate source data from the applicable files and systems. Perform analysis from either pre set-up packages or from original source data. Perform production roles as assigned. Follows desktop procedures, publications standards and government/customer specifications for authoring. When required, programs documents for multiple SGML outputs by applying applicability rules within the structure of the text. Determines proper effectivity and applicability for each authoring job. Verify information and check for discrepancies. Make changes as required. Marks up illustrations and submits using established procedures. Performs a thorough self-check of authored material. Develops solutions to routine technical problems of limited scope. Creates system theory descriptions of operations of limited scope and complexity by analyzing product designs and engineering principles to provide understanding of technical systems and components to ensure product reliability and safety. Develops maintenance, repair & retrofit procedures and techniques of limited scope and complexity that guide end-users to change, maintain and restore product into usable condition. Utilizes engineering data knowledge, maintenance operational knowledge and pertinent regulations that guarantee product reliability, safety and efficiency. Design, fabricate, build and analyzes test systems, components, materials, and manufacturing processes and technologies". Actually many of those are part of the earlier paragraph; they might be duplicated. The "Position Responsibilities" section only includes the bullet list after that heading? In the text, after "Position Responsibilities" there are lines each starting with a verb, but then after that there is "Basic Qualifications". The earlier long paragraph may be overlapping. To avoid duplication, we should treat the earlier paragraph as About the role (summary). Then the Position Responsibilities list as separate bullet points (the ones after that heading). We'll include those bullet points exactly as given. Let's extract the bullet list after "Position Responsibilities": - Develops, maintains and releases electrical/mechanical drawings, systems designs or engineering documentation and data by applying company, industry and governmental standards - Using design tools prepares documentation and incorporates design changes - Creates, develops and maintains systems designs by preparing design layouts, modifying existing designs and assisting in identifying design discrepancies - Supports engineering system design and functionality validation activities - Develops and maintains product installation designs and part designs ranging from simple to moderately complex - Coordinates activities and products with internal partners and external suppliers - Works under general direction Now Basic Qualifications (Required Skills/Experience): - Must be able to lift, push, and pull up to 35 pounds frequently within an 8-hour shift - 3+ years’ experience with designing the fabrication of wire harness/cables - 3+ years’ experience using power measurement test and measurement instrumentation (such as power supplies, power meters, and analyzers) - Experience reading and interpreting engineering drawings - 3+ years’ experience with electrical troubleshooting utilizing volt ohm meters and electrical system drawings - Experience fabricating, installing, routing, terminating, soldering, and repairing electrical wiring harnesses; or any variety of electrical components, and associated equipment Preferred Qualifications (Desired Skills/Experience): - Associate degree or higher - Active U.S. Secret Security Clearance - Knowledge with GOLDesp (work orders, fabrication orders, etc) Pay Rate Range: 36 - 41 USD hourly Benefits Information: Optional Benefits: Medical, Dental, Vision, 401K Now we need to output HTML. We'll start with a

    for the contract assignment statement? Might be considered boilerplate but it's substantive. We'll include as a

    before sections. Then About the role: we need a

    About the role

    then a

    with the summary paragraph (the long paragraph). Ensure we don't duplicate content that appears also in responsibilities. It's okay if some overlap but we should preserve all info; duplication is allowed? The instruction says remove duplicated lines. So we should avoid duplicating the same sentences. The long paragraph includes many sentences that also appear in responsibilities list? The responsibilities list is a subset. To avoid duplication, we could keep the long paragraph as About the role (summary) and keep responsibilities list as separate bullet points, even if some overlap. But that would duplicate content. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. If we include both the long paragraph and the responsibilities list, there will be duplicated lines (the responsibilities list items appear also in the long paragraph). To avoid duplication, we could either omit the long paragraph and keep responsibilities list as the main description, or keep the long paragraph and omit responsibilities list. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." The long paragraph is substantive; responsibilities list is also substantive but maybe thin. We could combine them: use the long paragraph as About the role, and not include a separate Responsibilities section. However the instruction says to use sections only when posting has real specific content for it. The posting does have a "Position Responsibilities" heading with specific bullet list. So we should include Responsibilities section. To avoid duplication, we could modify the About the role paragraph to be a brief summary not containing the same bullet points. But we must preserve ALL substantive information; we cannot omit or summarize away detail. So we need to keep all details. If we keep both, we will have duplicated lines (the same sentences appear twice). That violates "remove duplicated lines". So we need to avoid duplication by not repeating the same sentences. We could keep the long paragraph as is, and for Responsibilities we could keep only those items that are not already in the long paragraph. But the long paragraph seems to contain all those items (maybe more). Let's check: The long paragraph includes many of the same phrases: "Develops, maintains and releases electrical/mechanical drawings, systems designs or engineering documentation and data by applying company, industry and governmental standards." That's exactly the first bullet. It also includes "Using design tools prepares documentation and incorporates design changes." etc. It seems the long paragraph essentially contains all the responsibilities bullet points, maybe in more detail. So to avoid duplication, we could keep the long paragraph as the responsibilities description and not have a separate Responsibilities section. But then we lose the explicit "Position Responsibilities" heading. However the instruction says to include a section only when posting has real specific content for it. The posting does have a "Position Responsibilities" heading with specific content. If we omit that section, we are not representing that heading, but we still preserve the content (in About the role). Is that acceptable? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could use those headings if we have content. It doesn't say we must use Responsibilities heading if we have the content elsewhere. But we should try to follow the