UAM Utility Designer 1 | Make Ready Engineering | Remote

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info. Let's parse the posting. Company: Davey Resource Group, Inc. Locations: Richfield, OH Additional Locations: Remote Work Site: Remote Req ID: 212143 Position Overview: The Utility Designer 1 is responsible for planning, designing, verifying locations, inspecting, or otherwise capturing information related to utility and telecommunication assets. Then a paragraph about diversity etc. Compensation Data: Starting Rate: $20-$25 per hour Overtime: Time and a half after 40hrs/wk, average work week 45 hours Job Duties: What You Will Do Responsibilities: list bullet points. Qualifications: Required: list bullet points. Preferred: list bullet points. Additional Information: What We Offer [Benefits]: list benefits. Divisional Overview: description of company, EEO statement, etc. Should we include as "About the role"? Probably not; we can include a section "About the role" summarizing position overview and maybe company description? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role (position overview + maybe company description?), Responsibilities, Requirements (maybe required qualifications?), Qualifications (maybe preferred?), Skills (maybe combine required/preferred skills?), Benefits, Pay, Schedule. We need to decide what content goes where. We have: - Position Overview: description of role responsibilities at high level. Could go under About the role. - Compensation Data: Starting Rate and overtime info => Pay section. - Job Duties: list of responsibilities => Responsibilities section. - Qualifications Required and Preferred => could be Requirements (required) and Qualifications (preferred) or Skills. The instruction list includes Requirements, Qualifications, Skills. We need to decide mapping. We have Required qualifications (high school diploma, willingness to obtain certificates, proficiency in basic office apps, ability to read/comprehend/draft correspondence, effective communication skills, basic arithmetic, ability to follow instructions, solve problems). Preferred: Associate's or Bachelor's degree in engineering or related technical field, prior experience in electric utility or telecommunications industry, knowledge of electric hazard identification, equipment identification, or communication equipment, familiarity with Outside Plant Engineering design and pole loading analysis software. We could put Required under "Requirements" and Preferred under "Qualifications". Skills could be derived from both but maybe we can omit Skills if not distinct. The instruction says prefer a few substantive sections over many thin ones. So we could combine Required and Preferred into Qualifications, but we have separate headings allowed. However we must only include sections when posting has real specific content. We have content for both required and preferred, so we could have two sections: Requirements (required) and Qualifications (preferred). Skills maybe not needed. Benefits: we have list. Pay: we have compensation data. Schedule: we have average work week 45 hours, overtime after 40hrs/wk. That's schedule info. Could include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include Skills if no distinct content. Now we need to format. Use

