Estimator I

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes "ESSENTIAL FUNCTIONS / RESPONSIBILITIES:" and "EQUIPMENT KNOWLEDGE:", "ROLE REQUIREMENTS:", "PHYSICAL REQUIREMENTS:", "WORK ENVIRONMENT:" plus some other statements. We need to map to appropriate headings: Responsibilities (essential functions), Requirements (role requirements), Qualifications (maybe equipment knowledge?), Skills (maybe communication skills), Benefits (none), Pay (none), Schedule (none). Also maybe "About the role" could be a brief intro but not present. We should not create sections with filler. We need to preserve all substantive info, not invent. Remove boilerplate like "Reasonable accommodations may be made..." etc? That's part of work environment but maybe we can keep as prose under a section like "Work Environment". However the instruction says use headings only for those listed; we could still include a "Work Environment" heading? Not in list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should only use those headings. If we have content that doesn't fit, we could put under Responsibilities or Requirements as appropriate. We need to avoid repeating job title. No Job ID. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we should make
  • . For requirements list also. We need to use

    for prose. We must not include sections with placeholder like "commensurate with experience". Not present. We must not include Benefits, Pay, Schedule unless posting actually states them. It does not. So omit those sections. Thus we will have sections: Responsibilities, Requirements, Qualifications, Skills maybe. We need to decide what goes where. From posting: ESSENTIAL FUNCTIONS / RESPONSIBILITIES: bullet list of duties. EQUIPMENT KNOWLEDGE: bullet list: Corporate computer systems. Microsoft Applications ROLE REQUIREMENTS: bullet list: Ability to work will in a fast paced environment..., Understanding and support..., Ability to understand..., Must be able to read blue prints., Minimum two-year technical degree..., Knowledge of basic Mechanical Engineering concepts..., Knowledge of the ASME Code..., Verbal and written communication skills., Ability to effectively work with internal and external customers... PHYSICAL REQUIREMENTS: just a sentence about physical demands. WORK ENVIRONMENT: sentence about work environment, reasonable accommodations, etc. Also statement about ISO system, training checklist. We need to preserve all substantive info. So we need to include physical requirements and work environment somewhere. Could be under Requirements? Or maybe under Qualifications? But we have no heading for Physical Requirements or Work Environment. Could we create a section "Requirements" and include physical requirements as part of it? 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, but likely we should only use those headings. It says "include a section ONLY when the posting has real, specific content for it". So we could create a section "Requirements" and put all requirement-like content there, including role requirements, physical requirements, work environment, equipment knowledge maybe as qualifications. But we also have "Qualifications" heading; we could put education/experience etc there. "Skills" heading for communication skills etc. We need to avoid duplication. Let's parse: Responsibilities: essential functions bullet list. Equipment Knowledge: could be under Qualifications or Skills? It's knowledge of systems. Role Requirements: includes abilities, understanding, safety, reading blueprints, education, knowledge, communication skills, teamwork. Physical Requirements: sentence. Work Environment: sentence. ISO system training: sentence. We could create sections:

    Responsibilities

    with ul of duties.

    Requirements

    with ul of role requirements (abilities, safety, blueprint reading, education, knowledge, communication, teamwork). Also maybe include physical requirements as a

    under Requirements? But requirement list is for duties/requirements/benefits; physical requirements could be a

    .

    Qualifications

    maybe for equipment knowledge? Or we could put equipment knowledge under Qualifications as a
    .

    Skills

    maybe for communication skills? But communication skills already in requirements. Could combine. We need to avoid thin sections. Perhaps better: have Responsibilities, Requirements (includes role requirements, physical requirements, work environment, equipment knowledge), Skills (communication skills). But we need to ensure we don't lose info. Let's think: The instruction: "Use
    • for any list of duties/requirements/benefits, and

      for prose." So if we have a list, we must use ul/li. For prose, p. Thus we can have multiple sections each with either a list or prose. We need to decide which content is list vs prose. Responsibilities: list -> ul. Equipment Knowledge: list -> ul. Role Requirements: list -> ul. Physical Requirements: prose -> p. Work Environment: prose -> p. ISO system training: prose -> p. We could group prose under a section like "Additional Information" but not allowed heading. Could we put them under Requirements as prose after the list? That would mix list and prose in same section, which is okay; we can have both

      and

      under same heading. Thus we can have:

      Responsibilities

      ...

      Requirements

      ... role requirements ...

      Physical demands ...

      Work environment ...

      ISO system ...

      Qualifications

      Equipment knowledge ...
      But we also have education etc already in role requirements list; maybe we don't need separate Qualifications. We could instead have:

      Responsibilities

      ...

      Requirements

      ...

      Qualifications

      Equipment knowledge...
      But then physical requirements and work environment and ISO training would be missing. Could we put them under Requirements as prose after the list? Yes. Thus:

      Requirements

      ... role requirements ...

      Physical demands ...

      Work environment ...

      ISO system ...

      That covers all. Now we need to ensure we don't include boilerplate like "This job description is not intended to be all inclusive..." etc. That's under WORK ENVIRONMENT? Actually after WORK ENVIRONMENT there is: "This job description is not intended to be all inclusive, and the employee will also perform other reasonably related business duties as assigned by immediate supervisor and other management, as required. Staffing of positions to be determined by the company. As an employee, you are required to understand the ISO system and the elements that affect your job. Must prove that employee can meet the essential duties of the job within 90 days by completing employee training checklist F-HR-720-02-03-01." We need to preserve substantive info; that includes the ISO system statement and training checklist. The earlier sentences about job description not inclusive etc may be considered boilerplate? It's generic but still part of posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The sentence about job description not inclusive could be considered boilerplate legal? Might be considered generic disclaimer. Safer to remove it? It's not EEO etc. But it's a standard disclaimer. I'd lean to remove it as boilerplate. Keep the ISO system and training checklist. Thus under Requirements we will have prose: "As an employee, you are required to understand the ISO system and the elements that affect your job. Must prove that employee can meet the essential duties of the job within 90 days by completing employee training checklist F-HR-720-02-03-01." Now we need to extract the bullet points exactly. Let's copy responsibilities bullets: - Communicates with customers via telephone, e-mail, determining customer needs and requirements to assist in developing designs, specifications, and actively sells SPVG’s products and services - Analyzes each customer RFQ to determine product specifications, the method of manufacture, and other customer requirements such as packaging and delivery. Determines the optimum method of manufacturing for the product to meet or exceed customer’s functionality, quality, appearance, and delivery requirements. Communicates with the Engineering staff for product design criteria. - Calculates the projected costs of labor, material, sub-contracting and transportation, and sends the customer a detailed quotation for the project on a timely basis. - Responsible to send customer an amended quote letter when changes in the delivered quote letter are necessary or the projected delivery date varies more than two to four weeks from the quote date. - Adhere to and abide by all ITAR-specific job standards and training. Protect and properly safeguard ITAR-sensitive information and work product; ensure dissemination or disclosure of and access to “protected data” occurs only with those trained and approved for exposure to ITAR content. - IMMEDIATELY notify Supervisor/Manager, Human Resources, Legal (email: compliance@samuel.com) or the Samuel Ethics Alert Hotline of known or suspected unauthorized disclosure, release of or access to protected ITAR content. Equipment Knowledge: - Corporate computer systems. - Microsoft Applications Role Requirements: - Ability to work will in a fast paced environment to meet team expectations. (typo "will" but keep) - Understanding and support of Company policies and procedures. - Ability to understand and abide by all safety rules and regulations to perform the job. - Must be able to read blue prints. - Minimum two-year technical degree and/or 3 to 5 years of related job experience. - Knowledge of basic Mechanical Engineering concepts are desired. - Knowledge of the ASME Code, and ability to use ASME related software is a plus. - Verbal and written communication skills. - Ability to effectively work with internal and external customers in a team environment Physical Requirements: sentence: "The physical demands described here are representative of those that must be met by an employee to successfully preform the essential functions of this job." Work Environment: "The work environment characteristics described are representative of those an employee encounters while performing the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." Then after that: "This job description is not intended to be all inclusive, and the employee will also perform other reasonably related business duties as assigned by immediate supervisor and other management, as required. Staffing of positions to be determined by the company. As an employee, you are required to understand the ISO system and the elements that affect your job. Must prove that employee can meet the essential duties of the job within 90 days by completing employee training checklist F-HR-720-02-03-01." We'll keep the ISO system sentence and training checklist; remove the earlier generic sentences. Thus prose for Requirements after list: "As an employee, you are required to understand the ISO system and the elements that affect your job. Must prove that employee can meet the essential duties of the job within 90 days by completing employee training checklist F-HR-720-02-03-01." Now we need to output HTML fragment only. Structure:

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      As an employee, you are required to understand the ISO system and the elements that affect your job. Must prove that employee can meet the essential duties of the job within