Traveling OERP Specialist

We need to output HTML fragment with headings

for sections present: About the role? Not present. Responsibilities: we have "Essential Duties & Key Responsibilities". Use heading

Responsibilities

maybe. Requirements: we have Qualifications section. Use

Requirements

or Qualifications? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: Responsibilities, Qualifications, Benefits, Pay. Also maybe "Physical Demands" and "Work Environment" are not in list; we should not create headings for them unless they map to allowed headings. Probably we should drop them as they are not in allowed list. Also we need to include Pay section only if posting actually states salary range. It does: "The salary range for this position is estimated to be 78,000.00 - 110,000.00 USD annualized." So we include Pay heading with that info. Benefits: posting mentions benefits: "Turner Construction provides flexible benefits, including medical, dental, and vision coverage, financial benefits such as a 401(k) plan, Health Savings Account, Flexible Spending Account, wellness benefits, a voluntary legal plan, identity theft, life insurance, and short-term and long-term disability coverage. In addition to our extensive benefits offerings, we provide paid vacation, wellness/sick time, holidays, paid parental leave, tuition reimbursement, employee referral bonuses, and end-of-year appreciation pay." So we include Benefits heading. Schedule: Not explicitly stated; only travel involved 100% and full-time long-term traveling position. No explicit schedule like hours. So we should not create Schedule heading. About the role: Not present; we could maybe use a short paragraph from Position Description? But we should not create heading if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not add About the role if not present. However we have Position Description paragraph that could be considered "About the role". But the instruction says we can use headings like About the role. The posting includes "Position Description:" with a paragraph. That could be considered About the role. We could treat that as About the role section. But we need to decide. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. We can include About the role if we have content. The Position Description paragraph: "Implement First Equipment Company (FEC) On-site Equipment Rental Programs (OERP) and provide training, onboarding, and daily management of on-site programs. Work with project teams and vendors to support efficient use, movement, and maintenance of construction equipment." That's basically a summary. So we could include About the role heading with that paragraph. But we also have Responsibilities section with list of duties. So we could avoid duplication. The Position Description is somewhat overlapping with responsibilities. Might be okay to include as About the role. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, benefits, pay, etc. Also we need to include travel involved 100% maybe as part of Responsibilities? It's a metadata; we could include in a short paragraph under About the role or maybe as a note. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Travel involved 100% is metadata; we could fold into a short

maybe under About the role or as a separate paragraph before sections. But we should not create a heading for it. So we can include a short paragraph after the heading maybe. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

Implement First Equipment Company (FEC) On-site Equipment Rental Programs (OERP) and provide training, onboarding, and daily management of on-site programs. Work with project teams and vendors to support efficient use, movement, and maintenance of construction equipment. This is a full-time long-term traveling position with 100% travel, starting on a project in Prineville, OR.

Responsibilities

• Serve as point of contact for project teams and on-site rental vendors to understand, confirm, and implement equipment needs.
• Visit project sites to establish presence with stakeholders to manage on-site equipment requirements, maintenance, and transition of construction equipment to/from yard.
• Provide exceptional customer service and timely communication with project team stakeholders and on-site trade and rental vendors for relationship development and service excellence.
• Provide support for end-user system troubleshooting related to rental software, and inventory and contract management systems for on-site equipment rental programs.
• Support project teams and vendors adoption and adherence to systems.
• Monitor utilization of rental equipment use and track vendor billing, and accuracy of customer invoices for on-site equipment rental programs.
• Provide on-site equipment rental program preconstruction information, including but not limited to generating equipment lists for bidding consideration.
• Develop and maintain on-going vendor relationships to promote reliability and high service standards throughout projects.
• Other activities, duties, and responsibilities as assigned.

Requirements

