Engineer AutoCAD Plant 3D Piping Design

We need to output HTML fragment with sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. We need to extract content: The posting includes: - Date posted, hiring org, position number, industry, job title, location, work model, shift, employment type, estimated duration, min/max hourly rate (both 57.00), must have skills/attributes, experience desired, required minimum education, preferred education, note about C2C not available. - Job Description sections: Required Education, Preferred Education, Required Experience, Preferred Experience, Required Skills, Preferred Skills, Key Responsibilities. - Benefits: "For information and details on employment benefits offered with this position, please visit here." That's not specific benefit details; it's a link placeholder. According to rule: never create Benefits section unless posting actually states them. It says "For information and details on employment benefits offered with this position, please visit here." That's not actual benefit details; it's a generic statement. So we should not include Benefits section. - Pay: we have min and max hourly rate both $57.00. That is specific pay info. So we should include a Pay section with that info. - Schedule: we have Shift: M-F, 8am to 4pm. Also Work Model: Hybrid (Onsite 1-2 days a week). So schedule info includes shift and work model. We can include a Schedule section with that. - About the role: maybe we can include a brief paragraph summarizing the role? The posting includes job description but not a separate "About the role". We could create an About the role section using the job description summary? But we must not invent or summarize away detail. We could put the job description prose under About the role? However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if we have content. We need to decide which sections to include based on content. We have: - Responsibilities: we have Key Responsibilities bullet list. - Requirements: could combine required experience, required education, required skills? The instruction says we can have Requirements section. Could include required experience and required education. - Qualifications: could include preferred education, preferred experience, preferred skills? Or we could separate Qualifications and Skills. But we should not create thin sections. Prefer few substantive sections. We have specific content for: - Responsibilities (Key Responsibilities) -> list. - Requirements (Required Experience, Required Education, Required Skills) -> could be combined. - Qualifications (Preferred Education, Preferred Experience, Preferred Skills) -> maybe. - Pay (hourly rate) -> specific. - Schedule (Shift, Work Model) -> specific. We should not include Benefits because no specifics. We should not include About the role unless we have a paragraph describing role; we could use the job description prose that is not already captured in responsibilities? The job description includes paragraphs like "Required Education..." etc. Those are more about requirements. There's no separate overview paragraph. So we could omit About the role. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive information: need to include details like location, work model, shift, employment type, duration, hourly rate, must have skills/attributes, experience desired, required education, preferred education, required experience, preferred experience, required skills, preferred skills, key responsibilities. We need to format as HTML fragment: use

for headings,

