VDC Drafter

We need to output HTML fragment with headings for sections that have real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, etc. Also remove application instructions like "For more information, please visit our website..." and "Further details will be provided during the interview process..." and "We are an Equal Opportunity Employer..." etc. We need to preserve all substantive info. Let's parse the posting. Content: - Intro: "Comprehensive Energy Services, Inc. is hiring skilled VDC Drafter! Join a company that values people and is passionate about making a difference. Competitive based pay, opportunity for advancement with a supporting team and professional leadership. Don't wait any longer to join our CES Team today!" - Benefits: "Benefits Offered: Medical, Dental, Vision, Company Paid Life Insurance, Additional Life Insurance, Paid Short Term Disability, Long Term Disability, Accident, Cancer, Hospital, 401 K, Paid Time Off, Holiday pay, and more!" - Role description: "The VDC Drafter is responsible for producing accurate BIM models and construction and shop drawings for mechanical and plumbing systems. This role is hands-on and requires the drafter to manage assigned modeling and drawing tasks from start to finish, coordinate conflicts, and deliver complete drawing packages with minimal oversight." - Essential Duties: list of duties under headings: BIM Modeling and Drafting, Coordination and Clash Avoidance, Project Support Field and Shop, Document Control and Standards, Communication and Ownership. - Education And Experience: bullet list of requirements. - Qualifications And Skills: bullet list. - No explicit Pay or Schedule details beyond "Competitive based pay". That's vague; we should not create Pay section unless posting actually states them. "Competitive based pay" is not a specific number; but it's still mention of pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated, so we can include Benefits. Pay: "Competitive based pay" is a statement but not specific; maybe we can include Pay section with that phrase? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive based pay". That is a statement about pay, albeit vague. I'd include a Pay section with that sentence. Schedule: not mentioned, so omit. - Also we have "About the role" maybe we can include an introductory paragraph as About the role. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. We need to preserve all substantive info; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we will produce something like:

  About the role

  Comprehensive Energy Services, Inc. is hiring skilled VDC Drafter! Join a company that values people and is passionate about making a difference. Competitive based pay, opportunity for advancement with a supporting team and professional leadership. Don't wait any longer to join our CES Team today!

  Benefits

  • Medical
  • Dental
  • Vision
  • Company Paid Life Insurance
  • Additional Life Insurance
  • Paid Short Term Disability
  • Long Term Disability
  • Accident
  • Cancer
  • Hospital
  • 401 K
  • Paid Time Off
  • Holiday pay
  • and more!

  Responsibilities

  The VDC Drafter is responsible for producing accurate BIM models and construction and shop drawings for mechanical and plumbing systems. This role is hands-on and requires the drafter to manage assigned modeling and drawing tasks from start to finish, coordinate conflicts, and deliver complete drawing packages with minimal oversight.

  Then we can have subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

  for section headings (list). Likely they expect only those top-level headings. But we have detailed duties under categories like BIM Modeling and Drafting etc. Those could be represented as

  ? Not allowed? The instruction only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could embed those duty categories as

  or maybe as within

  . However they said use
  • for any list of duties/requirements/benefits. So we could list duties as items under a
    under Responsibilities. But the duties have subcategories; we could embed them as
    • with internal headings? Might be okay to use
    • BIM Modeling and Drafting: ...
    . That preserves detail. Similarly for Requirements (Education And Experience) and Qualifications And Skills. Thus:

    Requirements

    • Education: A bachelor's or master's degree in mechanical engineering, construction management, or other engineering fields is preferred. High school diploma or general education degree (GED) is required.
    • Experience: 2+ years in BIM/VDC drafting for a mechanical or plumbing contractor (or equivalent experience). Experience with Navisworks (clash detection and coordination). Working knowledge of AutoCAD (as-builts and details, if required). Working knowledge of Bluebeam (markups and coordination review). Familiarity with Autodesk/BIM360 (document control and model sharing). Experience with fabrication-driven modeling (spooling, prefab packages, and shop workflows).

    Skills

    • Strong working knowledge of Revit (mechanical and plumbing preferred).
    • Ability to read and interpret construction documents (plans, sections, schedules, and details).
    • Ability to produce buildable, install-ready drawings (not just models).
    • Comfortable working independently, prioritizing tasks, and owning deadlines.
    • Strong organization skills for models, sheets, revisions, and exports.
    We also need Pay section: "Competitive based pay". Could be a

    . Thus:

    Pay

    Competitive based pay.

    We should not include Schedule. Now ensure we removed boilerplate: "For more information, please visit our website ...", "Further details will be provided during the interview process and the job description.", "We are an Equal Opportunity Employer and a Drug-Free Work Place". Remove those. Also remove duplicated lines: none. Now output only HTML fragment. Check that we didn't miss any substantive info: The intro about company values, competitive pay, opportunity for advancement, supporting team, professional leadership, join CES Team today. That's in About the role. Benefits list includes all items. Responsibilities includes the description. Duties: we captured under Requirements and Skills? Actually duties are separate from requirements. We placed duties under Requirements? No, we placed education/experience under Requirements, and skills under Skills. But we lost the duty details (BIM Modeling and Drafting etc). We need to include those somewhere. Could put them under Responsibilities as a list. Thus under Responsibilities we can have a
    with each duty category as
    • containing subpoints. Let's extract duties: - BIM Modeling and Drafting: * Build and maintain Revit BIM models for mechanical and plumbing systems based on contract documents, specifications, submittals, and internal standards. * Produce shop drawings, spool sheets, layout drawings, and fabrication or installation details suitable for in-house shop and field use. * Develop and revise drawings for RFIs, ASIs, bulletins, and change orders, and incorporate coordination updates as the project evolves. * Create and manage families, parameters, view templates, sheets, legends, and annotation standards as needed to keep deliverables clean and consistent. - Coordination and Clash Avoidance: * Support model coordination using Navisworks (or similar) for clash detection and constructability review. * Identify conflicts early and resolve them through model adjustments or clear coordination notes, escalating only when necessary. * Maintain coordination quality across trades by aligning modeling to agreed elevation strategies, access clearances, and install sequencing. - Project Support Field and Shop: * Provide dimensioned layouts, penetration and sleeve coordination drawings, and install-ready details to support field execution. * Create prefab or spool packages that are cut-ready and organized for shop fabrication workflows. * Incorporate field feedback into drawings and keep models aligned with real installation conditions. - Document Control and Standards: * Keep models and sheets organized using company file structures and naming. * Maintain revision tracking and ensure drawing packages are complete prior to issue. * Coordinate and draft to project specifications and internal standards (systems, callouts, and typical details), where applicable. - Communication and Ownership: * Communicate with the Construction Operations teams on project updates. * Manage assigned scope independently: plan workload, flag missing information early, and deliver on schedule. * Coordinate directly with the VDC Manager, Project Managers, detailers, and shop leadership to confirm priorities and constructability needs. * Provide clear markups, screenshots, and concise notes for internal reviews and coordination items. We need to preserve all that. Thus under Responsibilities we can have a
      where each top-level duty is a
      • containing maybe a heading and then a
        for subpoints? But instruction says use
        • for any list of duties/requirements/benefits. It doesn't forbid nested lists. So we can do nested
          . Thus:

          Responsibilities

          • BIM Modeling and Drafting
            • Build and maintain Revit BIM models for mechanical and plumbing systems based on contract documents, specifications, submittals, and internal standards.
            • Produce shop drawings, spool sheets, layout drawings, and fabrication or installation details suitable for in-house shop and field use.
            • Develop and revise drawings for RFIs, ASIs, bulletins, and change orders, and incorporate coordination updates as the project evolves.
            • Create and manage families, parameters, view templates, sheets, legends, and annotation standards as needed to keep deliverables clean and consistent.
          • Coordination and Clash Avoidance
            • Support model coordination using Navisworks (or similar) for clash detection and constructability review.
            • Identify conflicts early and resolve them through model adjustments or clear coordination notes, escalating only when necessary.
            • Maintain coordination quality across trades by aligning modeling to agreed elevation strategies, access clearances, and install sequencing.
          • Project Support Field and Shop
            • Provide dimensioned layouts, penetration and sleeve coordination drawings, and install-ready details to support field execution.
            • Create prefab or spool packages that are cut-ready and organized for shop fabrication workflows.
            • Incorporate field feedback into drawings and keep models aligned with real installation