• Bachelor’s Degree from accredited program and minimum of 2 years of experience in construction rentals, logistics, equipment, or warehouse management, or equivalent combination of education, training, and experience
• Basic understanding of construction equipment, jobsite logistics, and equipment maintenance requirements
• Knowledge of financial principles and budget forecasting
• Active listening skills and responsive with strong follow-up practices
• Highly organized to manage On-site Equipment Rental Programs (OERP) on project site or yard, and in support of construction operations
• Process skills to think through logistics and communicate expectations
• Ability to professionally engage and collaborate with internal and external stakeholders
• Professional verbal and written communication skills
• Familiar with equipment rental software (e.g., Wynne RentalMan) and P2P systems (e.g., Coupa)
• Experience with continuous improvement concepts, methodologies, and tools
• Embrace change and quick learner to adopt processes, information, and technology enhancements
• Proficient computer skills, Microsoft Office suite of applications, and database applications
• Regular travel

But note: "Regular travel" is already covered; we could keep. We also have Physical Demands and Work Environment; we are not including them as they are not in allowed headings. Should we drop them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we drop Physical Demands and Work Environment, we are omitting substantive information. However we are only allowed to use certain headings; but we could include them as

paragraphs without headings? 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." It doesn't forbid other headings; it says use

  for section headings (e.g. those). It implies we should use those headings for sections, but we could also use other headings if needed? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict headings to only those examples; they are examples. So we could add headings for Physical Demands and Work Environment if we want to preserve that info. However the examples list didn't include them, but they said e.g. So we could still use

  Physical Demands

  and

  Work Environment

  . That would preserve info. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections, but not strictly limited. Safer to include them as headings to preserve info. However the instruction also says "Prefer a few substantive sections over many thin ones." So we might want to avoid too many sections. Physical Demands and Work Environment are substantive but could be combined into a "Working Conditions" section? Not in examples. But we could keep them as separate sections; they'd be thin but still substantive. The instruction says prefer a few substantive sections over many thin ones. So maybe we should combine them into a section like "Working Conditions" but not in examples. Could we embed them under Responsibilities? Not appropriate. Could we add a

  after Responsibilities that includes physical demands and work environment as prose? That would preserve info without extra headings. That seems better: we can include a paragraph that covers physical demands and work environment details. That would keep fewer sections. Thus we will have sections: About the role, Responsibilities, Requirements (Qualifications), Benefits, Pay. Possibly also Skills? Not needed. We need to include all qualifications details; we already have them under Requirements. We need to include Benefits details as list. We need to include Pay details as paragraph. We need to ensure we don't include boilerplate like EEO etc. We'll drop that. Now craft HTML. Check for any repeated lines: Ensure we didn't duplicate. Let's write:

  About the role

  Implement First Equipment Company (FEC) On-site Equipment Rental Programs (OERP) and provide training, onboarding, and daily management of on-site programs. Work with project teams and vendors to support efficient use, movement, and maintenance of construction equipment. This is a full-time long-term traveling position with 100% travel, starting on a project in Prineville, OR.

  Responsibilities

  • Serve as point of contact for project teams and on-site rental vendors to understand, confirm, and implement equipment needs.
  • Visit project sites to establish presence with stakeholders to manage on-site equipment requirements, maintenance, and transition of construction equipment to/from yard.
  • Provide exceptional customer service and timely communication with project team stakeholders and on-site trade and rental vendors for relationship development and service excellence.
  • Provide support for end-user system troubleshooting related to rental software, and inventory and contract management systems for on-site equipment rental programs.
  • Support project teams and vendors adoption and adherence to systems.
  • Monitor utilization of rental equipment use and track vendor billing, and accuracy of customer invoices for on-site equipment rental programs.
  • Provide on-site equipment rental program preconstruction information, including but not limited to generating equipment lists for bidding consideration.
  • Develop and maintain on-going vendor relationships to promote reliability and high service standards throughout projects.
  • Other activities, duties, and responsibilities as assigned.

  Requirements

  • Bachelor’s Degree from accredited program and minimum of 2 years of experience in construction rentals, logistics, equipment, or warehouse management, or equivalent combination of education, training, and experience
  • Basic understanding of construction equipment, jobsite logistics, and equipment maintenance requirements