Job Captain

We need to output HTML fragment with sections: About us? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: About us (company description), Overview (role description), Primary Responsibilities (list), Reports to: Engineering Manager (metadata), Requirements (Education, Experience and Desired Qualifications) (list), Supervisory Responsibility: Yes. Lead a team of 4 – 6 Designers. Work Environment: In office. Remote schedules only if otherwise agreed to. Physical Demands: Ability to walk a job site if required with proper use of PPE. Position Type/Expected Hours of Work: Monday through Friday, 8 am – 5 pm unless otherwise agreed to with the Engineering Manager. Travel: Minimal. Only to jobsites in the area. Occasional trip may be required to the Houston Office. Classification: Exempt - Salaried Benefits (list). Also maybe "About us" could be a section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list About us, but we could include "About us" as a heading? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exclusive list. We could include "About us" as a heading if we want. However they said "Prefer a few substantive sections over many thin ones." So maybe combine About us and Overview into a single "About the role" or "Overview"? The job title is Engineering Job Captain. The "About us" is company description, not role. Could be omitted? But they said preserve ALL substantive information. So we need to keep company description. Could put it in a

  without heading? Or we could have a heading "About ARCXIS" but not in the list. 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, but suggests those are typical. Safer to follow the examples: include sections for About the role (maybe combine overview and responsibilities?), Responsibilities, Requirements, Benefits. Possibly also include "Work Environment" etc as part of Requirements or a separate section? Could embed in Requirements as prose. We need to avoid creating Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated (list). So we include Benefits section. Pay not stated, so omit. Schedule: they gave Position Type/Expected Hours of Work: Monday through Friday, 8 am – 5 pm unless otherwise agreed to. That's schedule info. Should we include a Schedule section? The posting states schedule, so we can include Schedule section. However they said prefer a few substantive sections over many thin ones. Could embed schedule in Requirements or Overview. But schedule is specific; maybe include as a short

  under a Schedule heading. Since they said include a section ONLY when posting has real, specific content for it. Schedule is present, so we could include Schedule heading. Similarly, we have Work Environment, Physical Demands, Travel, Classification. Could be part of Requirements or a separate "Job Details" section. But we might avoid many thin sections. Could combine those into a "Job Details" section with

  paragraphs. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't mention Job Details. However we could still use other headings if needed, but better to stick to those. So we need to map content to those headings. We have: - About the role: could contain Overview (description of role) and maybe About us? Actually About the role is about the role, not company. So we can put Overview there. - Responsibilities: Primary Responsibilities list. - Requirements: Education, Experience and Desired Qualifications list. - Qualifications: maybe we could split Requirements into Education/Experience and Qualifications? But we have only one list. Could treat Requirements as both. - Skills: maybe we could extract skills from requirements (proficiency in CAD, Revit, etc.) but that's already in Requirements. Could create Skills section listing technical skills. - Benefits: list. - Schedule: Position Type/Expected Hours of Work. We also have Reports to: Engineering Manager (metadata). Could be placed in a short

  under About the role or Requirements. Supervisory Responsibility: Yes. Lead a team of 4 – 6 Designers. Work Environment: In office. Remote schedules only if otherwise agreed to. Physical Demands: Ability to walk a job site if required with proper use of PPE. Travel: Minimal. Only to jobsites in the area. Occasional trip may be required to the Houston Office. Classification: Exempt - Salaried. These could be placed under Requirements or a separate section like "Job Details". But to avoid many thin sections, we could incorporate them into Requirements as additional bullet points or prose. But the instruction: Use

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

    for prose. So we can have multiple

    lists. We need to preserve ALL substantive information. So we must include supervisory responsibility, work environment, physical demands, travel, classification. We can embed them as

    paragraphs under a section like "Job Details" but we don't have that heading. Could we add a heading "Job Details"? The instruction didn't forbid other headings, but gave examples. It said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for sections, but not necessarily limited to them. However to be safe, we could create a section "Details" but that's not in examples. Might be considered deviating. Better to fit into existing sections. We could add a "Requirements" section that includes education/experience, supervisory responsibility, work environment, physical demands, travel, classification as bullet points or prose. But some are not strictly requirements (like work environment). Could still be included. Alternatively, we could create a "Qualifications" section for supervisory responsibility etc. But the examples include Qualifications as a heading. So we could split: Requirements for education/experience, Qualifications for supervisory responsibility, work environment, physical demands, travel, classification. Skills for technical skills (CAD, Revit, etc.). Benefits as given. Schedule as given. About the role for overview. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. That seems reasonable and not too many. Now we need to extract content. About us: company description. Should we include that? It's substantive. Where to put? Could be part of About the role? But About the role is about the role, not company. However we could include a brief company overview under About the role as context. The instruction says preserve ALL substantive information. So we need to include company description. We could add a

    under About the role before the overview. Alternatively, we could create a separate section "About the company" but not in examples. Might be okay but risk. I'd embed in About the role. Thus About the role

    About the role

    then

    containing company description and role overview. Now Responsibilities: list of Primary Responsibilities items. We need to convert each line into

    • . List: - Collaborate with project managers and design teams to develop engineering solutions that meet project deadlines and client requirements. - Review, redline and quality check detailed engineering drawings, specifications, and calculations using CAD, Revit, Forte and other design software. - Conduct site visits and surveys to gather information and assess project conditions, as required. - Coordinate with consultants, contractors, and regulatory agencies to obtain necessary approvals and permits. - Assist in the preparation of project proposals, budgets, and schedules. - Review and evaluate project documentation to ensure compliance with industry standards and codes. - Provide technical guidance, training and support to designer & drafter staff members. - Participate in meetings with clients, stakeholders, and project teams to discuss project progress and resolve technical issues. - Stay current with advancements in engineering technology, codes, and regulations. Now Requirements: Education, Experience and Desired Qualifications list: - Bachelor's degree in Civil Engineering, Structural Engineering, or related field a plus, but equivalent and relevant job experience can be substituted. - Minimum of 5 years of experience in engineering design and project management. - Proficiency in CAD, Revit, and other engineering design software. - Strong understanding of building codes, regulations, and industry standards. - Excellent communication, problem-solving, and teamwork skills. - Ability to manage multiple projects simultaneously and meet tight deadlines. - Ability to lead and manage teams by balancing work distribution to attain high On Time Delivery results and low error rates. - Experience working on commercial, institutional, or multi-family residential projects is a plus. - LEED accreditation or knowledge of sustainable design practices is a plus. Now Qualifications: Supervisory Responsibility: Yes. Lead a team of 4 – 6 Designers. Work Environment: In office. Remote schedules only if otherwise agreed to. Physical Demands: Ability to walk a job site if required with proper use of PPE. Travel: Minimal. Only to jobsites in the area. Occasional trip may be required to the Houston Office. Classification: Exempt - Salaried. We could format as bullet points or prose. Since they are not a list of duties/requirements/benefits, we could use

      for each. But we could also make a

      with
      • for each. The instruction: Use
        • for any list of duties/requirements/benefits. These are not duties/requirements/benefits, but they are qualifications. Could still be list. Safer to use

          for each. Thus Qualifications section:

          Qualifications

          then

          Supervisory Responsibility: Yes. Lead a team of 4 – 6 Designers.

          Work Environment: In office. Remote schedules only if otherwise agreed to.

          Physical Demands: Ability to walk a job site if required with proper use of PPE.

          Travel: Minimal. Only to jobsites in the area. Occasional trip may be required to the Houston Office.

          Classification: Exempt - Salaried.

          Now Skills: we could extract technical skills from Requirements: Proficiency in CAD, Revit, and other engineering design software. Also maybe Forte mentioned in responsibilities. Could list: CAD, Revit, Forte, other design software. Also maybe knowledge of building codes, etc. But we already have those in Requirements. To avoid duplication, we could keep Skills section short: list of software/tools: CAD, Revit, Forte