for each section heading. Under each, use

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. We must not repeat job title as heading. We must not put Job ID etc. We must remove boilerplate: EEO statements, divisional overview maybe? The divisional overview includes company description and EEO. That's boilerplate? It's somewhat generic but includes company description. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statement and divisional overview that is basically EEO and company description. However the company description may be considered substantive? It's about Davey Tree Expert Company. Might be considered boilerplate but it's describing the company. The instruction says remove EEO/equal-opportunity boilerplate. The divisional overview includes EEO statement and also description of Davey Tree Expert Company. Might be considered boilerplate but also includes info about the company. However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. It doesn't say remove company description. But the divisional overview includes both. Safer to keep the company description? But it's preceded by "Divisional Overview The Davey Tree Expert Company is an Equal Opportunity Employer..." That's largely EEO. The rest: "Davey Resource Group, Inc., is a leader in the natural resource, environmental, and forestry consulting industries throughout the United States. The Davey Tree Expert Company provides research-driven tree services, grounds maintenance and environmental consulting for residential, utility, commercial and environmental partners in the U.S. and Canada. We care about our clients, each other and the world around us. We offer the resources, size and stability of a big company while maintaining the culture, entrepreneurial spirit and feel of a small one. We invest in our employees by offering industry-leading training, technology and benefits that lead to a rewarding and safe work experience at all levels. Wherever you want to grow your career, there’s a place for you at Davey. To learn more, visit Davey.com." That's somewhat generic but could be considered company overview. Might be okay to keep under About the role? But we already have position overview. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company description if it's substantive. However it's quite generic and could be considered boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. It doesn't explicitly say remove company description. I'd lean to keep it as part of About the role. But we also have "Accommodations: If requested by employee or otherwise as required by law, reasonable accommodations will be made to enable employees with disabilities to perform essential job functions. If you need assistance at any time, please contact us at 1-877-411-7601 or at Recruiting@davey.com." That's also boilerplate (accommodations statement). Should remove. "Employment Type: Permanent Job Type: Full Time Travel Expectations: None" - Travel Expectations: None is maybe schedule-related but it's basically none. Could be considered schedule info but it's just stating none. Might be considered filler. The instruction: 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. Travel Expectations: None is like "None" which is placeholder? Might be considered filler. Better to omit Travel Expectations. Thus we will not include a separate Travel section. Now schedule: we have average work week 45 hours, overtime after 40hrs/wk. That's substantive. Now we need to ensure we don't duplicate content. Let's extract each piece. About the role: combine Position Overview paragraph and maybe company description. Position Overview: "The Utility Designer 1 is responsible for planning, designing, verifying locations, inspecting, or otherwise capturing information related to utility and telecommunication assets. The Davey Tree Expert Company and its subsidiaries value each individual and strive to encourage diverse ideas and perspectives to inspire collaboration and empower our employees. We believe our commitment to building a culture of belonging by treating everyone with respect, dignity, empathy, and care is critical to achieving our vision and mission." That's the position overview paragraph. Company description from divisional overview (excluding EEO): "Davey Resource Group, Inc., is a leader in the natural resource, environmental, and forestry consulting industries throughout the United States. The Davey Tree Expert Company provides research-driven tree services, grounds maintenance and environmental consulting for residential, utility, commercial and environmental partners in the U.S. and Canada. We care about our clients, each other and the world around us. We offer the resources, size and stability of a big company while maintaining the culture, entrepreneurial spirit and feel of a small one. We invest in our employees by offering industry-leading training, technology and benefits that lead to a rewarding and safe work experience at all levels. Wherever you want to grow your career, there’s a place for you at Davey. To learn more, visit Davey.com." We could combine these into About the role. Now Responsibilities: list from Job Duties: - Utilize software platforms to analyze and interpret field data. - Record existing telecommunication and electric utility infrastructure. - Identify and document safety risks and hazards. - Apply engineering principles to design aerial and underground utility facilities. - Transfer designs to other software platforms. - Collaborate to propose infrastructure design solutions. - Ensure equipment maintenance and report issues promptly. - Travel occasionally (5%) for on-site job duties, projects, or meetings. Now Requirements (required qualifications): - High school diploma or equivalent. - Willingness to obtain and maintain professional certificates and licenses as required. - Proficiency in basic office applications and data entry; willingness to learn utility design software. - Ability to read, comprehend, and draft professional correspondence. - Effective communication skills in both one-on-one and group settings. - Basic arithmetic proficiency. - Ability to follow detailed instructions, solve problems, and address varied situations. Now Qualifications (preferred): - Associate’s or Bachelor's degree in engineering or related technical field. - Prior experience in the electric utility or telecommunications industry. - Knowledge of electric hazard identification, equipment identification, or communication equipment. - Familiarity with Outside Plant Engineering design and pole loading analysis software. Now Benefits: list from What We Offer [Benefits]: - Group health plans* - Short-term and long-term disability insurance* - Life insurance* - Paid parental leave - 401k with up to a 4% company match** - Employee Stock Purchase Plan: Opportunity to buy company stock at a 15% discount - Holidays and paid time off* - Payroll savings plan* - Charitable matching gift program* - Employee referral bonus program* - Employee Educational Scholarship* - Davey Family Scholarship* - 20% discount on all Davey services* - Cell phone discounts* - Vehicle purchase discount program* - Plus, so much more! - All listed benefits available to eligible employees on Day 1. - Union employees are not eligible for a 401k plan, but may be eligible to join pension plans negotiated by their local union. We need to preserve all substantive information, including the asterisks and double asterisks? They are likely footnotes. We should keep them as part of the text. Now Pay: Starting Rate: $20-$25 per hour Overtime: Time and a half after 40hrs/wk, average work week 45 hours. We could phrase as: Starting rate: $20–$25 per hour. Overtime: time and a half after 40 hours per week. Average work week: 45 hours. Now Schedule: we could include the average work week and overtime info, but that's already in Pay. However schedule section could contain typical work week, overtime policy. Since we already have Pay section with that info, maybe we don't need separate Schedule. But the instruction allows Schedule section if posting states them. It does state average work week 45 hours and overtime after 40hrs/wk. That's schedule info. However we already used that in Pay. Could we avoid duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but we should avoid redundant sections? It says prefer a few substantive sections over many thin ones. So we could combine Pay and Schedule into one section? But headings are predefined; we could still have both