Traveling OERP Specialist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if there is real specific content. We need to parse the posting. First, remove boilerplate: Division, Project Location(s), Minimum Years Experience, Travel Involved, Job Type, Job Classification, Education, Job Family, Construction, etc. Those are metadata; we can fold minor metadata into a short

or drop it. The instruction: "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." So we can include a short paragraph with location, travel, job type maybe. We need to preserve all substantive information: Position Description, Essential Duties & Key Responsibilities, Qualifications, Benefits, Salary range, etc. We need sections: maybe "About the role" (position description), "Responsibilities" (essential duties), "Qualifications" (education/experience), "Skills" (maybe list of skills), "Benefits", "Pay". Schedule? Not given explicitly; travel involved 100% indicates travel, but schedule not given. We shouldn't create Schedule unless posting actually states it. It does not give schedule like full-time, but it says full-time long-term traveling position. That's schedule info: full-time. Could we treat that as Schedule? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full-time long-term traveling position. So schedule could be inferred as full-time. But is that explicit? It says "This is a full-time long-term traveling position". That's schedule info. So we can include a Schedule section with "Full-time, long-term, traveling". However, we need to avoid filler like "not specified". It's specified. We also have Pay: salary range given. Benefits: described. Thus sections: About the role (position description), Responsibilities (essential duties), Qualifications (education/experience), Skills (maybe list of skills from qualifications), Benefits, Pay, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract content. Position Description: "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 prose. Essential Duties & Key Responsibilities: list bullet points. Let's list them: - 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. Also note: "This is a full-time long-term traveling position that will be starting on a project in Prineville, OR". That's schedule/location/travel. Salary range: "The salary range for this position is estimated to be 78,000.00 - 110,000.00 USD annualized." 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." Qualifications: list: - 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 Physical Demands and Work Environment: these are substantive but maybe we can include under a section like "Working Conditions" but not in allowed headings list. The allowed headings are limited to those: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical demands under "Requirements" maybe? Or "Skills"? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings; we can also use "Requirements" for physical demands etc. But we need to preserve all substantive information; we can include physical demands under a "Requirements" section (maybe as a list). Or we could add a "Working Conditions" section but not in the list; risk of being considered not allowed. Safer to put physical demands and work environment under "Requirements". Also "Travel Involved: 100%" could be under Schedule or Requirements. We need to avoid filler like "commensurate with experience". Not present. Now craft HTML. We'll start with a short

  for metadata: location, travel, job type maybe. But we can incorporate location into Schedule or About the role. The instruction: fold minor metadata into a short

  or drop it. So we can have a

  with location and travel info. Let's produce:

  Location: Bend, OR 97703 USA (starting project in Prineville, OR). Travel involved: 100%. Job type: Regular, full-time long-term traveling position.

  Then sections. About the role:

  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.

  Responsibilities:

  Responsibilities

  • ...
  Qualifications: maybe separate Qualifications and Skills. Qualifications could be education/experience; Skills could be abilities. We have qualifications list includes education, experience, understanding, knowledge, skills, etc. We could split: Qualifications: education and experience; Skills: the rest. But we need to avoid thin sections. Could combine Qualifications and Skills into one section "Qualifications" with both education/experience and skills. However the instruction allows both headings; we can use both if we have substantive content. Let's decide: Qualifications heading for education/experience; Skills heading for abilities/knowledge. Qualifications content: - 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 That's it. Skills content: list the rest: - 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 We could also include physical demands under Requirements maybe. But we have not used Requirements heading. Could put physical demands and work environment under Requirements. Requirements content: list physical demands and work environment. Physical demands bullet points: - Frequently required to sit, climb, balance, stoop, kneel, crouch, crawl, use hands to finger, handle or feel objects, tools, or controls, and reach with hands, talk, and hear. - Frequently views a computer monitor and frequently uses a computer keyboard. - Specific vision abilities required: close vision, peripheral vision, depth perception, and ability to adjust focus. - Performance of required duties require physical ability to climb permanent and temporary stairs, passenger use of construction personnel hoists, ability to climb ladders and negotiate work areas under construction. - Regularly required to be mobile, and regularly travels both short and long distances via a variety of conveyances. - Must regularly lift and/or move up to 10 pounds and occasionally lift and/or move up to 25 pounds. Work environment bullet points: - Performs work on-site at construction work sites, office locations, and/or off-site venues. - Regularly works at construction work sites where exposed to moving mechanical parts, high precarious places, fumes, or airborne particles, outside weather conditions, and risk of electrical shock. - Noise in work environment usually moderate to loud. - Occasionally works in an office or remote setting; noise usually quiet to moderate. - Required to work in compliance with company safety policies, procedures, and applicable laws. We could combine these into Requirements. Now Benefits: list. Benefits content: we can list as
  • ...
  . Pay:

  Pay

  The salary range for this position is estimated to be 78,000.00 - 110,000.00 USD annualized.

  Schedule:

  Schedule

  Full-time, long-term, traveling position (starting project in Prineville, OR). Travel involved: 100%.

  We already included location in metadata p; but we can also include location in schedule. To avoid duplication, maybe keep metadata p minimal: location and job type. Then schedule just full-time long-term traveling. But we need to avoid duplication. Let's decide: metadata p: "Location: Bend, OR 97703 USA (starting project in Prineville, OR).