• for lists,

  for prose. We need to decide structure: maybe sections: Requirements, Qualifications, Responsibilities, Pay, Schedule. Within Requirements: we can have subheadings? Not allowed; only

  for section headings. So we can't have nested headings. We could put paragraphs and lists. We could do:

  Requirements

  Location: Los Angeles, CA, USA, 90013

  Work Model: Hybrid (Onsite 1-2 days a week)

  Shift: M-F, 8am to 4pm

  Employment Type: Temporary, Full-Time

  Estimated Duration: 13 months

  Hourly Rate: $57.00 (fixed)

  Education: High School Diploma or equivalent required; Bachelor’s Degree preferred.

  Experience: 2–10 years of experience in engineering drafting/design; Experience supporting the design and documentation of high-pressure pipelines (4 years); Experience working in a collaborative, cross-functional environment (preferred); Experience applying drafting expertise across multiple disciplines (preferred).

  Skills (Required):

  • Autodesk AutoCAD Plant 3D proficiency
  • Strong technical drafting skills
  • Ability to develop and manage 3D piping models
  • Ability to create intelligent P&IDs
  • Ability to produce orthographic and isometric drawings
  • Ability to maintain project databases in alignment with industry standards
  • Ability to interpret engineering concepts into clear and precise technical documentation
  • Strong attention to detail

  Skills (Preferred):

  • Adaptability in a project environment
  • Cross-functional coordination skills
  • Continuous learning mindset
  • Understanding of engineering standards, regulatory requirements, and industry codes
  But we need to avoid duplication: we already listed experience details; we must preserve all substantive info. The "Must Have Skills/Attributes" list includes AutoCAD, Design, Engineering. That's somewhat covered by required skills but we should include it. Also "Experience Desired" includes specific years: Experience in engineering drafting/design (2-10 yrs); Experience supporting the design and documentation of high-pressure pipelines (4 yrs); Autodesk AutoCAD Plant 3D proficiency (2 yrs); Understanding of engineering standards, regulatory requirements, and industry codes (3 yrs). We should incorporate those. We have to be careful not to invent or summarize away detail. We can list them as prose. We also have "Required Minimum Education: High School Diploma or equivalent" and "Preferred Education: Bachelor’s Degree". Already captured. We have "Job Description Required Education High School Diploma required. Preferred Education Bachelor’s Degree preferred." Duplicate. We have "Required Experience 2–10 years of experience in engineering drafting/design. Experience supporting the design and documentation of high-pressure pipelines." etc. We have "Preferred Experience Experience working in a collaborative, cross-functional environment. Experience applying drafting expertise across multiple disciplines." We have "Required Skills Autodesk AutoCAD Plant 3D proficiency. Strong technical drafting skills. Ability to develop and manage 3D piping models. Ability to create intelligent P&IDs. Ability to produce orthographic and isometric drawings. Ability to maintain project databases in alignment with industry standards. Ability to interpret engineering concepts into clear and precise technical documentation. Strong attention to detail." We have "Preferred Skills Adaptability in a project environment. Cross-functional coordination skills. Continuous learning mindset. Understanding of engineering standards, regulatory requirements, and industry codes." We have "Key Responsibilities Lead the development and review of 3D models, piping layouts, and orthographic drawings. Ensure technical drawings and schematics comply with company standards and industry codes. Support the full design lifecycle through accurate technical documentation. Develop and manage 3D piping models and related design documentation. Generate intelligent P&IDs, orthographic drawings, and isometric drawings. Maintain project documentation and databases according to applicable industry standards." We need to preserve all that. We also have "Only those lawfully authorized to work in the designated country associated with the position will be considered." That's boilerplate legal/EEO? It's a legal statement about work authorization. According to instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal statement about work authorization; likely considered boilerplate legal. Should we remove? It's not EEO but it's a legal requirement. The instruction says remove legal boilerplate. So we should remove that line. Also "Please note that all Position start dates and duration are estimates and may be reduced or lengthened based upon a client’s business needs and requirements." That's also boilerplate; remove. Also benefits link etc remove. Also EEO statement etc remove. Also E-Verify statement etc remove. Thus we keep only substantive job details. Now we need to output HTML fragment only. We need to decide which sections to use. We could have:

  About the Role

  maybe with a short paragraph summarizing the role: Engineer AutoCAD Plant 3D Piping Design. But we must not invent or summarize away detail. Could we use the job title and location? That's not summarizing away detail; it's just restating. But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having a paragraph that mentions the job title. However "About the role" could be a short description; we could write something like "This position involves engineering drafting and design using AutoCAD Plant 3D for high-pressure pipeline projects in a hybrid work environment." That is summarizing but not inventing; it's derived from the posting. Is that allowed? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing could be considered summarizing away detail if we omit details. Safer to avoid About the role section unless we have a explicit paragraph in the posting that describes the role. There isn't one. So we omit About the role. Thus sections: Responsibilities, Requirements, Qualifications, Pay, Schedule. We need to ensure we don't create thin sections. Each of these will have substantive content. Let's craft:

  Responsibilities

  • Lead the development and review of 3D models, piping layouts, and orthographic drawings.
  • Ensure technical drawings and schematics comply with company standards and industry codes.
  • Support the full design lifecycle through accurate technical documentation.
  • Develop and manage 3D piping models and related design documentation.
  • Generate intelligent P&IDs, orthographic drawings, and isometric drawings.
  • Maintain project documentation and databases according to applicable industry standards.

  Requirements

  Location: Los Angeles, CA, USA, 90013

  Work Model: Hybrid (Onsite 1-2 days a week)

  Shift: Monday–Friday, 8am to 4pm

  Employment Type: Temporary, Full‑Time

  Estimated Duration: 13 months

  Education: High School Diploma or equivalent required; Bachelor’s Degree preferred.

  Experience: 2–10 years of experience in engineering drafting/design; 4 years of experience supporting the design and documentation of high‑pressure pipelines; 2 years of Autodesk AutoCAD Plant 3D proficiency; 3 years of understanding of engineering standards, regulatory requirements, and industry codes.

  Required Skills:

  • Autodesk AutoCAD Plant 3D proficiency
  • Strong technical drafting skills
  • Ability to develop and manage 3D piping models
  • Ability to create intelligent P&IDs